The ABCDE Task Prioritization Method: A Framework That Helps You Actually Do Less

How long is your to-do list? Twenty items? Fifty? Or so long you avoid opening it altogether.

For a long time, my list was exactly that: a sticky, tangled heap of variables. Every day, new tasks arrived faster than I could finish old ones. I crossed things off quickly, but the genuinely important stuff kept sinking to the bottom. It wasn’t until I tried an old framework—Brian Tracy’s ABCDE method—that I realized the problem had never really been “too many tasks.” It was that I had never sorted them by weight.

The Longer Your To-Do List, the Less You Want to Touch It

The longer the list, the higher the cost of getting started. You stare at the cascade of tasks, silently calculating which one is more urgent, and still don’t make the first move. This is classic decision fatigue. Before doing any real work, you’ve already spent your mental energy.

The more subtle issue is that many items on your list don’t belong there at all. Some should be handed to other people. Some should simply be deleted. Instead, you carry them all on your shoulders without distinction. From what I’ve seen, the gap between people who focus deeply and people who stay busy often has less to do with discipline than with who figured out earlier which tasks could be dropped safely.

Burnout is often a tooling problem, not just a habit problem.

Say you carve out an afternoon block for deep work, and a stream of meeting requests slowly eats it away. In that case, the thing worth fixing is your workflow and prioritization mechanism—not your willpower.

ABCDE: A Five-Letter Coordinate System for Priority

Here’s a simple way to layer your tasks. It looks almost too basic, but don’t underestimate it.

A-Level: You Can’t Afford to Skip This Today

A means must do. If you don’t do it, the day has not really been lived—or more precisely, real trouble will show up at your door.

The test is blunt: if you push this off until tomorrow, will somebody come looking for you? Will a key deliverable slip? Will the situation go from manageable to messy?

If you can’t tell within three seconds, it’s probably not an A. Important tasks carry their own weight; they shouldn’t require long deliberation.

B-Level: You Should Do It, but the Sky Won’t Fall

B means should do. There’s a real benefit to completing it, but missing it doesn’t cause immediate damage.

Weekly reports, non-urgent client follow-ups, routine maintenance work—these often land in the B bucket. The defining feature of a B task: it can wait, but it shouldn’t vanish forever. If something has sat at B for three weeks without being touched, you need to make a call. Downgrade it to C or promote it to A and schedule it. The worst option is to pretend it’s not urgent while quietly resenting its presence.

C-Level: Nice to Do, Low Cost to Skip

C means nice to do. These tasks bring real satisfaction and marginal value, but dropping them won’t cost you anything.

Recommending a book to a friend, tidying your bookmarks, poking around a new tool that hasn’t been green-lit yet—all of these are C. My habit now is to batch them in a specific time window, say, Friday afternoon, half an hour max, no more.

D-Level: Hand It Off

D means delegate. Plenty of people get stuck here, always thinking, “teaching someone else takes more time than just doing it myself.”

That’s true the first time. But the genuine value of D-level shows up later: once someone else learns it, every future iteration stops eating your core attention. The real question isn’t “Can this person do it right now?” It’s “Can this task be taught and completed by someone else?”

E-Level: Delete It Without Guilt

E means eliminate. Erasing a task isn’t failure. It’s an active choice.

Pay attention and you’ll discover a long list of things that were meaningful once but are long past their expiration date. The weekly KPI report nobody actually reads. The group chat asking you to sync status every week, out of habit, while everyone scrolls past. The process improvement initiative that has stalled for six months with no clear owner. Those items were never going to happen. Delete them, and you’ll feel an odd relief—better, honestly, than crossing off a finished task.

Fifteen Minutes to Sort Today’s Tasks

The whole workflow is straightforward. Here’s how I walk through it.

1. Write down every single task for the day. Don’t sort anything yet.
2. Label each one A, B, C, D, or E. You know what the letters mean.
3. Rank the A-level items internally. Make them A-1, A-2, A-3, with the most consequential first.
4. Start on A-1. Don’t touch anything else until it’s done.

