Productivity Systems Compared: GTD, PARA, Zen to Done and More

Which productivity system is best?

There is no best system, only a best match between the system’s primary question and your current bottleneck. If commitments slip through the cracks, you need GTD’s capture and review loop. If you cannot find anything, you need PARA. If you cannot sustain any system for more than three weeks, you need Zen to Done. If your day has no shape, the Ivy Lee method will do more in ten minutes than a full GTD setup will in a weekend.

The mistake is adopting a system because it is respected rather than because it addresses the failure you actually experience. A well-run simple system beats a badly run comprehensive one every time. A 2021 meta-analysis of time management research found moderate associations with performance and stronger associations with wellbeing, which suggests the benefit comes from the behaviour, not the sophistication of the framework.

What question does each system answer?

Read the middle column twice. Those five questions are genuinely different, and one person can have more than one of them at once — which is why hybrid setups are common and why “which system is best” is the wrong framing.

What is GTD and what does it do well?

Getting Things Done is a five-stage workflow published by David Allen in 2001: capture, clarify, organize, reflect, engage. Its central claim is that your mind is for having ideas, not holding them, so every commitment needs to live in a trusted external system. In practice that means an inbox processed to zero, context lists, a projects list for anything requiring more than one action, a waiting-for list, and a someday/maybe list. The weekly review holds it together. Without that review, the lists decay within a month and the system stops being trusted, which is the same as not having one.

Where it wins. GTD is unmatched at handling a high volume of heterogeneous commitments. If you are juggling forty open threads across six projects and three clients, the capture-and-clarify loop is what stops the low-grade anxiety of not knowing what you have forgotten. The mechanism is externalization: decisions get made once, in a defined place, instead of repeatedly in your head.

Where it fails. Two places. First, maintenance: a full setup takes hours, and the weekly review is a genuine calendar commitment. Second, prioritization: GTD deliberately avoids telling you what matters most. It will help you do things efficiently, including the wrong things.

What is PARA and when should you use it?

PARA is Tiago Forte’s four-folder structure: Projects, Areas, Resources, Archives. It sorts information by how soon you will act on it rather than by topic. A project has a goal and an end date. An area is an ongoing responsibility with a standard to maintain. Resources are topics of interest. Archives hold anything inactive.

The elegance is that it works in almost any tool — a notes app, a cloud drive, a task manager, an email folder tree — because it only requires four top-level containers. When you are unsure where something goes, the test is actionability: will you act on this in the next month? If yes, it belongs to a project. If it is an ongoing obligation, an area. If neither, a resource or the archive.

Where it wins. If your problem is retrieval — the right document, the right note, the right decision record — PARA solves it faster than any task system will. It also survives tool changes, because the structure is conceptual rather than software-specific.

Where it fails. PARA has no opinion about Tuesday. It organizes knowledge but does not schedule work, track next actions, or force a review. Adopting PARA alone and expecting your task list to improve is the most common misapplication.

What is Zen to Done and who needs it?

Zen to Done is Leo Babauta’s simplification of GTD, published in 2007. It keeps the useful mechanics, drops the elaborate lists, and — unlike GTD — adds a habit-building sequence. The ten habits include collecting, processing, planning, doing one thing at a time, using a simple system, organizing, reviewing weekly, simplifying, setting routines, and finding work you care about.

The defining rule is adoption speed: take one habit, practise it for about thirty days, then add the next. That is the whole innovation, and it addresses GTD’s real failure mode — people build the structure in a weekend and have no habits to sustain it.

Where it wins. For anyone who has abandoned a system before, ZTD’s sequencing is more valuable than any feature list. The “do one thing at a time” and daily planning habits produce visible results within a week.

Where it fails. It is lighter than GTD by design, so complex multi-project work fits less gracefully. If you genuinely have sixty open loops, the simple system overflows. It also assumes patience: the full ten habits take most of a year.

Is the Bullet Journal still worth using?

Yes, for a specific profile: someone with a moderate task volume who values handwriting, reflection, and a single place for plans and notes. Ryder Carroll made the method public in 2013. It uses rapid logging — tasks, events, and notes marked with simple symbols — plus monthly and future logs, and a migration step where unfinished items are deliberately rewritten or dropped. Migration is the secret: rewriting an unfinished task forces a decision that a digital list lets you avoid. Most people discover that a third of what they carry is not worth carrying.

Where it wins. Reflection quality, flexibility, and no notifications. The monthly migration is a natural review that many digital users never perform.

Where it fails. Search, backup, sharing, and scale. You cannot query a notebook, link a task to a document, or collaborate. Past roughly 30 tasks a week, manual migration becomes a chore and the system slips.

Does the Ivy Lee method still work?

It does, and it is the cheapest system on this list. The method is usually attributed to a 1918 consulting engagement with Charles Schwab: write six tasks for tomorrow, rank them by importance, start with the first and stay on it until done, then move to the next. Anything unfinished rolls into the next day’s list of six.

The attribution is old enough to be uncertain, but the method does not depend on its origin story. It works because it forces three decisions in five minutes: how much can I realistically do, what matters most, and what comes first.

