Getting Things Done – VisualReads

The Core Promise

Your mind is for
having ideas, not
holding them.

The source of stress is not having too much to do. It is keeping track of too much to do in your head.

Allen's central insight is deceptively simple: the human mind is a terrible filing system. When you try to remember everything you need to do, every incomplete task stays active in your mind as an 'open loop' – constantly consuming processing power in the background, creating low-level anxiety even when you're not consciously thinking about it. The solution is not to do more or work faster. It is to capture everything in a trusted external system, so your mind is free to focus on actually doing things rather than desperately trying not to forget them. This is the promise of GTD: not productivity, but clarity.

In practice

For the next 30 minutes, do a complete brain dump. Write down every single thing you're trying to remember – every task, project, commitment, idea, and worry. Don't organise it yet. Just get it all out of your head and onto paper or into a notes app. Notice how your mind feels afterward.

Cross-references

→

Deep Work – Newport – cleared mental space enables deep focus

→

Essentialism – McKeown – deciding what matters before capturing everything

↔

The 48 Laws of Power – Greene – keeping plans in your head as strategic concealment

Once you have a trusted capture system → the next challenge is processing what you've captured. Which requires...

↓

The Two-Minute Rule

If it takes less
than two minutes,
do it now.

The cost of deferring a small task is almost always higher than the cost of doing it immediately.

Allen's most immediately actionable principle: if a task can be completed in two minutes or less, do it the moment it appears rather than adding it to a list. The reasoning is practical – the overhead of capturing, organising, reviewing, and re-deciding to do a small task often takes longer than just doing it. Email replies, quick calls, simple decisions: doing them now eliminates the mental residue they would otherwise leave. The two-minute rule is not about being busy – it is about recognising that some things cost more to manage than to complete.

In practice

For one full day, apply the two-minute rule strictly. Every time a task arrives – an email, a request, a small decision – ask: can this be done in two minutes? If yes, do it immediately. If no, capture it in your system. At the end of the day, notice whether your to-do list is shorter or longer than usual.

Cross-references

→

Atomic Habits – Clear – habit stacking and immediate action

→

Essentialism – McKeown – the cost of saying yes to everything

↔

Deep Work – Newport – constant task-switching undermines depth

With small tasks handled immediately → the next step is deciding what to do with everything else. Which means...

↓

Next Actions

Projects don't
get done. Next
actions do.

The reason tasks stay on lists forever is that 'write report' is not an action. 'Open document and write first paragraph' is.

One of GTD's most practically powerful distinctions: a project is any outcome that requires more than one action. Every project must have a defined next physical action – the very next thing you would do if you sat down to work on it right now. 'Plan the presentation' is not a next action. 'Open PowerPoint and create title slide' is. This distinction matters because the mind procrastinates on vague commitments and acts on clear steps. When you review your list and see 'write report', your brain has to re-decide what to actually do every time. When you see 'open document and write the executive summary', the decision is already made.

In practice

Go through your current to-do list. For every item that is actually a project (requires more than one step), identify and write down the very next physical action. Be specific: what app, what file, what call, what decision? Notice how your resistance to those tasks changes.

Cross-references

→

Atomic Habits – Clear – making the next action obvious reduces friction

→

Deep Work – Newport – clear tasks enable deep focus sessions

↔

Essentialism – McKeown – fewer projects done completely vs. many projects stalled

With next actions defined → the question of when to do them requires a review system. Because...

↓

The Weekly Review

The system only
works if you
trust the system.

A capture system that is not reviewed regularly becomes another source of anxiety rather than relief.

Allen identifies the weekly review as the most critical – and most commonly skipped – element of GTD. The weekly review is a dedicated block of time, typically 1–2 hours, in which you clear your inboxes, review all your projects and next actions, and update your system to reflect current reality. Without it, the system gradually falls out of sync with your actual commitments, and you stop trusting it. And the moment you stop trusting it, your mind starts trying to hold everything again – and the open loops return. The weekly review is not a productivity technique. It is the maintenance that makes everything else possible.

