How I Clear My Emails and Get to Inbox Zero
Based on Tiago Forte's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Start the weekly review with a short checklist, then process email as part of that routine rather than as an open-ended task.
Briefing
Inbox zero isn’t achieved by “working through” email—it’s achieved by treating every message as a notification that must be converted into a single next action (or discarded/parked) within seconds. Tiago Forte’s weekly review workflow starts with a five-item checklist, then moves into email using a strict decision-first approach: read the oldest messages first, identify what each email is asking for, and immediately route that outcome into a task system or a “save for later” reading queue. The key safeguard is avoiding action-taking inside the inbox itself, which otherwise turns email into a time sink.
The process begins with a digital weekly review checklist on a Mac sticky note. From there, Forte opens Superhuman (with Gmail as the comparable model) and sorts messages in reverse chronological order—but intentionally starts at the bottom to work through the oldest emails first. He estimates only a few days’ worth are pending, and for each email he focuses on one question: what action does this message require? He draws a hard line between deciding and executing. If someone needs a quick reply, the reply becomes a task; if the email is informational, it gets archived. This distinction prevents “firefighting” behavior where the inbox becomes a project.
To capture actions without leaving the email context, Forte uses Things as a task manager and a Things “quick capture” extension. A keyboard shortcut pops up a small capture window directly over the current screen, letting him attach the relevant email thread via a link. He types a minimal task label—often just enough for future recall—then returns to the inbox. Once captured, he archives the email with a single keystroke (E), moving to the next message. The workflow repeatedly demonstrates how little detail is required at this stage: “reply to Dan’s email about bundling our subscriptions,” “review mentor program retrospective,” or “tests new DSLR setup and give recommendations to Joe.”
When emails are not actionable but worth reading later, he routes them to Instapaper via a browser extension, building a separate reading list for phone or tablet time. Newsletters and long threads get scanned briefly for relevance, then archived or saved. Forte also highlights a pattern-recognition benefit: by moving quickly, related issues surface across different emails—such as multiple requests tied to reorganizing shared Google Drive folders—so he can consolidate follow-ups (e.g., talk to Bethenny) rather than handle each message as an isolated one-off.
The workflow extends beyond email into batching and routing: recordings are captured as “listen to interview recording” tasks rather than played immediately; meeting logistics are archived if irrelevant; and a conference-related email is forwarded to Evernote using its dedicated email address. Even file delivery is handled efficiently—when a signed contract arrives, he downloads it and archives without extra steps.
By the end, Forte frames email as a notification system rather than a workspace or project management tool. The practical takeaway is that inbox zero becomes repeatable when each message is converted into either (1) a single captured task, (2) a “save for later” item, or (3) an archive—fast enough to keep attention on meaningful work elsewhere.
Cornell Notes
Inbox zero is reached by converting each email into a single outcome—task, saved reading, or archive—without doing the work inside the inbox. Forte starts with a weekly review checklist, then processes email from the oldest messages first to ensure nothing is missed. For every message, he decides what action it requires, captures that action in Things using a quick-capture shortcut that links back to the email thread, and immediately archives the email with a keystroke. Informational items get archived; newsletters and articles get saved to Instapaper; long recordings become “listen later” tasks; and some content is forwarded to Evernote. The payoff is speed plus pattern recognition, letting related issues get consolidated into fewer follow-ups.
Why does Forte process email from the oldest messages first instead of starting at the top of the inbox?
What’s the practical difference between “deciding” what to do and “taking action” on an email?
How does quick capture prevent context switching while turning emails into tasks?
What does Forte do with emails that are interesting but not actionable right now?
How does moving quickly through email help with organizing work beyond individual replies?
What routing shortcuts does he use for specific content types?
Review Questions
- When processing an email, what single question should determine whether it becomes a task, a saved item, or an archive?
- How does capturing a task with a link back to the email thread change what you do next?
- Give two examples of content that Forte routes to a “later” system instead of handling immediately, and explain why.
Key Points
- 1
Start the weekly review with a short checklist, then process email as part of that routine rather than as an open-ended task.
- 2
Work through the oldest emails first to avoid missing older obligations while newer messages accumulate.
- 3
Treat email as a notification system: decide the next action, capture it, and archive—don’t execute inside the inbox.
- 4
Use a quick-capture workflow (Things quick capture) that links each task back to the originating email thread for fast future recall.
- 5
Route non-actionable but valuable items to a separate reading or storage system (Instapaper for articles/newsletters; Evernote for forwarded content).
- 6
Batch complex work by capturing it as a “do later” task (e.g., listening to recordings) instead of starting it immediately.
- 7
Move quickly enough to spot repeated themes across different emails, enabling consolidation of related follow-ups into fewer tasks.