Eat the Frog: Method, Examples and Common Mistakes

What is the eat the frog method?

The eat the frog method is a daily prioritisation rule: identify the single task that matters most and that you are most tempted to postpone, then complete it first thing, before reactive work begins. Everything else in the day is allowed to be second.

Brian Tracy popularised it in *Eat That Frog!* (2001), a short book of 21 techniques for stopping procrastination. His framing is deliberately blunt: if your job is to eat a frog, do it first thing in the morning, and if you have two frogs, eat the biggest one first. The frog is not the easiest task, the most urgent task, or the task someone else is asking about. It is the one that would change the week if it were finished.

That definition has three parts, and all three matter:

1. Important — it moves a goal, a client, a deadline or a number that someone will eventually ask about.
2. Avoided — you have already rescheduled it at least once, or you feel a small resistance when you look at it.
3. Undone in one sitting — it can be finished or meaningfully advanced in one protected block, not “worked on” indefinitely.

Most people confuse the frog with the hardest task on the list. Hard is not the test. A hard task that nobody needs is just hard. The test is consequence.

Where does “eat the frog” come from?

It does not come from Mark Twain, and the real origin is older and stranger. The line is usually printed as: “Eat a live frog first thing in the morning and nothing worse will happen to you for the rest of the day.” Quote Investigator found no evidence that Twain wrote or said it. The first documented attachment of the line to Twain appears in a newspaper in 1988 — seventy-eight years after he died.

The trail leads back to the French writer Nicolas Chamfort, who died in 1794 and attributed the remark to a acquaintance called Monsieur de Lassay. The original version is about swallowing a toad each morning so that nothing later in the day would seem disgusting by comparison. Émile Zola swapped the toad for a live frog in an 1896 essay about literary criticism. The metaphor then travelled for a century before someone hung it on Twain, where it stuck.

Does the misattribution matter? Slightly, yes. It is a useful reminder that a memorable quote is not evidence. The method has to stand on its own mechanics, and fortunately it does — the research below is about behaviour, not about who said what.

> Common mistake: repeating the Twain line in a team workshop. Someone in the room will know it is fake, and the rest of your argument loses a little authority at exactly the moment you need it.

How do you actually do it? Five steps

The method is simple to describe and easy to do badly. These five steps are the version that survives a real week.

Step 1: Choose the frog the evening before

Pick tomorrow’s frog before you leave work, not at 9 am when the inbox is already open. Choosing in the morning means choosing while reacting, and reactive brains pick the loudest task rather than the most valuable one. Write the frog on a physical note or pin it as the top task in your tool, and add one sentence on what “done” means.

Step 2: Define done in observable terms

“Work on the pricing model” is not a frog; it is a mood. “Send the revised pricing model to Lena with the three scenarios and a recommendation” is a frog. The definition should be specific enough that a colleague could tell whether you finished.

Step 3: Protect the first block before anyone else can book it

Block 90 minutes at the start of your working day and treat it as an external meeting with yourself. If your calendar is shared, mark it private or label it “focus — do not move”. The block is the method; without it, eat-the-frog is just a nice intention.

Step 4: Write an if-then plan for the moment you will start

This is where most of the effect lives. Instead of “I will do the frog tomorrow”, write: “If I sit down at 8:30 and open my laptop, then I will open the pricing file and write the recommendation before opening email.” The structure is a trigger plus an action, and it removes the in-the-moment decision that procrastination feeds on.

Step 5: Remove the escape hatch

Close email, mute chat, put the phone in another room, and close every tab that is not the frog. If the frog requires research, open only the two sources you need. The point is not discipline; it is removing the two-second decision that lets you drift.

Why does the eat the frog method work?

It works because starting is the expensive part, and pre-decided starts are cheaper than improvised ones. That is not a motivational claim; it is one of the better-supported findings in self-regulation research.

In a meta-analysis of 94 independent studies with more than 8,000 participants, Gollwitzer and Sheeran found that forming implementation intentions — explicit if-then plans about when, where and how to act — had a medium-to-large effect on goal attainment, d = 0.65. In one of the underlying experiments, students given a difficult goal completed it 62% of the time when they had formed an implementation intention, against 22% without one. A separate study on holiday assignments found that people with if-then plans started 1.5 hours from their intended time, while people with only a goal intention drifted 8 hours.

Two supporting facts make the method relevant rather than theoretical. Around 20% of adults describe themselves as chronic procrastinators, a rate that has held steady across countries for three decades of research. And procrastination is not a time-management failure so much as an emotion-regulation one: the task is avoided because it feels aversive, and avoidance provides immediate relief. Doing the frog first removes the relief loop before it can run all day.

Where the folk explanation goes wrong. The usual story is that willpower peaks in the morning, so the hardest task should go first. That is too simple. Chronotype matters: if you are a genuine night owl, your best cognitive window may be late morning or early evening, and forcing a 6 am frog can produce a worse result than a 4 pm one. The defensible version is narrower — do the frog in your first protected block, whatever time that is, and do it before reactive work claims the day.

How do you choose the right frog?

Score your candidates on four dimensions from 1 to 5: impact on a real goal, how often you have postponed it, how much dread it produces, and whether it can be finished in one block. Multiply impact by two, because consequence should dominate, then add the rest. Highest score wins. It takes three minutes and it beats staring at a list.

Here is a worked scoring for a freelance designer on a Tuesday:

