A chief of staff at a growth-stage company sees 280 to 350 emails a day. A head of operations at a mid-market firm, similar. A COO at a 500-person company, sometimes more.
This is not the inbox of a normal knowledge worker. It is the inbox of the person whose job is to know what is happening across the entire company.
If you are an operator, you cannot inbox-zero your way through 300 daily emails by typing faster. You have to triage at scale.
What operators are actually doing in email
Operators are pattern-matching, not replying. The job is:
- Spot the three threads where something is going wrong.
- Spot the two threads where a decision is needed from above.
- Push everything else to the right person.
- Not get pulled into the noise.
Most operators we talked to said the same thing in slightly different words: “I do not need to reply to most of my email. I need to know what is in it.”
This is a different problem from the founder's “reply to the seven that matter.” The operator's problem is “scan 300 fast enough to spot the seven that matter.”
The three-pass scan
Every operator we watched used some version of this.
Pass one (5 minutes): subject lines and senders only. Skim the entire inbox by sender and subject. Do not open anything. Tag mentally: known sender, known topic, no surprise. Anything that surprises you, mark for pass two.
Pass two (15 minutes): open the surprises. Read just the first three sentences of each surprise. Tag: needs reply now, needs delegation, FYI, false alarm. Reply to the “needs reply now” immediately, in two sentences. Delegate the rest.
Pass three (10 minutes): the regular queue. Skim the known-sender threads at high speed. Most are status updates that do not need you. Archive without reading the bodies. Reply only to the ones that ask a direct question.
Total: 30 minutes for 300 emails. Operators who run this religiously have time left for the actual job.
The delegation discipline
The real superpower of an operator is delegation. Not the meeting kind. The email kind.
When a thread is asking a question that is not for you, the rule is: do not just forward. Forward with one sentence. “Sara, this is yours, please respond by EOD Tuesday.”
This adds 10 seconds. It saves Sara 5 minutes of wondering whether you wanted her to reply or just FYI.
Operators who do this well train their teams to operate without them. Operators who do not, become the bottleneck for every decision.
What “needs reply” means for an operator
Operators reply to roughly 15 percent of their inbox. The 15 percent breaks into three buckets.
- Decisions only the operator can make. Vendor contract terms, hire approvals, internal escalations.
- External representations. A customer or partner needs an answer from someone senior.
- Personal capital. A relationship that needs maintenance: a board member, an old colleague, a mentor.
If a thread does not fit one of these three, it should not get a reply from the operator. It should be delegated, archived, or read for context.
Most of an operator's inbox is information, not work.
What operators ignore
The category we see most often misused: long internal threads CC'd to the operator out of caution. The team copies you because they are not sure you want to be in the loop.
Two moves.
One: ask once, in a team channel, “please do not CC me on routine ops threads. I will catch up at the weekly review.” Most teams comply within a week.
Two: if you are still on long internal threads, mute them. Most clients support muting a thread so it does not bother you again. STAMP does this with M.
After a month of consistent muting, internal noise drops by half.
The weekly synthesis
Operators benefit from a weekly synthesis email that turns 300 emails a day into a one-page mental model.
A typical synthesis covers:
- Three things going better than last week.
- Three things getting worse.
- Two decisions waiting on someone else.
- One pattern across customer feedback.
This synthesis is for the operator, not for anyone else. It is the moment they catch what daily triage missed. Forty minutes on Friday afternoon. Worth its weight.
What STAMP ships for operators
Three operator-specific behaviors:
- Sender clustering. Threads from the same team or topic group together. You see “15 threads about Q3 budget” as a unit, not 15 separate items.
- Decision detection. Threads that contain a question with your name attached get tagged “Decision needed.” Saves the “am I being asked or just looped in” cognitive load.
- Delegation snippets. One-keystroke shortcut to forward with a templated “please respond by [time]” sentence.
These are mundane. They save operators between 30 minutes and 2 hours a week. We have data.
A typical operator day with STAMP
Real example. Chief of staff, 250-person company, $42M ARR.
8:42 a.m. Coffee. Open STAMP. Headline: “Working late, Priya. 9 need attention.”
- Top: CEO forwarded a board question. Tagged Decision needed VIP. Reply with a draft. 5 minutes.
- Next: Head of Sales asking for a customer escalation. Tagged Reply needed. Decide and delegate. 90 seconds.
- Next: a vendor contract amendment. Tagged Decision needed. Sign and reply. 3 minutes.
- Next: 12-thread cluster about Q3 hiring. Skim. Note one thread to follow up. Archive the rest as a unit.
- Next: 14 newsletters and digests. Quietly out of sight. Friday afternoon problem.
26 minutes. 9 threads handled. 280 read for context, no reply needed. The day starts with focus.
Where to go from here
For the broader system, the founder's email triage system. For the philosophy, email triage — the missing layer.
Triage at operator scale. hello@stamp.email