Ivy Lee, Eat the Frog and ABCDE: three daily methods

Most personal prioritization advice collapses into one instruction, which is why so much of it feels interchangeable. These three do not: each answers a question the other two leave open.

• ABCDE decides what belongs on the list. It grades every item by the consequence of not doing it, and two of its five grades take work off the list entirely.
• Ivy Lee decides the order. Six items, ranked, worked one at a time, with the ranking done the day before.
• Eat the Frog decides what happens first. The hardest important task goes at the front of the day, before the day has a chance to fill up.

Run them in that sequence and you have a daily routine that costs about ten minutes at the end of the afternoon. Run one alone and you have a useful habit with a known gap.

The method has been retold thousands of times and the retellings agree. What varies is which part people treat as optional, and the parts they drop are the parts doing the work. Four constraints are load-bearing: the list is capped at six, it is ranked rather than merely written, it is made the evening before, and the items are worked in strict sequence. Remove any one and you are left with a to-do list.

Six has no special property. Five works, seven works. What matters is that the number is small enough to force a choice and large enough to describe a real day, and that the choice happens when nothing is on fire.

The evening step is the one with a research footing. Peter Gollwitzer's work on implementation intentions, summarized with Paschal Sheeran in a meta-analysis covering dozens of studies, found that deciding in advance when and where you will act produces a medium-to-large improvement in whether the action happens at all, compared with holding the same goal without a plan. Writing tomorrow's six at 5 PM is an unglamorous version of exactly that.

Without it, a day that begins with deciding what the day is about begins with the inbox, because the inbox is the only place where a decision appears to have been made for you already.

Brian Tracy's Eat That Frog!, first published in 2001, takes its title from a line about eating a frog first thing in the morning so that nothing worse can happen to you for the rest of the day. Tracy attributes it to Mark Twain, as does nearly everyone who repeats it, but it does not appear in Twain's published writing and the image is usually traced further back, to the eighteenth-century French writer Nicolas Chamfort. It is the same effect as the Schwab check: a memorable line acquires a famous name.

The instruction underneath is precise. Your frog is the task with the largest consequence that you are least likely to start voluntarily. Not the biggest task, and not the technically hardest one: the one carrying avoidance. Tracy's corollary is that if there are two frogs, you eat the uglier one first.

Two questions identify it reliably:

• If today produced only one thing, which one would make the day worth having? That finds the consequence.
• Which item have I moved forward more than twice? That finds the avoidance. When both questions return the same item, you have the frog and there is nothing left to decide.

Three details separate people who do this from people who intend to. Set the frog up the night before, so the morning starts with the work rather than with locating the file. Do it before opening email, because email is a queue of other people's frogs and it supplies excuses that feel like reasons. And if the frog genuinely needs three hours, that is a block to schedule, which is the territory of time blocking and timeboxing.

ABCDE comes from the same book and does the job the other two assume is already done: turning a long, undifferentiated list into a graded one. You write out everything, then put a single letter beside each item, and the letter is determined by consequence rather than by preference or urgency.

The rule that makes the grading enforceable is this: never work on a B while an A is open, and never on a C while a B is open. Without it, the letters are decoration.

Two grades are where the method earns its keep, and both are uncomfortable. D is limited by authority, not by judgement. A common rule of thumb is to delegate anything someone else can do to roughly seventy percent of your standard, since the missing thirty percent is worth less than the hours it buys back. But if you have nobody to hand work to, the letter is unavailable and the honest version of your list has no Ds in it.

E is the letter almost nobody uses. Eliminating a task means telling someone it will not happen, or admitting that a thing you agreed to six weeks ago was never going to matter. That is a social cost rather than an organizational one, which is why unused E items survive as permanent Cs. A list with no Es on it has usually not been graded, only annotated.

The failure mode is grade inflation. If more than about a third of the list is A, the grading has become an expression of anxiety rather than a judgement about consequence. The corrective is to name the consequence in a sentence: if you cannot finish "if this does not happen by Friday, then ..." with something concrete, it is a B.

Suppose eleven things are on the list: a performance review you owe a direct report, open nine days; a vendor contract to approve; an answer legal wants on a data processing agreement; a section of the quarterly plan to draft; a colleague's design document to read; an expense report; a wiki page to tidy; a conference invitation; two recruiting screens to schedule; a newsletter you keep meaning to leave.

Graded: the review, the contract and the legal answer are As. The plan section and the design document are Bs. The wiki page is a C. The expense report and the recruiting screens are Ds. The newsletter and the conference invitation are Es, and both are dealt with in two minutes tonight.

Ranked into tomorrow's six: the review, the legal answer, the contract, the plan section, the design document, and the wiki page if the day is kind. The frog is obvious, because it is the item carried for nine days. It goes first, before email, so the review is written by 10 AM instead of being moved a tenth time. The exercise took under ten minutes, and its main output was not the list: it was that two items left the system entirely and two more became someone else's.

All three assume a working day that is mostly yours, and that is where each fails first.

Ivy Lee assumes a single lane. Strict sequential work is impossible on a calendar with eight to fifteen meetings on it, and items block on other people all day. The adaptation that keeps the spirit is to treat the six as an order of preference rather than a queue: when a gap opens you work the highest-ranked item that is currently startable, and you never take a lower one because it is easier. Sizing tasks to the gaps they will fall into is covered in time blocking and timeboxing.

Eat the Frog assumes the frog is a task. Dread is often a symptom of an undefined next step rather than of difficulty: "write the performance review" resists starting in a way that "open last quarter's notes and list three examples" does not. That is a scoping problem, and the decomposition habit for it belongs to Getting Things Done, whose next-action rule exists for items that feel heavy because they are vague. The method also assumes morning is your best hour. For many people it is not, and the more accurate instruction is to eat the frog in your peak window, wherever that falls; see energy management.

ABCDE grades consequence, and consequence is not leverage. A small task that unblocks four other people can score C on its own consequence and still be the most valuable thing on the list. Personal grading cannot see that, which is what team-level scoring is for: MoSCoW and RICE weigh reach and effort explicitly, and the Eisenhower Matrix separates urgency from importance, which ABCDE folds into a single letter.

One failure is shared by all three: they make choosing easier and none of them makes starting easier. If the frog is correctly identified, ranked first and still not begun by eleven, the problem is not prioritization, and the small-commitment techniques in Pomodoro and Atomic Habits are the better tool. A timer set for twenty-five minutes asks for less than a morning does.