The proposal wins clearly. Notice that the invoice query is the most finishable and the least dreaded — which is exactly why it is dangerous. It is the task you will do instead, feel productive about, and then reschedule the proposal for the fourth time.

What does it look like in practice?

Scenario 1: the 90-minute arithmetic. A product manager protects 90 minutes at 8:30 every weekday. That is 7.5 hours a week out of a 40-hour week — 19% of her working time, spent on the single highest-consequence item. Over a quarter that is roughly 90 hours, or two and a half working weeks, applied deliberately instead of dissolving into meetings. The same person previously spent those morning hours on Slack and status updates.

Scenario 2: twelve frogs versus four. Two account managers handle similar workloads for ten weeks. The first does eat-the-frog four days a week and completes 12 significant pieces of work — proposals, quarterly reviews, a churn-risk plan. The second works the same total hours but starts with email, and completes four. Same effort, three times the output on the work that gets reviewed at year end.

Scenario 3: the cost of a postponed frog. An operations lead has a frog worth finishing: reconciling a supplier invoice run before month end. Postponed by three working days, it delays $84,000 of payments, triggers two supplier calls, and costs a Friday afternoon of firefighting. The task itself was 70 minutes. The delay cost roughly six times the task.

Scenario 4: the frog that is too big. “Write the annual report” is not a frog. Split it: “Draft the operations section, 1,200 words, from the Q3 notes”. That is finishable in 90 minutes. If your frog cannot be finished in one block, the frog is actually the first slice of a project, and you should name the slice.

What are the common mistakes?

• Five frogs. Choosing three to five “priorities” recreates the problem the method solves. One frog, and a clear second in case the first is blocked by someone else.
• Opening email first “just to check”. Ten minutes of inbox triage sets the day’s agenda to other people’s priorities. The frog does not survive that.
• Choosing the frog in the morning. You will pick what feels urgent at 9:05, which is rarely what matters.
• No definition of done. Vague frogs expand to fill the block and end in a status of “made progress”.
• Letting the block be movable. A focus block that can be rescheduled for any meeting will be rescheduled for every meeting.
• Treating the frog as the whole day. The method orders your day; it does not replace planning, and it does not excuse you from the 20 smaller tasks that keep a team running.
• Skipping the frog on bad days and calling the method broken. One missed day is data, not failure. The habit is judged over a month, not a morning.

> Practical tip: keep a “frog log” of one line per day — the task, whether it was done before 11 am, and what interrupted it. After three weeks, the log tells you whether your problem is avoidance, an over-booked calendar, or frogs that are too large. Each has a different fix.

Who should not use this method as written?

The method assumes you control your first working hour. Plenty of people do not, and pretending otherwise produces guilt rather than output.

If you work on-call, in a hospital ward, on a support desk or in a warehouse, your day starts with whatever arrives. For those roles, the adaptation is a “frog window” rather than a frog morning: the first 45 minutes after the peak period, protected and labelled. If you are a parent with a 6 am to 9 am school run, your frog may be at 9:30 or 8 pm. If your role is genuinely reactive by design — sales development, incident response, executive assistance — the honest alternative is to pick the frog three times a week rather than daily, and protect the block on those days.

There is also a harder case: the frog you keep avoiding because it is genuinely underspecified, not because it is unpleasant. If you have moved the same task for three weeks, the problem is usually that you do not know what the first step is. In that case the frog for today is “define the first step and book 30 minutes with the person who knows”.

How does the method work for a team?

At team level, the useful version is a shared frog, not a shared rule. Each person names their frog in the daily stand-up, and the team agrees not to book meetings into the first block without a reason. That single calendar norm does more than any productivity training.

Two practices make it stick. First, the team lead models it: if the manager’s first act each morning is a 9 am status call, nobody will protect their own block. Second, review the frog log weekly in the same meeting where work is reviewed — not to police individuals, but to notice when a frog has been postponed three weeks running. A repeatedly postponed frog is usually a decision nobody has made yet, not a discipline problem.

For distributed teams, add one rule: no asynchronous messages before the block ends unless something is on fire. The cost of a “quick question” at 8:40 is not the two minutes of reply; it is the twenty minutes of reloading context.

Where does Doitify fit?

Doitify is our product, so read this section with that in mind. The method needs three things to survive: a place to record tomorrow’s frog, a calendar block that is visible to the team, and a record of whether it happened. Most people keep those in three different apps, which is why the habit decays around week three.

In Doitify, a task can carry sub-tasks, a checklist, an owner and a due date, so the frog is not a note but a piece of work with a definition of done attached. You can flag the day’s frog, block the time on the calendar, and see in the work report whether the block was protected. The AI Coach can also break an oversized frog into a first slice, which addresses the most common reason people stall. It will not make the task pleasant, and no tool can. It removes the friction between deciding and starting.

Conclusion

Eat the frog is a one-sentence rule with an unusually good evidence base behind the mechanism it relies on. Decide the night before, define done, protect the first block, and write the if-then sentence that removes the moment of choice. That is the whole method.

The reason it fails is rarely the method. It is five frogs instead of one, a block that can be moved by anyone who asks, and frogs that are really projects wearing a task’s clothing. Fix those three and the rest follows: the worst thing in your day is finished before the day has a chance to fill up with everything else.

If this post on eat the frog was helpful, you might also enjoy Workplace Context Switching Statistics: The 2026 Data Guide and Time Blocking vs Time Tracking: What’s the Difference and Which Should You Use?.