Executive Summary
Before leaders choose a framework, build a plan, or bring in outside support, they need to know whether the organization is actually ready to begin. This section lays out seven questions that test that readiness. They address the reason for the change, the type of change, the groups affected, the definition of success, leadership readiness, organizational history, and the ability to stay oriented when circumstances shift. The purpose is not delay. It is honesty. A change effort that cannot answer these questions clearly is already carrying risks that will surface later at a higher cost.
What This Page Answers
- Why should leaders stop and ask hard questions before a change effort begins?
- What seven questions deserve honest answers before planning starts?
- How is the trigger for a change different from the WHY behind it?
- Why does it matter whether a change is proactive or reactive?
- Who is affected by the change, and what does each group need?
- What does success look like in observable, specific terms?
- Does leadership have the alignment, capacity, and standing to drive the work?
- What does the organization’s history with change suggest about what lies ahead?
- How can leaders stay oriented when the change evolves?
The Questions
Before a plan gets built, before a partner gets called, before a single communication goes out, seven questions deserve honest answers. Not optimistic answers. Not the answers that sound good in a kickoff meeting. Honest ones.
Most organizations treat questions like these as throat-clearing before the real work begins. That is the mistake. These questions are the real work. A change initiative that cannot answer all seven is not ready to move.
Question One: Do we know why this change is happening, and can we state it plainly?
Not in a paragraph. Not in a strategy document. In a sentence clear enough that any employee in the organization could repeat it and mean the same thing.
This sounds easier than it is. Organizations regularly confuse the trigger for the change with the reason for it. The trigger is what set things in motion. The WHY is why any of it matters. These are different questions, and conflating them produces communication that answers the wrong one.
If ten leaders in your organization were asked to state the WHY of this change independently, how many answers would you get? If the number is more than one, the WHY is not yet settled.
Question Two: Is this change proactive or reactive?
This question matters more than most leaders recognize, and it is worth slowing down on.
Proactive change begins with a decision. The organization sees something coming, a market shift, a competitive threat, an opportunity, a strategic pivot, and chooses to move. Leadership has time to think, to plan deliberately, and to build the case before the pressure arrives. The WHY can be constructed thoughtfully. The timeline has some room in it.
Reactive change begins with an event. Something has already happened. A competitor made a move. A regulation changed. A crisis surfaced. A key person left. The organization is responding, and the pressure is already present. The WHY may be partially or fully decided by circumstances outside leadership’s control. The timeline is compressed.
Neither situation is better or worse than the other. Both require excellent leadership. But they require different things from that leadership, and applying the wrong approach to the situation produces predictable problems.
Leaders who treat a reactive situation as if it were proactive will plan with a thoroughness the situation cannot accommodate and communicate with a deliberateness the urgency will undermine. Leaders who treat a proactive situation as if it were reactive will move faster than the thinking warrants and skip the preparation that a longer timeline makes possible.
The honest question is not which type of change is easier to manage. It is which type of change you are in. The answer shapes everything: how deep the planning needs to go, how urgent the communication must feel, how much stakeholder readiness you can realistically build before the change goes live, and how much of the WHY the circumstances have already written for you.
Question Three: Who is affected by this change, and what does each group need?
Not who is involved in implementing it. Who is affected by it.
These are often different populations, and treating them the same way is one of the most reliable ways to generate resistance that could have been anticipated. The people building the roadmap have a relationship with this change that is nothing like the relationship of someone who will arrive one day to find a role redesigned around it.
Different groups affected by the same change carry different information needs, different concerns, different histories with the organization, and different levels of influence over whether the change succeeds. Answering this question honestly requires more than a stakeholder list. It requires a genuine attempt to understand what each group is walking into.
Question Four: Can we describe what success looks like in observable, specific terms?
Not as a goal statement. Not as a percentage improvement. As something a person could walk into a room and see.
Goal statements describe intentions. Observable success describes reality. “Improve customer satisfaction” is a goal statement. “A customer who calls with a billing question reaches a resolution in one interaction without a transfer” is observable success. The second version tells everyone in the organization something specific about the future state. The first version tells them almost nothing.
If the people leading this change cannot describe success in observable terms, the people doing the work have no way to know when they have gotten there.
Question Five: Does our leadership have the alignment, the capacity, and the organizational standing to drive this?
Three questions dressed as one, and each deserves a separate honest answer.
Alignment means the leaders responsible for this change agree on the WHY, the future state, and the path. Not publicly. Genuinely. A leadership team aligned in meetings and fragmented in the hallway will produce a change initiative that sends mixed signals at every level below it.
Capacity means the leaders driving this change have the time, the attention, and the resources to do it properly alongside everything else they already carry. Many change initiatives are under-resourced, not because the budget is insufficient but because the people accountable for the work are already at full capacity before the initiative begins.
Standing means the people leading this change have the organizational credibility and authority to hold difficult conversations, make hard calls, and drive accountability when the work gets uncomfortable. Technically capable leaders without organizational standing will struggle in ways that have nothing to do with their competence.
Question Six: What is our history with change, and what does that history tell us about what we are walking into?
Organizations have memories. Employees who have watched three change initiatives stall in the last five years bring that history to the fourth one. Leaders who have seen their organizations navigate difficult transitions successfully bring that confidence.
The history is not destiny. But it is context, and ignoring it is naive. An organization with a difficult change history needs to account for the skepticism it has earned. An organization with a strong track record can build on the trust it has accumulated.
The questions worth asking: What change efforts in this organization have succeeded, and why? Which ones failed, and what did the failure look like? What do employees believe about this organization’s ability to follow through? The answers to those questions already shape how people will receive this change, whether leadership acknowledges them or not.
Question Seven: Are we prepared for this change to evolve, and do we have a way to stay oriented if it does?
No change initiative survives contact with reality entirely intact. The organizations that navigate change well are not the ones with the most accurate initial plans. They are the ones with the clearest orientation points, the ones that can absorb new information, adjust course, and keep moving without losing the thread back to the WHY.
This question does not ask whether the organization is comfortable with ambiguity. It asks whether the organization has a way to make decisions when the situation changes. Who has the authority to call a change in direction? How does that decision get communicated? What stays fixed and what is open to revision?
Without answers to those questions, a change that evolves becomes a change that loses its shape. And a change that loses its shape loses the confidence of the people being asked to carry it.
Section Takeaway
Seven questions is not a long list. But most organizations cannot honestly answer all of them before the work begins. That is not a reason to wait. It is a reason to do the answering now, before the cost of the gaps surfaces somewhere more expensive.
If you worked through these questions and found gaps, that is useful information. Most leaders do. The question is not whether the gaps exist. It is whether you have the tools to close them before the work begins in earnest.
If you worked through them and found solid answers, a different question surfaces. Clarity about the WHY, the affected populations, and what success looks like is genuinely valuable. But clarity without structure is just good thinking. The next section gives that thinking somewhere to go.