The Rule of Seven
When an email thread hits seven replies without resolution, stop typing and get on a call.
- Difficulty
- Starter
- Time to result
- ~days to results
- Steps
- 3
- Confidence
- 90%
A hard stopping rule for asynchronous communication: once a thread crosses a set number of back-and-forth emails without converging, escalate the medium instead of adding another message. It replaces the slow death of a non-converging thread with a synchronous conversation that actually resolves the issue. The threshold is a dial you tune to org size.
Origin
Shweta Shrivastava's own rule, developed at a prior company and adapted at Waymo. She calls it 'the rule of seven.'
Core principles
- 01Long email exchanges that don't converge waste many people's time
- 02Set an explicit cap on thread length before switching to synchronous
- 03Adding more people to a stuck thread makes it worse, not better
- 04The threshold scales with company size (looser at bigger companies)
How to run it
- 1
Set your thread cap
Decide the maximum number of email exchanges you'll tolerate on a single unresolved issue. Shweta uses seven; at bigger companies she loosens it toward ten.
Pro tip Count exchanges, not total messages — the trigger is repeated back-and-forth, not a single broadcast.
- 2
Watch for the escalation pattern
The danger sign is two people going back and forth, then more people getting added, then everyone chiming in with no clear direction. That sprawl is the signal the thread has failed.
Watch out Adding more recipients to force resolution usually dilutes ownership and slows things further.
- 3
Switch to synchronous
Once you hit the cap, call the person, grab a room, or start a huddle and resolve it live in one conversation.
Pro tip Name the rule out loud to the team so anyone can invoke it without it feeling like a complaint.
In the wild
Shweta describes the classic failure mode: 'a couple of people are just going back and forth and then adding more people and then adding more people and everybody chimes in but where is this thing really headed.' Rather than let it run, she invokes the cap and moves the discussion to a call.
→ Issues that stalled in email get resolved in a single live conversation, saving many people's time.
Common mistakes
Treating more email as more progress
Piling additional replies and CCs onto a stuck thread feels productive but almost never converges; the volume is a symptom of the wrong medium, not a path to resolution.
Never setting an explicit threshold
Without a pre-agreed cap, no one has permission to break the pattern, so threads drift indefinitely and everyone silently tolerates the waste.
Is it for you?
Best for
Product managers and team leads drowning in long, unresolved email or Slack threads who want a simple trigger to force resolution.
Not ideal for
Decisions that genuinely require a written async paper trail, or distributed teams across timezones where a synchronous call is impractical.
From the transcript
“is what I I used to call is the rule of seven if there have been seven emails in an email thread and you still…”
“the long email exchanges that don't converge and go anywhere I feel or waste of time for many people”
“a couple of people are just going back and forth and um and then you know and adding more people and then adding more people…”
From the episode
Product lessons from Waymo
Shweta Shrivastava (Waymo, Amazon, Cisco)