--- name: 3-21-0-inbox-system description: Use when someone wants a daily email routine of three inbox sessions of 21 minutes each that end at zero, with the inbox ignored in between, known as the 321zero or 3-21-0 method. Distinct from [[inbox-cleanup]] (a one-off backlog clearance, not a daily routine), [[focus-blocker]] (blocks distractions rather than scheduling email), and [[text-shortcut-system]] (speeds up the replies written during sessions). --- # 3-21-0 Inbox System The 3-21-0 method, also written "321zero", is an email routine: check the inbox in three sessions a day, spend 21 minutes in each, and finish each session with the inbox at zero. Between sessions, ignore the inbox. It is described on the Happy blog as "321zero" (see Learn more). This skill adapts the routine to one person's day and writes it down. ## Input required - **Daily rhythm**: working hours, meetings, and when attention is best. - **Email load** and how fast replies are expected by colleagues or clients. - **Accounts and devices** that receive mail. - **Tools** for filters, labels, and snoozing. - **Starting state**: if the inbox already holds a large backlog, clear it first with [[inbox-cleanup]]. ## Questions to ask first Ask in **one batch of at most five questions**, skipping any already answered: 1. What are your working hours, and when are natural breaks? 2. How quickly must people hear back from you, and are there urgent senders who need a separate route? 3. Is your inbox currently near empty or carrying a backlog? 4. Which tasks hide in your mail that belong on a task list? 5. Can you turn off email notifications on your devices? ## Method 1. **Understand the parts.** Three sessions per day, 21 minutes each, and zero as the end state of every session. Outside the sessions the inbox stays closed. 2. **Define zero.** Zero means every message has been processed, not that every message has been answered. Each one is replied to, done, delegated, deferred to a task list or calendar, archived, or deleted. A message that needs real work is moved out of the inbox with a note of the next action. 3. **Place the three sessions.** A common default is early in the working day, around midday, and near the end, but fit them to the user's schedule. Put them in the calendar as recurring blocks. 4. **Set a timer.** The 21 minutes are a boundary. Process messages one at a time, oldest or newest first as the user prefers, and stop when the timer ends even if the inbox is not empty. If it regularly is not, adjust the load rather than the length: filters, unsubscribes, or an earlier triage rule. 5. **Apply a decision rule to each message.** - Takes about two minutes or less: do it now. - Needs more: capture it as a task with a date, then archive the mail. - Not for you: forward or delegate. - Information only: read, then archive. - Junk: unsubscribe through the service's own control, or mark as spam. 6. **Ignore the inbox between sessions.** Turn off badges, pop-ups, and sounds. Close the mail client or tab. Agree an urgent route (a phone call or chat message) with the few people who truly need one. 7. **Tell others.** Colleagues may expect quicker replies. Share the schedule, or add it to an auto-reply or signature, so silence is not misread. 8. **Review after two weeks.** Check which sessions were skipped, which overran, and which messages kept slipping. Adjust times or filters. Use [[text-shortcut-system]] to speed up repeat replies. ## Output format - **Schedule:** the three session times with calendar entries. - **Zero definition** in the user's words. - **Decision rule** for each message, on one card. - **Notification changes** and the urgent route. - **Message to colleagues** (a few lines). - **Two-week review questions.** ## Ground rules - **Do not claim an inventor or research.** Cite only that the routine is described as "321zero" on the Happy blog and is also called the 3-21-0 method. - **Zero is processed, not answered.** Make sure the user does not read it as an obligation to reply to everything. - **Fit the job.** Roles with real-time email (support, on-call) may need more sessions or an exception; say so rather than force the rule. - **Never ask for message contents** with sensitive data, or passwords. - **Keep urgent routes.** Do not leave people unable to reach the user in an emergency. ## Self-check before answering - Are there exactly three sessions, each 21 minutes, with calendar times? - Is "zero" defined as processed, not answered? - Is there a decision rule and a place for tasks that leave the inbox? - Are notifications off and an urgent route set? - Did I keep this distinct from a one-off backlog cleanup? ## Common pitfalls - **Treating the inbox as a task list** — tasks need their own list. - **Checking between sessions** — the rule collapses into constant monitoring. - **Starting with a huge backlog** — the first sessions never reach zero. - **Skipping the explanation to colleagues** — slow replies cause friction. - **Using zero as a measure of worth** — the aim is calm and reliability. - **Letting sessions run long** — the boundary is the point. ## Example prompt > I want to try the 3-21-0 method for email. I work 9 to 5 with meetings > most afternoons. Set up three 21-minute sessions, tell me how to define > zero, what to do with messages that need real work, and how to explain > it to my team. ## Learn more - Happy blog, "321zero: how I solved my email overload", , the source describing the routine. - [[inbox-cleanup]] for clearing a backlog before starting. - [[text-shortcut-system]] for faster replies inside the 21 minutes. - [[focus-blocker]] for keeping other distractions out of the gaps.