Where it wins. Speed of adoption, zero tooling, and a natural cap on commitments. Six items is few enough that a day feels achievable.

Where it fails. It does not capture incoming work, does not handle dependencies, and offers no structure for the 200 items that are not today’s six. It is a daily planning tool, not a system.

Worked example: diagnosing the wrong system

A consultant has 62 open commitments across five clients, misses follow-ups roughly twice a month, and has tried three systems in eighteen months. Her instinct is to try a fourth.

A short audit changes the diagnosis:

The counts point to two problems, not one. Capture is broken, so the first fix is a single inbox and a weekly review — GTD’s core loop, not the full apparatus. Retrieval is second, and four PARA folders solve it in an afternoon. The daily planning gap closes with six ranked items each morning. Pick by symptom count, not by reputation.

Worked example: the maintenance budget

Systems have running costs, and that cost is the reason most get abandoned. Here is an honest annual estimate for one person.

Ninety-nine hours is roughly two and a half working weeks. That is not an argument against GTD — for someone with sixty open loops and a coordination-heavy role, it can be the best overhead they spend. It is an argument against paying GTD’s maintenance cost for a problem that four folders and six daily priorities would solve.

Worked example: migrating to PARA without losing a weekend

A marketing lead has 2,400 files and notes scattered across two drives and a notes app. A full reorganisation feels like a week of work, so it never starts.

The tractable version:

1. Create four folders. Do not create subfolders for the first month.
2. Move only active projects — usually 8 to 15 — into Projects. At 2 minutes per decision, that is 16 to 30 minutes.
3. Move ongoing responsibilities into Areas: team, budget, hiring, reporting.
4. Leave everything else where it is, and move items into Resources only when you next touch them.
5. At the end of the month, move anything untouched for a year into Archives in one bulk action.

Total first-session effort: under two hours, against an estimated 30-plus for the full migration. The remaining 2,000 files get sorted lazily, at the moment of use — which is when you actually know where they belong.

How do you combine systems without creating a mess?

Combine at most two, and give each one a distinct job. The workable patterns:

• GTD for execution, PARA for storage. The most common pairing. GTD decides what to do; PARA decides where the supporting material lives.
• ZTD habits, simple lists. Ten habits adopted slowly, one plain task list. Lowest failure rate for people who have abandoned systems before.
• Ivy Lee plus a capture inbox. Six daily priorities, one place for everything that arrives.
• Bullet Journal plus digital calendar. Paper for planning and reflection, digital for shared commitments and reminders.

What does not work is running two execution systems at once. Two task lists mean two versions of the truth, and the older one wins by default because it is the one you look at out of habit.

Why do productivity systems fail?

Almost never because the method is wrong. Four causes explain most collapses.

The maintenance exceeded the benefit. A system that costs 45 minutes a week and saves 20 will be abandoned, correctly.

The system was adopted all at once. Building every list, folder, and habit in one weekend creates a structure with no behaviour underneath it.

Nothing forced a review. Every system here depends on a recurring reflection step: GTD’s weekly review, PARA’s monthly sort, the Bullet Journal’s migration, Ivy Lee’s evening list. Remove it and the system becomes an archive of stale intentions.

The tool was chosen before the method. Buying software and then looking for a workflow to fit it is backwards. The method should survive a tool change; if it does not, it was a tool configuration rather than a system.

> Common mistake: Measuring the system by how complete it looks. A tidy set of twelve context lists is not evidence of anything. The only meaningful measures are whether you know your next action and whether the important work moves.

What are the trade-offs?

No configuration avoids all five costs. The realistic goal is to choose the cost you can pay for years, not the benefit that looks best in a screenshot.

How do you keep a system running with a team?

Individual systems break at the team boundary. Your GTD next-action list is private, so nobody knows what you committed to. Your PARA folder is private, so the document you filed neatly is invisible to the person who needs it.

The fix is a shared layer that mirrors the individual logic: commitments captured with an owner, project material living next to the work, and one recurring review the team actually runs. In Doitify, tasks and sub-tasks carry owners and due dates, projects hold their documents and meeting notes, and reports show progress without anyone assembling a status deck. Sprints and backlog views give recurring work a review rhythm, and the AI Copilot can turn a captured goal into a structured plan.

Doitify is our product, so read that as disclosure. If you work alone and your volume is low, the Ivy Lee method plus a notes app will outperform any platform.

Conclusion

The systems compared here are not competitors on a single ranking. GTD is an execution engine, PARA is a filing system, Zen to Done is an adoption strategy, the Bullet Journal is a reflection practice, and Ivy Lee is a daily planning shortcut. Choosing between them without knowing which question you are answering is why so many people cycle through all five.

So run the diagnosis first. Count your open loops, time how long it takes to find a document, and check whether you had a plan before 10 a.m. this week. The counts will point at one or two gaps. Fix those with the smallest system that covers them, run it through a busy month, and only then add a second layer. A modest system you trust beats an elegant one you abandon.

If this post on productivity systems was helpful, you might also enjoy How to Reduce Meeting Overload and Time Blocking vs Time Tracking: What’s the Difference and Which Should You Use?.