Process inboxes sequentially top-to-bottom, never cherry-picking — skipping difficult items creates a permanent maybe pile

Why This Is a Rule

Cherry-picking creates a toxic dynamic: you process the easy items (quick replies, simple decisions, clear actions), skip the hard items (ambiguous requests, uncomfortable decisions, complex responses), and after each processing session the inbox shrinks in quantity but concentrates in difficulty. The remaining items are all the ones you've repeatedly skipped — the "maybe pile" of deferred decisions that never gets processed because it's 100% hard items by the time you face it.

Sequential processing — top to bottom, no skipping — prevents this concentration effect by forcing you to handle each item in the order it appears. You can't get to the easy item below until you've dealt with the hard item above. This constraint converts the processing session from "handle easy things" (which feels productive but leaves the hard things indefinitely) to "handle everything" (which is actually productive).

The mechanism is a forcing function: the sequential constraint removes the escape route of "I'll deal with this later." For each item, you must make a decision right now: act on it, delegate it, defer it with a specific date, or delete it. "Skip" is not an option. This is David Allen's GTD processing workflow applied as a discipline rule.

When This Fires

• During any inbox processing session (email, physical inbox, notes inbox, task inbox)
• When your inbox has a chronic tail of items that never seem to get processed
• When inbox processing sessions clear 80% of items but the same 20% persists for weeks
• Complements Batch tasks by cognitive context (communication, financial, scheduling), not by arrival order — minimize context-switching within processing blocks (batch by cognitive context) with the within-batch processing discipline

Common Failure Mode

The growing "bottom of inbox" pile: items that have been in the inbox for weeks or months, skipped every processing session because they require a difficult decision or an uncomfortable action. Each skip reinforces the avoidance, making the item feel harder than it actually is. The pile grows, the guilt grows, and eventually the entire inbox becomes aversive.

The Protocol

(1) During inbox processing, start at the top item. Do not scan ahead for easy wins. (2) For the current item, make one of four decisions: Act (if under your dispatch threshold — Calibrate your personal do-it-now threshold: set it where management overhead equals execution cost, not at an arbitrary 2 minutes), Delegate (if someone else should handle it), Defer (schedule a specific date to handle it — put it in your task system with a date), or Delete/archive (if no action is needed). (3) Do not move to the next item until you've made a decision on the current one. "Skip" is not a valid decision. (4) If an item genuinely requires information you don't have, defer it with a specific follow-up action: "Email X to get the information I need to decide this." The item leaves the inbox and enters the task system. (5) At the end of processing, the inbox should be empty. Every item has been decided, not just the easy ones.