Ask a team that just finished a bad group project what went wrong and you'll hear "communication." Push once and it turns into something specific: two people built the same slide, nobody knew the model changed, a decision from week two quietly reversed itself in week five. That isn't a communication problem in the abstract. It's four missing agreements, and you can make all four in about twenty minutes at kickoff.
Rule 1: One source of truth, and it isn't chat
Every team accumulates places where information lives: a chat thread, a shared drive, three people's inboxes, the doc someone keeps a local copy of. The cost isn't storage, it's that nobody can answer "what's the current version?" without asking.
Pick one home for the work itself—deliverables, tasks, deadlines, owners—and make everything else a pointer to it. Chat is for coordination ("pushed the revised model"), never for storage. The test: if a teammate went dark for a week, could they get current by reading one place? If the answer requires scrolling chat history, you don't have a source of truth yet.
Rule 2: Define what each channel is for
Teams rarely agree on channels explicitly, so everyone imports habits from their job. One person treats chat as email and expects a next-day reply; another treats it as a tap on the shoulder. Both are reasonable. Together they're a conflict nobody has named.
Write it down at kickoff. A version that works for most teams:
- Chat: coordination, quick questions, "I'm stuck on X." Not a place decisions live.
- The project tool or shared doc: requirements, tasks, status, deadlines.
- Live call: contested decisions and anything needing real back-and-forth.
- One urgent channel: reserved for "this blocks my work today."
The specific split matters less than everyone knowing it. What kills teams is two people running different rules and each quietly concluding the other is rude.
Rule 3: Write decisions in three lines
Most decision loss happens because the reasoning lived in a call half the team missed. Weeks later somebody reopens it, nobody remembers why, and you spend another forty minutes relitigating.
Three lines, in one running log:
Decision: Scope the market analysis to the US only. Owner: Priya drafts the revised scope by Thursday. Why: Two weeks left; international data would eat the time we need for the recommendation.
The "why" is the line teams skip and the one that does the work. A decision without its reason can't be revisited intelligently—you can only re-argue it from scratch or defend it out of stubbornness. If decisions keep stalling because it's unclear who actually gets the final call, that's a different, more upstream problem—MBA Lab's Leadership Lab has a guide to setting clear decision rights before you're mid-argument.
Rule 4: Give silence a defined meaning
Async communication fails on ambiguity. When you post a question and get nothing back, you can't tell whether it's unseen, deprioritized, or ignored—so you either nag or assume, and both corrode the team.
Set response windows at kickoff: input requests inside 24 hours, document reviews inside 48, urgent same-day. Now silence inside the window is normal, and silence past it is a specific, undramatic thing to follow up on. You're not asking anyone to be more available. You're making availability legible, which is what actually lowers the temperature.
The kickoff conversation, in practice
None of this needs a long meeting. Twenty minutes, four questions, written where everyone can see them:
- Where does the work live?
- What is each channel for?
- How do we record a decision?
- What response time do we owe each other?
Teams that skip this aren't being efficient—they're deferring the conversation to a moment when something has already gone wrong and it's much harder to have. If you're setting up a project from scratch, a lightweight RACI pairs naturally with these four rules: RACI settles who owns what, and these settle how you talk about it.
When it isn't a communication problem
One honest caveat. These rules fix coordination failures, and most team friction is coordination failure. But some of it isn't. A teammate who has quietly checked out, or a persistent gap between what someone submits and what the team needs, won't be fixed by a better channel policy. Clear norms make those cases visible faster, which is genuinely useful—but the conversation they surface is a different one, and it's worth having directly rather than routing it through process.