Communication between teams is not fixed with another meeting or another channel. It is fixed when each kind of message has a place, an owner and a trail. Sales, product, operations and leadership do not fail because they “do not talk”. They fail because the same agreement lives in a thread, in a document comment and in the memory of the person who was not there. Improving that is design, not charisma.

The problem is not talking too much

Message volume is not the diagnosis. The diagnosis is the absence of a channel contract. If the urgent notice, the debate and the archive travel down the same pipe, everything feels urgent and nothing can be retrieved. The team that “does not communicate” is almost always communicating without pause. What it does not do is close.

  • Urgent: a short channel, named people and a response time.
  • Debate: a document or a meeting that ends with a written decision.
  • Archive: the note or the record, not yesterday’s thread.

Without those three boxes, each team reads the other’s silence as contempt. It almost never is. It is a message that died in the wrong pipe.

One channel, one purpose

Messaging won because the other side is already there. 73.3% prefer messaging a business and 74.6% trust more when they can. Inside the company the same force applies: the short channel reduces friction. The error is treating that channel as the system of record. Slack or its equivalent transports. It does not replace the document or the CRM.

Give each channel a purpose and publish it on one page. Email for what must be forwardable outside. Chat for what expires in a day. A document for what is edited. A video call for tone or a whiteboard. If a topic changes purpose, change channel on purpose — not “as well”. “As well” is how double work is born.

Shared context replaces the status meeting

Status meetings exist because status cannot be seen. A live board or document with an owner, a date and a visible blocker saves the ritual of reading aloud what should already be written. The meeting that remains is the decision or the conflict. The rest is presence theatre.

That requires each team to publish the minimum the other needs in order not to ask. Not a report. A status. “Blocked by X, owner Y, date Z” is communication between teams. A Monday context paragraph is not, if the fact changes on Tuesday and nobody updates. Shared context is a record, not an internal newsletter.

Writing is a team skill

Teams that coordinate well write in a dull, precise way. A subject that parses. The decision in the first sentence. Options, risk and a date. Who must reply. Anyone who writes to perform forces the other team to translate. That translation is the hidden cost of informal “good communication”.

Train the close. Every long thread ends as a three-line clip in the canonical place. Every video call ends with owners and dates, not “we agreed what we said”. If AI drafts a summary, Gartner’s 2026 point still applies: you need a company rule for what is treated as true and who validates it. An unreviewed summary is another layer of noise.

Rituals that scale

A short weekly ritual between team owners — not “everyone” — keeps the contract alive: what is blocked, what was decided, what moves channel. A monthly ritual kills zombie channels and groups that no longer have a purpose. Communication improves when there are fewer places an agreement can hide.

Measure repeated questions (“what state is this in?”), time to a cross-team decision and the number of agreements that exist only in chat. If those three fall, communication between teams improved even if the tone stays dry. The goal is not that everyone knows everything. It is that the person who must act does not have to hunt for the fact, and that the other team knows where to look without asking for a slot.