In practice

Block 90 minutes in your calendar for this week – call it 'Weekly Review'. During that time: clear your email inbox to zero, review every project and confirm it has a next action, capture anything still in your head. Do this every week for a month and notice how your baseline anxiety level changes.

Cross-references

→

Principles – Dalio – systematic reflection as continuous improvement

→

Essentialism – McKeown – regular review to eliminate what no longer matters

↔

The Power of Habit – Duhigg – habits require consistent cues and routines

With a reliable review process → the question is how to organise what you're tracking. Which requires...

↓

Contexts

Organise by context,
not by project.

You don't do projects. You do actions. And actions happen in specific contexts – at a computer, on the phone, at home, in a meeting.

GTD's organisational innovation: instead of grouping tasks by project, group them by the context in which they can be done. A '@computer' list contains everything that requires a computer. A '@calls' list contains everything that requires making a phone call. A '@home' list contains everything that can only be done at home. The advantage is efficiency: when you sit down at your computer, you scan only the '@computer' list rather than sorting through all your tasks. When you're waiting in a queue, you check '@calls'. You match your available energy, time, and tools to the right task at the right moment.

In practice

Reorganise your current task list into context categories. Start with three: @computer, @calls, @errands. Assign every task to a context. For one week, only look at the relevant context list when you're in that context. Notice how much mental energy you save by not re-reading irrelevant tasks.

Cross-references

→

Deep Work – Newport – environment design for focused work

→

Atomic Habits – Clear – environment design reduces decision fatigue

↔

Essentialism – McKeown – context-switching as the enemy of depth

With contexts established → the hardest part of GTD is letting go of the feeling that you should be doing something else. Which requires...

↓

The Horizons of Focus

Tasks make sense
only in the context
of goals.

A perfectly organised task list with no connection to what actually matters is just very efficient busyness.

Allen's most philosophically significant contribution: GTD is not just a task management system – it is a framework for aligning daily actions with longer-term meaning. He describes six 'horizons of focus': the immediate next actions, current projects, areas of responsibility, one to two year goals, three to five year vision, and life purpose. Most people live only at the bottom two levels, managing tasks and projects with no connection to why they matter. The weekly review should include not just a scan of next actions but a periodic look at the higher horizons – to ensure that the busyness is pointed in the right direction.

In practice

Write down your answers to three questions: What are my main areas of responsibility right now? What do I want to be different in two years? What kind of person do I want to be? Now look at your task list. Is what you're doing daily connected to those answers? Identify one task you could add and one you could drop.

Cross-references

→

Essentialism – McKeown – the essential intent as the north star

→

Man's Search for Meaning – Frankl – meaning as the context for daily action

↔

The 48 Laws of Power – Greene – long-term positioning over short-term task management

With horizons of focus established → the final question is whether the system actually reduces stress. Which depends on...

↓

Trusted System

You can only
relax about what
you've captured.

The goal of GTD is not to get more done. It is to feel appropriately relaxed about everything you're not doing right now.

Allen's most counterintuitive claim: the purpose of a productivity system is not to maximise output but to create what he calls 'mind like water' – a state of calm readiness in which you can respond appropriately to whatever appears without being distracted by everything else. When your system is complete and trusted, you can focus fully on what you're doing without nagging anxiety about what you're not doing. You know that everything is captured, that nothing is being forgotten, that the next review will catch what needs catching. This is not complacency – it is the foundation of genuine sustained performance.

In practice

After completing a full GTD setup – capture, process, organise, review – sit quietly for five minutes and notice your mental state. Are there still things nagging at you? If yes, they haven't been captured. Add them. Repeat until the nagging stops. That feeling of quiet is what the system is designed to produce.

Cross-references

→

Deep Work – Newport – cognitive freedom enables sustained depth

→

Mindset – Dweck – growth requires being fully present without rumination

↔

The Power of Now – Tolle – present-moment awareness vs. systematic capture