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.