When projects fail, the postmortem almost never says "we lacked talent." It says some version of "we weren't on the same page" — which is to say, communication failed. The failures are rarely exotic. The same seven mistakes appear in team after team, and each has a fix that is unglamorous and works.
1. The unstated assumption
Someone assumed the deadline meant end of day; someone else meant start of day. Someone assumed "done" included testing. Nobody was wrong; nobody checked. Fix: state the obvious on anything that matters — dates with times and time zones, "done" with its definition. The thirty seconds of redundancy is the cheapest insurance in teamwork.
2. The decision that lived in a conversation
A real decision got made — in a call, a hallway, a thread — and three weeks later half the team is executing a different memory of it. Fix: decisions aren't real until written: what, why, who decided, in a durable place the team actually checks. Attaching the decision to the work itself — a note on the relevant card in an action board like Axtio — beats a document nobody reopens.
3. Status hoarding
Progress and problems live in individual heads until the weekly meeting, so blockers age five days before anyone hears of them. Fix: visible-by-default work. A board everyone can read answers "where are we?" without a meeting, and surfacing a blocker becomes moving a card, not drafting a confession.
4. The missing "why"
Instructions arrive without reasons — "use the blue variant" — so when reality shifts, executors can't adapt and either freeze or guess. Fix: attach one sentence of intent to every nontrivial request. "Use the blue variant — it tested better with older users" lets someone make the right call when blue is unavailable. Commander's intent, one line at a time.
5. Tone debt in written channels
Terse messages read as hostile, questions read as accusations, and small misreadings compound into genuine friction — especially remote, especially cross-culture. Fix: two habits. Assume the generous reading when receiving. When sending anything with stakes, spend one extra minute on tone — or one keyboard shortcut: a rewriting tool like Wrivio turns a blunt draft into a clear-but-warm one and shows the diff, which is faster than the three-message misunderstanding it prevents.
6. The channel sprawl
The spec is in email, the amendment is in chat, the final call was verbal, and the newest teammate is expected to assemble the truth via archaeology. Fix: explicit channel agreements — chat for the ephemeral, tickets/boards for work state, documents for anything that must be findable in six months. The rule matters less than its existence; teams argue channels once and save the argument forever after.
7. Feedback saved up for a special occasion
Small frictions and small corrections accumulate silently until they detonate in a review or an exit interview. Fix: small feedback, fast, in the flow of work — "next time flag the risk before the demo, not after" costs ten seconds today and prevents the essay in six months.
The pattern behind all seven
Every fix is the same fix wearing different clothes: move information from heads and moments into words and places — cheaply, promptly, and where the team already looks. None of it requires charisma or communication talent. It requires the discipline to write the sentence now instead of resolving the confusion later. Teams that internalize that trade stop having communication problems and start having merely ordinary ones.
