Why Didn't Anyone Tell Me This Wasn't Working?
You rolled out the change. You explained it. You thought it landed.
Three months later, half your team is still doing it the old way. Nobody flagged it. Nobody pushed back in the meeting. You only found out because you happened to notice, or a customer mentioned something, or the numbers finally forced the question.
The frustrating part isn't that the change failed. Change fails all the time. The frustrating part is that you were the last to know.
It's not a communication problem
Most owners read this as a communication failure and respond by communicating more. Another email. Another reminder in the team meeting. Sometimes it helps. Usually it doesn't, because the problem was never that people didn't hear about the change. It's that nobody had a fast, safe way to tell you it wasn't working before it quietly died.
Silence gets misread as agreement. It's not. Silence is usually the absence of a real channel to say "this isn't working" without it turning into a confrontation, an extra meeting, or a mark against them.
What a feedback gap actually looks like
A few tells:
People nod in the room, then do the old thing at their desk
The only feedback you get is a shrug and "it's fine"
Problems surface as a crisis instead of a heads-up
You find out from a customer or a number before you find out from your team
None of these mean your people don't care. It usually means the cost of speaking up is higher than the cost of quietly working around the change. That's not a people problem. That's a design problem in how the change was rolled out.
Why this matters more than it looks like it does
A change that's failing quietly is worse than a change that fails loudly. Loud failure gets fixed. Quiet failure just sits there, burning time and trust, until it surfaces as a bigger problem than it needed to be.
The fix isn't a suggestion box nobody opens. It's building one specific, low-friction moment early where someone can say "this isn't working" and have it actually go somewhere. A two-week check-in. A direct question from you, not a survey. A named person whose job is to hear the friction and report it up, before it calcifies into "the way we've always done it, again."
This is one piece of a bigger pattern. Most change efforts stall for one of five reasons, and the feedback gap is only one of them. [link to five-gaps post] walks through all five and where yours is likely breaking down.
Where to start
If you're not sure whether this is your gap or a different one, that's exactly what the Change Readiness Assessment is built to surface. It takes a few minutes and tells you which of the five gaps is actually costing you, instead of guessing and communicating harder at the wrong problem.
