Getting things done (Allen)
How can getting things done (allen) improve people, teams, or organisational effectiveness?
Contents
Management consultant David Allen developed a cult following in the US when he published his ideas on personal organisation.
Getting Things Done, or GTD, is David Allen’s personal workflow method for moving commitments out of memory and into a trusted external system. It helps clarify what each item means, where reminders belong and what action is appropriate now.
When to use it
- Use GTD when tasks, email, ideas, meetings and unfinished commitments compete for attention, or when an existing list does not distinguish projects, next actions and reference material.
Origins
Management consultant David Allen developed GTD through decades of productivity coaching and presented it to a broad audience in Getting Things Done. The method combines familiar practices—capture, triage, filing, review and action—into a coherent workflow. Its central claim is practical rather than magical: the mind can focus more effectively when it is not being used as an unreliable reminder system.
What it is
The current GTD vocabulary describes five recurring practices:
- Capture: collect what has your attention.
- Clarify: decide what each item means and whether action is required.
- Organise: place reminders and support material in the right system.
- Reflect: review and update the system often enough to trust it.
- Engage: choose and complete appropriate work.
A project is any outcome requiring more than one action. The system therefore separates desired outcomes from the next visible, physical step that can move each outcome forward.
How to use it
Capture. Gather commitments, ideas, messages and loose material into a small number of reliable inboxes. Capture is temporary; an inbox becomes clutter if it is never clarified.
Clarify. Process each item. If no action is needed, discard it, keep it as reference or place it on a someday/maybe list. If action is required, define the intended outcome and next action. Complete very short actions immediately when that is genuinely efficient; otherwise delegate them or defer them to the appropriate list or calendar.
Organise. Keep distinct homes for trash, someday/maybe items, reference, projects, project support, waiting-for reminders, calendar commitments and next actions. Put only time-specific commitments on the calendar. Organise next actions by context when location, tool or person limits what can be done.
Reflect. Review the system regularly. A weekly review commonly includes clearing inboxes, updating project outcomes and next actions, checking waiting items and scanning the calendar. The review is what converts a set of lists into a trusted system.
Engage. Choose work from the available actions according to context, time, energy and priority. Balance predefined work with unexpected work and the work of clarifying new inputs.
Start with one complete capture, but implement the method proportionately. A light system that is reviewed consistently is more useful than elaborate software that becomes another maintenance burden.
Final analysis.
GTD reduces ambiguity by requiring a concrete next action and a dependable reminder. It does not determine which goals matter, protect time automatically or resolve excessive workload. Those choices still require strategy, boundaries and negotiation.
The method asks for an initial setup investment and continuing discipline. Its value comes from reliability, not from adopting every category exactly. Simplify the system while preserving capture, clarification, review and an explicit link between projects and next actions.
Top practical tip
Begin with one trusted inbox and one weekly review. For every active project, write the desired outcome and the next visible action. This small implementation delivers most of the clarity while you learn which additional lists or contexts are genuinely useful.
Top pitfall
Do not confuse maintaining the system with doing meaningful work. Endless capture, tagging and list refinement can become productive-looking avoidance. Keep the tool simpler than the work, delete stale commitments and use higher-level priorities to decide what should not be done at all.
Further reading
Allen, D. (2002) Getting Things Done: How to achieve stress-free productivity. London: Piatkus. Rather ironically, there is a summary of Allen’s book for those who don’t have time to read the complete book: Shortcut summaries (2012) Getting Things Done: A time saving summary of David Allen’s book on productivity. CreateSpace Independent Publishing Platform (online).