Getting Things Done

"What's the next action?" is the master question. Allen's most powerful tool is deceptively small. Most stuck items are stuck because no one decided the very next visible, physical behavior required. "Get a tune-up" is not actionable. Trace it back: you need to call the garage, but you lack the number, so the real next action is "Call Fred for the garage's number." That tiny decision is what most people never make until a crisis forces it.

Things rarely get stuck for lack of time. They stick because the doing has not been defined. When you have already determined the next action, you can exploit a fifteen-minute window with low energy to knock out a phone call instead of staring at an amorphous "project" and freezing. Deciding actions when things appear, rather than when they explode, is the efficiency revolution at the heart of the method.

Workflow is a chain only as strong as its weakest link. Allen breaks knowledge work into five distinct stages most people blur together:
1. Collect everything that has your attention into trusted in-baskets.
2. Process what each item means and whether it is actionable.
3. Organize results into the right "buckets" (lists, calendar, files).
4. Review the whole system regularly so you trust it.
5. Do, by making confident in-the-moment choices.

Most people fail at collection (leaks everywhere) or review (the system goes stale). The crucial discipline is keeping these stages separate. When you sit down to "get organized," you usually try to do all five at once, which is why list-making feels futile. You cannot organize an incoming pile, you can only capture it, then process it item by item, deciding and dispatching each before moving on, never returning anything to the in-basket.

The efficiency cutoff rule. When processing your inbox, if the next action will take two minutes or less, handle it immediately. The logic is purely economic: storing and tracking a tiny task costs more time and energy than just finishing it. Below roughly two minutes, deferral is wasteful overhead.

Allen recounts a software executive drowning in 300 emails a day who worked entire weekends to catch up. After clearing his 800-item backlog (much of it deletable, much of it two-minute replies), he never let his inbox exceed a screenful again. His staff joked he was "made of Teflon" because his response time collapsed. The rule scales with your window: with a long open block, stretch the cutoff to five or ten minutes; in a time crunch, shrink it to thirty seconds. The point is to stop re-handling trivial things repeatedly.

Match tasks to where you actually are. Allen rejects the traditional daily to-do list as demoralizing, because shifting priorities and constant new inputs make a pre-written daily plan obsolete by mid-morning, forcing endless rewriting. Instead, sort next actions by the tool, place, or person each one requires: "Calls," "At Computer," "Errands," "Agenda for boss," "At Home."

Why context first? Because it is the first real constraint on what you can do. Stuck in traffic, you can only pull up your "Calls" list. The calendar becomes sacred and minimal: only time-specific commitments, day-specific commitments, and day-specific information go there, nothing else. Everything written on the calendar must happen that day or not at all. This protects the calendar's trustworthiness and frees the rest into "as soon as I can" context lists you scan when the right window and energy appear.

Get clean, clear, current, and complete every week. Allen calls this the critical success factor, the practice that separates people who thrive on the system from those who let it rot. Once a week, block roughly two hours (he favors Friday afternoon) to gather loose papers, process all notes, empty your head, review every project for a defined next action, and scan your waiting-for and someday lists.

He offers a vivid analogy: most people feel best about work the week before vacation, not because of the trip but because they clean up, close loops, and renegotiate every agreement. The weekly review simply does this every seven days instead of once a year. Without it, your lists fall behind reality, your brain stops trusting the system, and it resumes the exhausting job of remembering. Trust is geometric: the more complete the system, the more you rely on it, the more motivated you are to keep it complete.

Five phases mirror how you decide dinner. Allen observes that your mind plans effortlessly all day and reverse-engineers that into a model. Choosing a restaurant, you move through: purpose (hunger, celebration), principles (your standards for food and cost), vision (imagining the pleasant evening), brainstorming (what time, is it open, who comes), organizing (sequencing the steps), and next action (call to book).

He contrasts this with "unnatural planning," the meeting that opens with "So who's got a good idea?" before anyone has clarified why they are there. That question only works when you are about 80% through your thinking. And he blames "reactive planning," the crisis cycle where people work harder, then get organized, then brainstorm, then finally hire a consultant who asks the obvious: what are you actually trying to do? The reactive cycle is just the natural model run backwards under pressure.

If filing takes over a minute, you'll stack instead. Allen is unusually fierce about reference filing because he found it to be the single biggest bottleneck in most people's systems. The principle: any single piece of paper must be fileable in under sixty seconds, or you will pile it and go numb to the pile. His prescriptions are concrete and slightly obsessive:
1. Keep files within arm's reach, not across the room.
2. Use one simple A-Z alphabetical system, not categories.
3. Own a label maker and keep it on your desk.
4. Keep drawers under three-quarters full and stocked with empty folders.
5. Purge once a year.

The deeper logic is friction. Reference material has no action attached, so it should add zero psychic weight, just a neat-edged library. But the slightest inconvenience converts good intentions into chaotic stacks, which then blur the line between actionable and non-actionable items and numb the whole system.

Priorities live at different heights. Allen maps work onto an aviation metaphor with six horizons:
1. Runway: current actions.
2. 10,000 feet: current projects.
3. 20,000 feet: areas of responsibility (your "hats").
4. 30,000 feet: one-to-two-year goals.
5. 40,000 feet: three-to-five-year vision.
6. 50,000+ feet: life purpose.

Logically, priorities should flow top-down: your purpose should govern your projects. But Allen makes a contrarian practical case for working bottom-up. When you are buried in unprocessed runway-level chaos, you cannot think clearly about vision, and top-down planning just raises your standards and adds more to an already overwhelming list. Get control of the mundane first, clear the psychic decks, and the elevated thinking emerges naturally. He notes executives who spend a day clearing their desks often spend that evening having visions about their company's future.

One question forces clarity, accountability, and momentum. Allen learned this technique from his mentor Dean Acheson (no relation to the statesman), who would pick up each paper on an executive's desk and demand the very next physical action. Applied across a team, the question becomes a cultural standard with outsized effects.

He argues meetings routinely end with a vague sense that something should happen and a quiet hope it is not your job. He forces the question twenty minutes before any meeting ends, and finds it usually takes those full twenty minutes to answer honestly. The query does four things: it creates clarity (forcing real decisions), accountability (whose ball is it?), productivity (resources allocated upfront, not in crisis), and empowerment (it undercuts the victim mentality, since complaining about something means you believe it could be changed, and the action question calls that bluff).