The Difference Between 'We Need Better Communication' and Actual Solutions

After every difficult change initiative, someone says it: "We need better communication."

It shows up in retrospectives. In feedback surveys. In hallway conversations. "The problem was communication."

And then the next change initiative starts, and the same problems happen again.

Because "better communication" isn't a solution. It's a complaint without a diagnosis.

"Better communication" means different things to different people

When leadership says "we need better communication," they usually mean "people didn't understand our rationale."

When middle managers say it, they mean "we weren't equipped to answer our teams' questions."

When frontline staff say it, they mean "we were confused about what was actually changing."

Those are three different problems. They require three different solutions. But they all get collapsed into the vague phrase "better communication."

The real problem is usually structural, not effort or skill based

When people say "better communication," they're usually implying that someone didn't try hard enough. Didn't send enough emails. Didn't explain clearly enough. Didn't communicate frequently enough.

But most change communication breakdowns aren't effort problems. They're structure problems.

Messages fragment as they cascade through management layers. Scope boundaries weren't established upfront. Timeline ambiguity paralyzes decision-making. Managers improvise answers because they weren't briefed properly.

None of those are solved by "communicating more" or "communicating better." They're solved by structural changes to how communication is designed and delivered.

Volume doesn't fix structural gaps

When organizations hear "we need better communication," they often respond by increasing volume. More emails. More meetings. More updates. More all-hands sessions.

This can actually make things worse.

More communication without structure just means more opportunities for messages to fragment, contradict each other, or create overwhelm. People tune out. They stop reading updates because there are too many to process.

Volume is not the same as clarity. Frequency is not the same as structure.

What actual solutions look like

Instead of "better communication," here's what helps:

Structural clarity before announcement. Ensure messages contain scope boundaries, timeline specifics, and operational details...not just strategic rationale.

Manager preparation before cascade. Brief managers on what questions their teams will ask and what answers to give. Don't make them improvise.

Consistent language across levels. Use the same words to describe the change from executive to frontline. Don't let each layer "interpret" the message.

Timeline commitments, not aspirations. Provide specific dates and decision points. "March 15" instead of "soon" or "Q2."

Acknowledgment of what's uncertain without speculation. Name what you don't know yet and when you'll know. Don't pretend everything is finalized when it's not.

Those are solutions. They're specific. They're structural. They prevent predictable failures.

Why organizations resist structural solutions

"Better communication" is appealing because it doesn't require changing anything fundamental. It just requires trying harder.

Structural solutions require acknowledging that the way you currently approach change communication has gaps. That your process needs improvement. That individual effort can't compensate for missing infrastructure.

That's harder to accept.

The diagnostic question

Next time someone says "we need better communication," ask: "What specifically broke? Where did the message fragment? What questions did people have that we didn't answer? At what point did confusion emerge?"

Most of the time, you'll identify a structural gap. Scope wasn't bounded. Managers weren't prepared. Timeline was vague. Messages contradicted each other across layers.

Those are fixable problems. But not by just "communicating better."

Stop treating communication as a soft skill

Communication during organizational change isn't just about being clear or empathetic or frequent. It's operational infrastructure.

When it's designed well, complex changes move through organizations without creating chaos. When it's designed poorly, even simple changes create confusion and resistance.

Treating it as a soft skill—something you just need to "do better"—misses the point. You need a system that prevents the structural breakdowns that individual skill can't fix.

This is solvable

If your organization keeps having the same communication breakdowns across different changes, that's not a people problem. It's a systems problem.

And systems problems have structural solutions.

Learn the systematic approach that identifies exactly where communication breaks during change and provides structure that prevents those failures before they happen.