The Communication Myth: Why Good Intentions Aren't Enough

"We just need better communication around here."

I have heard that sentence in exit interviews, in employee surveys, and in more than one leadership retreat where nobody wanted to be the first to say it out loud. It always gets nods around the table. And it almost never gets fixed, because most leaders hear it as a character problem instead of what it actually is.

When a team says there is a lack of communication, it is tempting for a leader to take that personally, or worse, to assume someone up the chain is hoarding information on purpose. In my experience working with organizations of every size, that is almost never what is happening.

Most leaders genuinely want their team informed. What they are missing is not intent. It is infrastructure.

The gap between what a leader means to share and what a team actually hears is rarely malice. It is the natural result of running an organization without a deliberate rhythm for getting information from the people who have it to the people who need it.

Here is where most leaders go wrong when they try to fix this. They tell the team to communicate more, or they send out a reminder email about staying in the loop, and then they wonder why nothing changes six months later.

Good intentions do not scale. Systems do.

The real question is not "why aren't we communicating better." It is this:

What do we have in place to make sure the right information reaches the right people automatically, without depending on someone remembering to send it?

Without an answer to that question, communication becomes something people do when they have extra time. And extra time is the first thing that disappears in a growing organization.

When I work through this with a leadership team, it usually comes down to the same three gaps, every time.

Where does this information actually live? Slack, email, a shared drive, a Monday huddle. It does not matter which tool you pick. What matters is that everyone knows where to look, because a tool nobody checks is not a system, it is just noise with a login.

Who actually needs to know this? Not everyone needs every update. A system that blasts everything to everyone trains people to stop reading any of it. A real process maps out who needs what, so the right people get the right information without burying everyone else in updates that were never meant for them.

When does this get shared, and how often? A weekly huddle. A monthly update. A quarterly review. The specific rhythm matters less than the fact that it is a rhythm. Once a cadence exists, nobody has to guess whether now is the right time to bring something up.

At Fortis, we do not leave this to chance, and we do not leave it to memory. Every Fortify Weekly Meeting we run for a client ends with a block we call Cascade. Five minutes, same time every week, with one job: decide who needs to know what came out of this meeting, and make sure it actually gets to them before the week moves on.

It sounds small. It is not. Cascade is the difference between a decision that lives and dies in a leadership meeting and a decision that actually reaches the people who have to act on it. Most of the "communication problems" I get called in to help fix are not people problems at all. They are missing Cascade problems. Nobody built the five minutes where someone asks, out loud, "who else needs to hear this."

The same is true one layer down. A lot of what looks like a communication breakdown is actually a decision-rights breakdown. If nobody has ever written down who is allowed to approve what, up to what dollar amount, without escalating, then every decision becomes a communication event by default, because nobody is sure who is supposed to know or who is supposed to decide. That is exactly what a Decision Authority Matrix is built to solve. Once it exists, half of what used to require a conversation just does not need one anymore.

A culture of transparency does not happen because a leader feels bad that people were left out of the loop. It happens because a leader was willing to sit down, look honestly at how information actually moves through the organization today, and build a system that does not depend on anyone's memory.

Stop asking your team to communicate better. Build the rhythm, name the channels, decide who needs to know what, and let the system carry the weight your good intentions never could on their own.

If this resonated, I would love to hear about it. Reach out anytime, or if you want to talk through what is actually breaking down in how your team communicates, schedule a free Discovery Call. No pitch, just a conversation.

Roger Peace, Founder, Fortis Leadership Group