Practitioner Craft
2026-02-20
Your inbox is not the problem. Your triage model is.
A structured email system for delivery leaders who process 200 emails a day and still need time to think.
The two-hour trap
On a multi-vendor clinical system replacement, I was averaging 200 emails a day.
Six vendors, four internal teams, a programme board, and a steering committee, all routing through one inbox. I spent the first two hours every morning reading and responding, and came out of it with nothing done. I had sent plenty of emails, but I hadn't advanced a single deliverable. Two hours of activity that felt productive but moved nothing forward. And those two hours don't come from nowhere. You don't have the luxury of blocking out the first quarter of your day for email. So the emails start before the workday and continue after it. An eight-hour day becomes ten. In reality, more.
The context-switching was the real cost. Every email that pulled me from planning mode into response mode carried a recovery penalty. Research suggests over 20 minutes to get back into deep work after an interruption.1 When your inbox generates 30 interruptions before lunch, the maths is brutal.
Email is only one channel, Teams messages, phone calls, Jira notifications, and walk-ups all compete for the same attention but it is the biggest and the most persistent. I used to think I was bad at email. Turns out I was bad at separating what needed my brain from what just needed my filing system.
Why inbox zero fails for delivery leaders
Inbox zero was designed for individual contributors with a manageable email load. A developer processing 30 emails a day can clear, file, and move on. The system works because most of those emails are actionable: a code review, a meeting invite, a question with a short answer.
PM email is structurally different. You're a hub, not an endpoint. Every workstream, every vendor, every stakeholder routes through you. The volume is not unusual. The composition is. Most of your email is informational: CCs, status updates, meeting notes, FYIs that someone sent because they thought you should know.
Inbox zero treats all of this the same: process and clear. You spend an hour clearing 50 emails and feel productive, but you have not advanced the project. You have moved messages between folders.
The real cost isn't unread emails. It's the constant switching between "respond to this" and "actually think about this." Those are different cognitive modes. Mixing them in a single inbox session guarantees you do both badly.
When inbox zero works
- You're an individual contributor
- Your email is mostly actionable
- Your team is small
When it fails
- You're a PM, programme manager, or delivery lead
- Your email is mostly informational
- You're a hub, not an endpoint
- You need a triage model, not a clearing model
The triage model
Life is sorting and filing. You do it with the dishwasher, with laundry, with bank statements. You never think about it because the system is obvious. Email is no different.
Stop treating it as a storage system and start treating it as a processing queue. A storage system accumulates. A processing queue triages.
It comes down to three categories.
Act
Needs your brain. A decision, an approval, a response that requires thought. These go into a dedicated folder and get your focused attention during processing time.
File
Reference only. You might need it later, but it doesn't need you now. File it where you will find it (by project, by vendor, by workstream) and move on. Where and how you file matters more than most PMs realise; a well-filed email is a governance record, not just a tidy inbox.
Archive
Noise. CCs that turned out to be irrelevant, newsletter-style updates, information that expired before you read it. Archive and forget.
The CC rule is the biggest time-saver: anything you're CC'd on goes into a weekly review folder automatically. If something is genuinely urgent, you should be a TO recipient, not a CC. CCs are informational by nature. They do not compete with action items for your processing time.
Time-boxing makes the triage model work. Two processing slots per day, say 9am and 2pm. Outside those windows, email is closed. This isn't about discipline or willpower. It's about protecting the hours where you do the work that actually moves the project forward.
The rhythm matters too. A daily review at the start of the day clears your Act folder and sets your priorities. A weekly review on Friday processes your CC folder, and even then, it is still just sorting and filing. Most of those CCs will resolve themselves before Friday. The ones that haven't get triaged the same way as everything else: act, file, or archive. The daily review takes five minutes. The weekly review takes 20. Both are worth far more than the time they cost, but the discipline of structured reviews is its own topic.
When to process immediately
- You're the blocker
- An approval is holding up a workstream
- A decision is needed by end of day
- A response is blocking someone else's work
When to batch
- Everything else
- Twice a day is sufficient for 95% of PM email
When I adopted this model, my morning email processing dropped from two hours to 40 minutes, and the quality of my first two hours of actual work improved measurably. Once the triage model is in place, you can systematise the processing step itself. I now use an AI-assisted sweep that converts triaged email into tasks and calendar entries, but that is a topic for a future article.
Subject line discipline: the team-level fix
Good subjects make good tracking. A vague subject line like "Re: Project update" becomes an unnavigable thread after 15 replies. You can't find the decision. You can't attribute the agreement. You can't search for it six months later when the vendor dispute lands on your desk.
Structured subject lines tell the recipient what to do before they even open the email. This is the first step toward writing for your reader, not for yourself. The subject line should serve their decision, not your update:
- FYA (For Your Action): you need to do something
- FYI (For Your Information): read and file
- FYR (For Your Records): archive, reference only
Format: FYA: Budget review - Response needed by 28 Feb
This is my system. The specific convention matters less than having one. "!Action Required:" works. "[ACTION]" works. Project codes in the subject line work. Pick a system, introduce it at a team meeting, model it yourself for two weeks. The team will follow.
When to split a thread: When the subject no longer describes the conversation. When someone replies to a budget email with a scope question, that's a new thread. Start a new email, copy the relevant context, give it an accurate subject. It takes 30 seconds and saves hours of searching later.
Thread discipline is governance. A well-structured email thread is searchable, attributable, and auditable. When a vendor dispute reaches contract negotiation, you need to find the email where the scope was agreed. Good subjects make that possible.
CC etiquette and the privacy problem
CC is not just a noise problem. It is an information governance problem.
Some conversations need to stay between specific people. CC discipline is not only about reducing volume. It's about knowing which conversations are private, which are transparent, and which sit somewhere in between.
The "reply all to a CC" cascade is the classic failure mode. Someone CCs you for information. You reply with a question. Now 15 people are in a conversation that should have been between two. Multiply this across a programme and you've created a noise factory.
When to CC: When someone needs to know this happened but doesn't need to act.
When NOT to CC: When you're covering yourself.
When to take it offline: When the email thread has become a meeting substitute. More than three back-and-forth replies on the same question means you should pick up the phone.
Ideas to try
Auto-file your CCs
Set up a rule: anything where you're CC'd (not TO) goes to a "Weekly Review" folder. Process it Friday afternoon. Most of it will have resolved itself or become irrelevant by then.
Adopt subject line prefixes
FYA/FYI/FYR is one system. "!Action Required:" is another. Pick one and model it yourself for two weeks.
Close email for two hours every morning
Process at 9am, then close it until 11am. Use that protected time for the work that actually advances the project: the thinking, the planning, the document you have been putting off.
Create a thread split habit
When a reply changes topic, start a new email with a fresh subject. Thirty seconds of effort now saves hours of searching later.
Audit your CC list before hitting send
Ask: does this person need to know, or am I covering myself? If it's the latter, the conversation you need to have isn't over email.
Your inbox will never be empty. But if it's structured, it doesn't need to be. Triage is the foundation, and once it is working, it changes how you file, how you write, and where you store the knowledge your project depends on.
Patterns in this article
- Information Fog — information exists but nobody can find it when it matters
- Compliance Theatre — governance artefacts exist but don't govern
- Gloria Mark's research at UC Irvine found it takes over 23 minutes to fully resume a task after interruption. Her book Attention Span (2023) is a good starting point if you want to understand why. ↩
This article contributes risks K1-K3, C5 to the practitioner's risk taxonomy.