If you prefer an interactive template, there are free ABCDE list tools online that sort letters for you. I’ve tried them; pen and paper is faster. Every extra step of recording adds a little mental load.

Here’s a sample from my own list, after I had sorted it:

A-1 Finalize the client proposal; send by 3 p.m.
A-2 Investigate the server billing anomaly; coordinate with finance
B   Update the project weekly report
C   Organize this week's saved articles
D   Have the intern run the competitor data gathering process
E   Remove "research new meeting tool"—two weeks untouched

If I had kept this as one flat list, I would have felt the pressure immediately. Once graded, the mind only sees one picture: start A-1. Everything else stays outside the attention radius.

How to Tell Whether Something Is an A or a B

The boundary between A and B trips up almost everyone. I’ve seen people who tag every task on the list as A. At that point, the whole system collapses.

My personal rule is what I call the “three-day consequence test.” Pretend you stop doing the task completely for three days. What happens?

If the answer is “someone will chase me, and something will break,” it’s an A. If it’s “maybe a little messy, but recoverable,” it’s a B. If it’s “probably nothing at all,” it doesn’t deserve B either.

It’s not a rigorous test, I admit. But it saves a lot of agonizing. The goal of prioritization isn’t to find the perfect sequence. It’s to make a reasonable call about what to do next with limited energy.

Where ABCDE Sits Next to Other Prioritization Methods

There are of course other methods out there. RICE scores each task by Reach, Impact, Confidence, and Effort. It works well when you need to quantify a complex decision, especially when several candidates all look defensible. MoSCoW splits items into Must, Should, Could, and Won’t, which makes trade-offs visible in a team setting. Kanban boards keep work flowing through columns and show you how fast tasks are moving. The Ivy Lee method asks you to pick six important items each day and work through them in order. “Eat the frog” tells you to attack the ugliest, hardest task first thing in the morning.

Each of these has a natural habitat. RICE works when you need to quantify complex trade-offs. MoSCoW supports team alignment during planning because the trade-offs are right there in the open. Kanban shines in long-running projects, where you can see task flow at a glance.

I still prefer ABCDE because it makes consequence the primary criterion, and the learning curve is almost nonexistent. No scoring spreadsheet, no board maintenance, no complicated system to hold in your head. In most cases, five minutes is enough to grade every task on today’s list. For someone already exhausted with no spare energy to learn elaborate frameworks, that lightness is exactly the point.

You can read more about Brian Tracy’s original take on the method in Eat the Frog.

Common Pitfalls When Using ABCDE

The method is simple, but execution has a few traps.

The most common one is tagging all fifteen tasks as A. If everything is important, nothing is. I keep the number of A tasks to three or fewer. If you have more, your judgment about consequences has drifted.

Another trap is treating D as a way to dump work. Delegation only works when the other person can actually receive it, and when you pass along enough context. If you just throw a task over the wall with no explanation, it will likely come back to you—or worse, be completed into something nobody recognizes. When I delegate, I treat it like writing a tiny handoff doc: background, expected output, deadline, all in one pass.

Then there’s the B and C graveyard. Labeling tasks B or C doesn’t mean they’ll ever get done. Build a weekly ritual to review the list and demote or delete anything that has sat at B for two consecutive weeks without movement. Otherwise, your list slowly becomes a monument to everything you meant to do but never had time for.

Closing: A Method Only Works When You Use It

What the ABCDE method really asks you to do isn’t just assign letters. It forces you to answer one question: what are the actual consequences of each task?

Once you answer that, your list looks different. You stop trying to eliminate tasks one by one and start making deliberate choices about what to take on, what to ignore, what to throw away. Time management sounds like a grand topic, but in practice, it often comes down to starting with A-1 on an ordinary Tuesday afternoon.

In my experience, this method is low-cost and high-return. It doesn’t require software. It doesn’t require an afternoon of training. It only asks you to spend fifteen minutes tomorrow morning sorting the day. When you do, you might find that you get more done simply because you finally stopped burning energy on the stuff that should have been deleted long ago.