Zen To Done (ZTD), Made Practical
MIT focus, habit-first adoption, and simplicity as a productivity strategy
Zen To Done vs GTD: what’s the difference?
Zen To Done (ZTD) is Leo Babauta’s deliberately simplified alternative to David Allen’s Getting Things Done (GTD), and it is best understood as three lists: what it keeps, what it drops, and what it adds. It KEEPS GTD’s two load-bearing moves — capture everything out of your head into a trusted place, and define the concrete next action rather than a vague project name. It DROPS most of the machinery: the elaborate context system, the multi-list filing structure, and the expectation that you maintain a comprehensive review of everything, all of which Babauta argues is where GTD collapses for ordinary users. It ADDS two things GTD does not have. First, habit-by-habit adoption — GTD is presented as a system you install and then run, while ZTD is presented as ten habits you adopt one at a time over weeks, which is a direct response to the observation that most GTD failures are adoption failures rather than design failures. Second, a daily focus on a small set of most important tasks (MITs) chosen in advance, where GTD leaves daily selection to contexts and available time. The practical trade-off: GTD is more complete and handles a large, complex commitment load better; ZTD is easier to sustain but does less for you, and if your obligations genuinely are complex you may find you rebuild parts of GTD anyway. Both are practitioner systems, not tested protocols.
People almost always arrive at Zen To Done through GTD — usually after trying Getting Things Done and finding it did not survive contact with an ordinary week. So the useful framing is a comparison rather than a standalone description. Where GTD and ZTD agree: get everything out of your head and into a trusted external system, and turn vague commitments into a concrete next physical action. Babauta does not dispute those; they are the parts he keeps. Where they part company is on everything built on top. GTD offers a complete apparatus — contexts, someday/maybe, project lists, reference filing, a thorough weekly review — and asks you to run the whole thing for it to work as designed. Babauta’s claim is that this is precisely the failure point: not that the design is wrong, but that installing an entire system at once is a change-management problem most people lose. ZTD answers that in two ways. It replaces the all-at-once install with ten habits adopted one at a time, treating adoption as the actual problem to solve. And it replaces reactive list-working with a small number of most important tasks chosen for each day, so the day has a shape before it starts. The honest trade-off is capability for sustainability: what GTD’s machinery buys you is the ability to hold a genuinely large and complicated set of commitments without dropping any, and ZTD gives some of that up in exchange for being lighter to keep running. Below are the core practices with the mechanisms that make them work.
Practices
- Identify most important tasks (MITs) each morning
Choose one to three tasks that must happen today and do them before anything else.
- Build the capture habit before anything else
Install one habit at a time — start with ubiquitous capture — before adding other ZTD practices.
- Keep a simple, few-list system
Use the fewest lists possible — one inbox, a few context lists, and nothing elaborate.
- Do a brief weekly review and planning session
Each week, review what happened, clear the decks, and commit to next week’s MITs.
- Do one thing at a time with full focus
Work on one task at a stretch with no split attention — the Zen principle applied to execution.
- Simplify by reducing commitments
Regularly eliminate projects, roles, and obligations that don’t align with your most important work.
- Align daily work with meaningful goals
Ground your MITs and projects in goals that genuinely matter to you, not just what is urgent.
How these practices connect
Every ZTD practice reduces the cognitive load of deciding what to do next, either by pre-committing the decision (MITs, capture, simple lists) or by removing inputs to the decision entirely (fewer commitments, single-tasking, goal alignment). The system works by shrinking the number of live things competing for attention at any moment, not by helping you organize more of them.
Do I need to set up the whole ZTD system at once to get any benefit?
No, and trying to is the most common way people fail with it. ZTD is designed around installing one habit at a time, starting with the capture habit, because adding several new behaviors simultaneously overwhelms the habit-formation process before any single one becomes automatic. Someone who tries the full system in week one is following the letter of ZTD while violating its actual mechanism.
How is picking most important tasks different from just keeping a simple list?
They operate at different points in the day. The simple, few-list system (one inbox, a short next-action list, a someday list) is the structure that holds everything you could possibly do without becoming a maintenance project of its own. Choosing most important tasks (MITs) each morning is a separate, daily act of picking one to three items out of that structure and doing them before anything else, so the day's direction is set in advance rather than by whatever surfaces first.
Why does ZTD care about single-tasking when it's mostly about lists and habits?
Because naming the right task and then fragmenting your attention while doing it wastes the benefit of naming it correctly. Multitasking is neurologically serial rather than parallel, and each switch between tasks carries an attention-residue cost that degrades performance on the one you're supposed to be doing. Doing one thing at a time with full focus is the execution-level practice that protects the value created by picking most important tasks in the first place.
What's the point of a weekly review if I already do MITs every morning?
Daily MIT selection only works if the underlying lists it draws from are current, and without a regular review those lists go stale, unchecked items pile up, and the whole system stops being trusted enough to use. The weekly review clears inboxes, confirms next actions still exist for live projects, and sets next week's MITs so each morning's choice is drawn from something accurate rather than an outdated pile. It's the maintenance cycle that keeps the daily practice honest.
Isn't reducing commitments basically the same as keeping a simpler list?
No, they act on different things. A simple, few-list system reduces the overhead of tracking work you still have to do, while reducing commitments removes the work itself, permanently, rather than handling it more efficiently. The mechanism behind cutting commitments is that any system's productivity gains are capped by the sheer volume it has to process, so eliminating non-essential projects is a higher-leverage move than organizing them better.
How does 'find your passion' connect to any of the practical, list-based parts of ZTD?
It's the check that keeps the task-management machinery pointed at something worth optimizing. Naming most important tasks and running a weekly review make execution efficient, but efficient execution of a task pile that was never curated for meaning just produces faster busyness. Periodically grounding MITs and projects in goals you actually care about is what connects the task level back to the goal level, so the system serves your actual aims rather than just your inbox.
If I can only adopt one ZTD habit, which one actually matters most?
By the system's own sequencing logic, it's the capture habit, since every other practice assumes you already have a trustworthy place to put things. A simple list system needs an inbox that's actually being fed, MIT selection needs items to select from, and a weekly review needs something to review; without ubiquitous capture in place first, each of those has nothing reliable to operate on. That's also why ZTD installs capture before any other habit rather than treating all seven practices as equally foundational.
How do you choose between these?
Which practice to reach for depends on what's actually failing right now, not on what kind of person you are. If your day gets consumed by whatever shows up first, the gap is at the morning-selection point and MITs are the fix. If your lists feel untrustworthy or bloated, the gap is structural and calling for a simpler system or a weekly review to restore its currency. If you're organized but still overloaded, the volume of commitments itself is the problem, and no amount of better listing fixes that — only cutting does. If you're focused on the right task but still not making progress on it, the failure is at execution and single-tasking is the lever. And if everything is running smoothly but feels hollow, that's a goal-alignment gap, not a systems gap.
What these approaches do not settle
The clearest disagreement in the evidence is between do-one-thing-at-a-time, which has RCT-level support behind the cost of task-switching, and most of the rest of ZTD, which rests on mechanistic reasoning or observational practitioner wisdom rather than controlled trials. The weekly review's value is inferred from general planning research, not from any study of a seven-day cadence specifically — that interval is Babauta's practitioner judgment. Similarly, the 'one to three' MIT count and the claim that habits must be installed strictly one at a time are reasonable heuristics, but how much cognitive budget or simultaneous habit-formation capacity any given person actually has varies enough that these numbers shouldn't be treated as fixed limits rather than starting points.
Practice this with IX Coach
Related concepts
- Getting Things Done (GTD), Made Practical
The five steps, the next-action habit, and the science of offloading your mind
- Atomic Habits, Made Practical
The four laws, the real mechanisms, and where the science is strong
- Essentialism, Made Practical
Less but better — the disciplined pursuit of less, trade-offs, and the mechanisms
How this pairs with other practices
- Time Audit Meets Zen to Done's Small Habits
A full week logged hour by hour, and one small habit built at a time, apply the same fix to two different sizes of overwhelm.
- Use the 90-Second Rule to Protect a Single-Tasking Block
A ninety-second pause can keep a stray notification from derailing the single-tasking habit at the center of Zen to Done.
- Implementation Intentions and Zen to Done, Paired
If-then planning closes the gap between wanting and doing; ZTD sequences habits so willpower never runs out. Here's how they actually fit.
- Use Attention Management to Make ZTD Stick
ZTD tells you which task to do first. It doesn't protect the block once you're in it — that's a second, separate skill this page names.