By the time a leader stands up at the all-hands to announce a change initiative, the outcome is largely already set. The announcement is not the beginning of the change. It is a verdict on conditions that were decided, or left undecided, in the weeks before anyone walked into the room. Everyone present is about to find out which way the verdict went.
This is the part most change management has backward. We treat the announcement as a launch, the moment the work begins. It is closer to a test, and a leader can fail it in public having already failed it in private, without ever realizing the test was running.
The pattern is familiar. Six to twelve months after the announcement, the energy has gone out of the initiative. The new behavior has quietly reverted to the old one. And the post-mortem turns to what went wrong in the rollout: the timeline, the resourcing, the middle layer that never got on board. Those are real. But they are usually symptoms of a gap that was visible, to anyone looking, before the first slide went up.
Why Do Change Initiatives Fail Before They Start?
The reason change initiatives fail is rarely the change itself, and rarely the execution. It is that the organization was not in a state to hold the change on the day it was announced.
When I work with leadership teams in the middle of a stalled transformation, the conversation almost always begins with the rollout. We work backward and find the rollout was fine. What was missing sat upstream of it. The initiative was announced into an organization where the people being asked to change did not believe their needs had been considered, where the senior team was nominally supportive but behaviorally unchanged, and where no one could say in a sentence why this work mattered more than the last three programs that quietly died.
None of that is an execution failure. It is a readiness failure, and the launch is only where it surfaces.
This matters because of where leaders look for the fix. If you believe the initiative failed in the rollout, you manage the next rollout harder: more communication, more governance, more change champions. If you understand that it failed in the conditions present before launch, you do something different. You stop announcing into conditions that predict failure, and you build the conditions first.
Why the Standard Change Playbooks Do Not Catch This
When a change initiative starts to stall, most leaders reach for the established change management canon: a certified internal change team, a structured methodology like the eight-step model or ADKAR, a rollout governance structure. These are competent tools, and they have a shared characteristic worth naming.
They start at or after the announcement.
Every one of those frameworks is an execution methodology. They are built to manage the change once it is underway: to sequence it, communicate it, and track adoption. What none of them does is tell a leader, before the announcement, that the initiative is already structurally unlikely to hold, and give them a way to see it while there is still time to act. That is the gap this post is about. Not how to run a change program, but how to know whether you should announce one yet.
The Four Conditions That Reverse the Pattern
Across two decades advising organizations through change, the initiatives that held shared four conditions. I do not offer these as a research finding. They are a practitioner’s framework, built from that work and consistent with what the leadership research does establish. Where the research is clear, I will say so.
My doctoral research established resilience and belonging as structural outcomes: properties of how an organization is designed, not traits of the people inside it. Change readiness follows the same logic. It is a condition you build into the structure before the work has a name, or it is absent, in which case the announcement is the moment the absence starts to cost you.
Condition one: leaders walk their talk
The first and most load-bearing condition is behavioral consistency at the top. Not stated support. Demonstrated support.
An initiative is read, by the people asked to carry it, through the behavior of the leaders sponsoring it, not through the messaging. When a senior team announces a change and then continues to operate exactly as before, the organization draws the correct conclusion: this is not real. Lack of C-suite backing is rarely a refusal to fund the work. It is a senior team that authorizes the initiative and then does not change its own behavior to match it. That gap is the most reliable predictor of failure there is, and it is visible immediately.
Condition two: people believe their needs were considered
The second condition is whether the people being asked to change believe the change accounts for them. This is the difference between compliance and commitment, and it is better understood than most leaders realize.
The research calls it procedural justice: people accept outcomes, including unwelcome ones, when they believe the process that produced them genuinely accounted for them. A workforce that was informed but not considered will comply. They will attend the sessions, update the deck, and wait for the initiative to pass. A workforce that believes its needs shaped the design will commit. The distinction is not motivational. It traces directly back to whether anyone asked, before the design was finalized, what this change would actually require of the people living inside it.
Condition three: honest error is safe, and standards hold
The third condition is psychological safety, and it is the most evidenced item on this list. It is also the one most often misread.
The condition is not a general tolerance for failure. It is narrower and harder. Every meaningful change involves a period where people do unfamiliar things imperfectly before they do them well. Psychological safety, in the sense Amy Edmondson’s research established, is the condition where the honest, in-progress error that learning requires is safe to make, while the performance bar stays exactly where it was. Not lowered standards. Safe candor under high standards. Where that condition is absent, people stop attempting the new behavior, because the risk of being caught getting it wrong is higher than the cost of quietly reverting to the old behavior they can already execute. The culture says it wants innovation. The structure rewards not getting caught. People believe the signal expressed through consequences, not the one in the values statement.
Condition four: people share an affinity for the mission
The fourth condition is whether the people carrying the change can connect it to a reason that matters to them.
This is the communication-of-vision gap, but it runs deeper than communication. Explaining the vision more clearly does not close it. What closes it is individuals being able to link the organizational mission to something they already value, so the change becomes something they have a stake in rather than something happening to them. A leadership team that cannot say why this work matters, in one sentence, to the person three levels down has not earned that person’s effort. It has requisitioned their compliance.
What This Looks Like Before You Announce
These four conditions are not built through a communications plan. They are built through specific leadership behavior in the period before the initiative is named.
That behavior is concrete. It means connecting the mission to what individuals already value, so condition four exists before you ask for it. It means reading accurately what the change will cost the people carrying it, and letting that shape the design, which is what produces condition two. It means backing the work visibly, changing how the most senior people spend their time and make decisions, rather than approving it and moving on, which is condition one. And it means keeping feedback moving in both directions, because that is how a leadership team finds out whether the first three conditions actually exist or only appear to.
The reason this work has to happen before the announcement is that the announcement is the test. You do not want to discover the conditions are absent by failing the test in public.
Where to Start
If you are preparing to launch a change initiative, or you are in one that is not holding, the most useful thing you can do this week is to run the four conditions as a diagnostic before you spend another dollar on execution.
Take the initiative and ask, for each condition, not whether you hope it is true but whether you have evidence it is true. Do the leaders sponsoring this change behave differently than they did before it, in ways the organization can see? Were the people being asked to change consulted in a way that shaped the design, or only informed after it was set? Is the honest early error this change requires safe to make, while the standard holds? Can a person three levels down say why this matters in a sentence that is theirs, not yours?
Where the answer is no, you have found a predictor of failure while you can still do something about it.
This is not a small thing to get right. A change initiative is among the most expensive and most visible bets a leadership team makes, and when it fails, it fails in front of the board. Treating change as a readiness problem rather than an execution one is risk reduction on that bet. The failure becomes visible early, while it is still cheap to fix. So does the reversal.
The leaders who beat the odds are not better at managing rollouts. They are better at refusing to announce into conditions that were always going to fail, and at building the four conditions deliberately before the work has a name.
If You Are in This Right Now
If you are preparing to launch a change initiative, or you are in one that is not holding, running the four conditions against your specific situation is where this becomes useful. A strategy call is a focused session to do exactly that: find the condition that is missing, and decide what has to be true before you announce, or before you spend more on an initiative that is already stalling.
This is not a sales conversation. It is a working session for leaders who recognize the pattern and want to see it clearly before it costs them the initiative.
Frequently Asked Questions
Why do change initiatives fail before they start?
Most change initiatives are decided before they are announced. By the time a leader announces a change, four conditions are either present or absent: demonstrated leadership backing, a workforce that believes its needs were considered, psychological safety for the honest error that learning requires, and a shared connection to why the change matters. The announcement does not build these. It reveals which ones are missing, which is why so many initiatives stall months later for reasons that were visible before launch.
What are the conditions for successful organizational change?
Four conditions most reliably predict whether a change initiative will hold: leaders who demonstrate the change in their own behavior rather than only authorizing it, people who believe their needs were considered in the design (procedural justice), psychological safety where honest early error is safe while standards hold, and a workforce that can connect the change to a mission it personally values. These are built before the announcement, not during the rollout.
Why is lack of C-suite backing a structural problem and not a political one?
Lack of C-suite backing is rarely a refusal to fund or approve the work. It is a senior team that authorizes the initiative and then does not change its own behavior to match it. The organization reads the behavior, not the messaging, and concludes the change is not real. Because it is expressed through behavior rather than stated position, it is structural, and it is the single most reliable predictor of change failure.
What is the difference between compliance and commitment in change management?
Compliance is doing what the change requires while waiting for it to be over. Commitment is carrying the change because you have a stake in it. The difference is not motivation or personality. It is whether the conditions for commitment, particularly considering people’s needs in the design and connecting the work to a mission they value, were built before the initiative launched.
How do you assess change readiness before launching an initiative?
Run the four conditions as a pre-launch diagnostic. For each, ask whether you have evidence it is true, not whether you hope it is: demonstrated leadership backing, a design that considered the people affected, psychological safety for honest early error under unchanged standards, and a mission connection a person three levels down can state in their own words. Where the answer is no, you have identified a predictor of failure while there is still time to address it before the announcement.
