The decision was difficult, the reasoning took weeks, and the meeting where it was announced was uncomfortable. Then it was done, and the leader moved on.
Six months later nothing has changed, and the explanation offered internally is that people did not embrace it.
Why the announcement feels like the work
Because for the leader it was the hardest part.
They carried the decision alone, anticipated the objections, absorbed the reaction, and answered the difficult questions in front of everybody. That is genuinely demanding and it produces a strong sense of completion.
For everybody else the announcement was the beginning. They now have to alter how they do something, absorb the period during which they are worse at their jobs, and work out what the change means in cases nobody addressed.
The two experiences are almost perfectly inverted, which is why the leader’s sense of where the effort sits is systematically wrong.
What has to exist for a change to take
An announcement supplies one of five requirements and organizations routinely supply only that one.
People know what to do differently on Monday. Specifically, in their own role. A stated direction is not a changed behaviour, and most announcements never descend to the level of an actual altered action.
They are able to do it. Training, access, tools, time. A change that requires a capability nobody has is not a change, it is an aspiration with a deadline.
The old way is no longer available. While both exist the old one wins, because it works.
Somebody owns it after the launch. A named person whose job includes this in month five, when the leader’s attention has moved.
The surrounding structures agree with it. If the stated priority is quality and the metric reported weekly is volume, the metric wins and the announcement was noise. This is the requirement most often violated and the hardest to see from the top.
The middle layer decides
An announcement reaches supervisors, and what they do with it determines the outcome regardless of how it was received in the room.
A supervisor who explains the change in their own words, applies it to their crew’s actual cases, and enforces it has made it real. One who mentions it once and continues as before has ended it, without ever having opposed anything.
Which means the launch meeting is not the important conversation. The important conversation is with supervisors, before the announcement, and it has to answer their question rather than the organization’s: what does this require of you, what will your people ask, and what do you say.
A supervisor who cannot answer a question from their crew will fall back on the old way, and they will be right to, because they cannot operate on an explanation they do not have.
Ask what changed, not whether it was understood
Leaders check on changes by asking whether people are on board, which returns yes.
The questions that return information are concrete and directed at the work. What are you doing this week that you were not doing in March? Show me the last three that went through the new process. What happens when the case does not fit?
The third of those is where most changes are quietly failing, because the exception case is handled the old way and the exception case is more common than anybody estimated.
The scale of the announcement is not the scale of the change
Large announcements produce a specific hazard: they create an expectation of transformation, which makes the ordinary difficulty of month four look like failure.
Frequently the better approach is a smaller announcement and a longer commitment. State the change plainly, without the launch apparatus, and then demonstrate over the following year that it is permanent by continuing to ask about it.
Organizations read persistence more accurately than emphasis. A change mentioned quietly and asked about every month for a year is understood as real. One announced in a full assembly and never raised again is understood as it deserves to be.
Edited by Patrick J. Wolf, PhD