Email is the default operations tool for most small stores because it requires no decision. It fails for coordination in a specific way: there is no shared state. Each person holds a partial copy of the conversation, nobody can see what is outstanding, and the record leaves with whoever owned the mailbox.
What Email was built for
Email was designed for correspondence between two parties, and it is still excellent at that. Supplier negotiations, customer escalations and anything needing a formal record belong there and should stay.
The trouble starts when it is used for coordination, because coordination needs shared state and email has none. A thread is a sequence of copies, not a single place, which is why the answer to "has anyone dealt with this" is always another email.
Where a store team pushes against it
The failures are structural rather than a matter of discipline, which is why better email habits never quite fix them.
- No shared state. Nobody can see what is outstanding without asking, and asking generates more email.
- Ownership is implied, never assigned. A thread with four people on it is owned by nobody, which is the classic dropped-ball condition.
- The record is per-mailbox. When somebody leaves, their half of every decision leaves with them.
- New people start from zero. There is no history to read into, so context has to be re-explained person by person.
- Reply-all is the only broadcast, so people are either over-copied or missed entirely.
The structural difference
| Store Huddle | ||
|---|---|---|
| Built for | Correspondence between parties | Coordination inside a team |
| State | Per-mailbox copies | One shared place |
| Ownership | Implied by who replies | Assigned, with a due date |
| New starter | No history to read | Reads the room |
| Store context | Pasted or screenshotted | Attached, with live state |
| Best for | Suppliers, customers, records | Internal coordination |
Neither column is a verdict. The question the table is trying to answer is whether the work your team does all day is the work the tool was shaped around, because that is what determines how much friction you absorb every week.
Keep Email if
- You are one or two people and coordination happens verbally anyway.
- Your external correspondence, with suppliers and customers, is what actually needs organising. Email is the right home for that and should stay there.
- Your team genuinely does work asynchronously across long gaps, where the formality of email is a feature rather than friction.
Consider moving if
- The question "did anyone deal with this" is a normal part of your week.
- You have lost a decision because it lived in the sent folder of somebody who left.
- New starters need things explained that already happened in threads they cannot see.
- Your team has quietly started a group chat alongside email, which is the strongest signal of all and usually predates anybody admitting it.
Common questions
Why is email bad for team coordination?
Because it has no shared state. Each person holds a partial copy, nobody can see what is outstanding, and ownership is implied by who happens to reply rather than assigned.
Should we stop using email entirely?
No. Email is right for correspondence with suppliers and customers and for anything needing a formal record. The problem is internal coordination, which is a different job.
What is the first sign email has stopped working?
A group chat appearing alongside it. Teams do not usually announce that email is failing; they route around it and the side channel is the evidence.