When “we need better communication” isn’t a communication problem

It arrives the same way almost every time: “the teams just need to communicate better.” So you get more meetings, a new channel, another stand-up. Six weeks later the friction is exactly where it was — now with more calendar invites.

Most of the time, poor communication isn’t the problem. It’s the symptom. People communicate badly when the structure forces them to.

Two teams that “don’t talk to each other” usually share no clear ownership boundary — so every handoff becomes a quiet negotiation about whose job this is. Or they’re measured on targets that pull in opposite directions, so talking more just surfaces the conflict faster. Or the information one team needs lives in a system the other can’t see, and no amount of goodwill fixes a permissions gap.

Add communication on top of a structural gap and all you’ve done is make the gap louder. The meeting doesn’t close it; it just gives people a room to feel it in.

So before you schedule another sync, ask a different question: what is the structure making people do? Where does ownership actually end for one team and begin for another — and is that written down anywhere, or just assumed? What are the two teams each rewarded for, and do those rewards agree? Fix that, and a lot of “communication problems” quietly disappear on their own.

Better communication is a fine goal. It’s rarely the fix — because it treats a symptom people can see instead of the structure they can’t.

Finding the structural gap underneath a “communication problem” is a lot of what a Service Clarity Audit does.

Book a Service Clarity Audit

Insights

When “we need better communication” isn’t a communication problem

12 August 20261 min read

It arrives the same way almost every time: “the teams just need to communicate better.” So you get more meetings, a new channel, another stand-up. Six weeks later the friction is exactly where it was — now with more calendar invites.

Most of the time, poor communication isn’t the problem. It’s the symptom. People communicate badly when the structure forces them to.

Two teams that “don’t talk to each other” usually share no clear ownership boundary — so every handoff becomes a quiet negotiation about whose job this is. Or they’re measured on targets that pull in opposite directions, so talking more just surfaces the conflict faster. Or the information one team needs lives in a system the other can’t see, and no amount of goodwill fixes a permissions gap.

Add communication on top of a structural gap and all you’ve done is make the gap louder. The meeting doesn’t close it; it just gives people a room to feel it in.

So before you schedule another sync, ask a different question: what is the structure making people do? Where does ownership actually end for one team and begin for another — and is that written down anywhere, or just assumed? What are the two teams each rewarded for, and do those rewards agree? Fix that, and a lot of “communication problems” quietly disappear on their own.

Better communication is a fine goal. It’s rarely the fix — because it treats a symptom people can see instead of the structure they can’t.

Finding the structural gap underneath a “communication problem” is a lot of what a Service Clarity Audit does.

Book a Service Clarity Audit

Working together

I work with organisations improving specific services, understanding why things are not working as expected, or building their own internal capability for this kind of work.

Get in touch →
← Back to Insights© 2026 Darius Shahab CMgr