'Inbox zero' has been badly implemented by everyone from productivity influencers to enterprise consultants. The failure mode: elaborate folder systems, tagging schemes, and 'process' vocabulary that no one actually follows past week two. This workflow is the minimum viable version — four buckets, drafts pre-written, follow-ups scheduled, run twice a day. If you do it consistently, inbox stays near zero without requiring willpower.
Batch into four buckets
Goal: Every email becomes one of four categories in one pass. No agonizing.
I have [N] unread emails. For each: paste the subject + first line. Categorize each into one of four buckets: (1) REPLY — needs a response from me, ≤5 minutes; (2) DELEGATE — someone else should own this, I'll draft the handoff; (3) DEFER — I need to do something (not just respond) that will take >5 minutes; add to my todo list with a proposed slot; (4) ARCHIVE — informational or done, no action. Return the classification as a table so I can approve or override in one pass.
Handoff: Do not action anything in Step 1. Just classify. Bucket everything first; then process by bucket.
Draft all REPLY responses in one batch
Goal: Same headspace, same voice, faster throughput than switching contexts email-by-email.
Draft all [N] REPLY responses. For each: paste enough context I gave you, and draft the response. Voice: dry, specific, appropriate to sender's register (formal for CFO, warm-casual for team). Keep each response ≤4 sentences unless the topic requires more. If a response requires info I don't have, draft it with a [BRACKET] I'll fill in.
Draft DELEGATE handoffs
Goal: Every delegation is a complete message — no follow-up chain because I didn't include enough.
Draft the DELEGATE handoff messages. Each includes: (1) the original context (paste of relevant email or link), (2) the specific ask, (3) the deadline, (4) the escalation path if the delegate can't do it (usually 'flag me by [date] and I'll rebalance'). Warm, brief, respectful of the delegate's own workload.
Schedule DEFERs into calendar blocks
Goal: Every deferred item has a specific time it will happen, or it's not deferred — it's abandoned.
For the DEFER items, propose specific calendar slots this week that fit their duration and priority. For each: (a) duration estimate, (b) proposed slot (based on my calendar / working style), (c) whether it needs quiet-time (analytical) or can happen in call gaps (light reading). If a slot conflicts with an existing meeting, note the conflict and propose an alternative.
Handoff: Confirmed slots go to your calendar as blocks (label: 'DEFER — [topic]'). Do them in the slot. If a slot passes without being done, that DEFER goes back into today's triage — do not silently accumulate.
Repeatability, not cleverness.
What lives where when the workflow finishes.
REPLY drafts → you review, click send. DELEGATE drafts → same. DEFER items → your calendar as time blocks. ARCHIVE → click archive. Total: 15-20 minutes twice a day (morning + late afternoon). If you're at zero unread twice a day for two weeks straight, the workflow is compounding; if you're not, either the volume is unrealistic or you're skipping Step 4 (which is the one that fails silently).
The same shape, different jobs.
- Solo founder — collapse Steps 1-2 (fewer emails); still do Steps 3-4 rigorously.
- Support-team lead — DELEGATE messages go to the on-call queue, not individual delegates; scheduling in Step 4 is team-time not personal.
- Executive assistant variation — assistant runs Step 1 solo, gets exec approval on Step 2-3 drafts, owns Step 4 scheduling.
- Weekly deep-clean — end-of-week, add a Step 5 that reviews items that were DEFERRED and never done; escalate or explicitly abandon.
Try this workflow once. Then decide if it earns a recurring slot.
The value compounds after the third run, not the first.