When “Eat the Frog” Is the Wrong Advice

Mark Twain (probably) said: eat a live frog first thing in the morning, and nothing worse will happen to you the rest of the day.

Brian Tracy turned it into productivity advice. The frog is your biggest, most important, most avoided task. Eat it first. Get it done before anything else gets in the way.

It’s good advice. For most situations.

But there’s one specific scenario where eating the frog will derail your entire day — and it’s more common than people realize.

When You’re Behind

Here’s the situation I’m talking about.

You have a backlog. Things that are overdue. Tasks that have been sitting on your list longer than they should. The pile has grown and now you need a session to work through it.

Some of those tasks are genuinely easy. A quick reply. A bill that just needs a credit card number. A form to fill out. Tasks that, with normal focus, you’d finish in five minutes each.

Others are harder. They require phone calls. Being put on hold. Navigating a bureaucratic process. Coordinating with someone whose schedule you don’t control.

Eat the frog says: start with the hard one.

But here’s what actually happens when you do.

You dial the bank. You wait 20 minutes on hold. You get transferred. You wait again. By the time the call is over, 45 minutes have passed and you’ve accomplished one thing. You’re tired. And now you look at the rest of your list.

The easy tasks that should take 10 minutes feel heavier than they did before. The momentum you needed to work through the backlog is gone. A lot of people just stop there and walk away.

The Momentum Principle

When you’re operating from a full tank — fresh energy, no backlog, a clear day ahead — eat the frog works well. You attack the hardest thing while you’re at your sharpest. Everything easier comes after.

But when you’re behind and need to rebuild, the dynamic is different. You’re not operating from a full tank. You need to build momentum first, and momentum comes from finishing things.

I had a coaching client working through exactly this situation — a pile of overdue bills, some that were one-click payments and others that required phone calls. I told him: start with the click-to-pay ones. Clear four or five of those. Get moving.

After a few quick completions, the state changes. You’re not staring at a pile anymore — you’ve already made a dent. The hard task at the end, the phone call you’ve been dreading, feels different when you’re already rolling.

Matching Task to Actual Energy

At Asian Efficiency, we talk about High, Medium, Low task matching — the idea that different tasks require different amounts of cognitive energy, and you should match task type to your actual available energy, not some idealized version of it.

High-energy tasks: complex thinking, writing, strategic decisions. These need full focus.
Low-energy tasks: routine admin, simple payments, confirmations. These can run on fumes.

When you’re behind and feeling overwhelmed, your available energy is often lower than usual. The overwhelm itself costs something. In that state, leading with a low-energy task and building up is more practical than leading with a high-energy task that might not get finished cleanly.

The goal isn’t to avoid hard things. It’s to sequence them correctly for the conditions you’re actually in.

How to Apply This

Next time you have a backlog session, sort your tasks before you start.

Look at everything you need to get through and ask: what’s the easiest thing here? What can I finish in under 10 minutes without much friction? Start there.

Do two or three of those first. Get some completions behind you.

Then work your way up. By the time you get to the hard thing, you’ll have momentum — and that momentum is a real input into how well the hard thing goes.

Eat the frog when you have a full tank. Build momentum first when you don’t.

For a full system to manage your tasks based on energy and priority, the Productivity Academy covers the complete High/Medium/Low matching framework along with weekly planning and daily execution workflows.