PlayInfoBox

Home /Utilities /The GTD Processing Decision Tree: What to Do With Everything in Your Inbox

The GTD Processing Decision Tree: What to Do With Everything in Your Inbox

Capturing everything in one inbox is the easy part. Processing it -- deciding what each item actually means -- is where most task systems break down. Here is the decision tree that fixes that.

Process one item at a time, top to bottom

Work through your inbox in order without skipping around, and make a decision about each item before moving to the next. Skipping an item you don't feel like deciding on is how inboxes silently pile back up.

First question: is any action required?

If the item requires no action at all, it has exactly three honest destinations: the trash, a reference folder for information you might need later, or a someday/maybe list for things you might act on eventually but not now.

If it takes less than two minutes, do it now

This single rule prevents enormous backlog: a quick reply, a one-line update, or a small task takes less time to just finish than it does to write down, categorize, and revisit later.

If it's not yours to do, delegate it and track it

If someone else is better positioned to handle it, hand it off and add it to a waiting-for list with a rough date, so you have a record to follow up on if it stalls.

If it needs more than two minutes and it's yours, defer it with a real next action

Anything that takes real time gets a next action written as a concrete, physical action -- not a vague goal. "Call the dentist to reschedule" is a next action; "deal with dentist" is not, and vague phrasing is the most common reason task lists silently stop getting used.

If it needs more than one step, it's a project

Anything requiring more than a single action to complete counts as a project in this system, and every project needs its own clearly identified next action -- a project with no next action attached tends to stall indefinitely.

The point is to decide, not to organize

It's easy to confuse processing with organizing -- filing something into a neat folder can feel productive without you ever having decided what it actually requires from you. The decision tree forces the harder step first: what does this actually mean, and what, if anything, do I need to do about it?

A vague next action is the most common failure point

Task lists tend to fail quietly, not dramatically, and the most common cause is items phrased too vaguely to act on -- "plan trip" or "handle taxes" sit unfinished for weeks because they don't describe a single physical action you could start doing right now. Rewriting a stalled item as a concrete first step is often all it takes to get it moving again.

Frequently Asked Questions

What's the difference between clarifying and organizing?

Clarifying is the thinking step -- deciding whether something is actionable and what the next action actually is. Organizing is the filing step that comes after -- placing that already-decided item into the right list, calendar slot, or folder.

Do I need to process my inbox to zero every time?

Getting to a fully empty inbox occasionally is satisfying but not required -- what matters more is that everything currently in the inbox has at least been looked at and assigned a decision, even if some items end up deferred to a someday/maybe list rather than removed entirely.