Point of View
Most change efforts don’t fail because the plan was bad. They fail because the organization ran the wrong kind of plan. A two-team process fix gets the full steering-committee treatment, while a genuine reinvention gets a kickoff email and a project manager. Before you decide how to lead a change, decide what kind of change it is.
The word “transformation” is doing too much work
Everything is a transformation now. New CRM: transformation. Reorg: transformation. Moving the weekly meeting to Tuesdays: give it time.
When every initiative wears the same label, it gets the same treatment: the same governance, the same expectations, the same amount of leadership attention. Some initiatives need disciplined delivery and little else. Others can’t succeed without leaders who stay involved long after kickoff, and a clear picture of how the organization will work when it’s done.
The failure is rarely effort or intent. It’s misclassification.
Two questions that sort it out
Instead of asking whether an initiative is “strategic” or “big,” ask two questions. They move independently, which is the point.
Why are we acting now? Proactive change is chosen: you see a gap coming and close it before it hurts. Reactive change is forced: something broke, a regulation landed, a competitor moved, a key customer left.
How much of the current model has to change? Incremental change improves how things work today. Transformational change replaces it: a new operating model, new decision rights, new ways of working across functions.
Put the two together and you get four kinds of change.
| Incremental | Transformational | |
|---|---|---|
| Proactive | Adaptation. Steady, low-risk improvement. Needs protected capacity, because it never feels urgent. | Evolutionary leap. Needs sustained leadership and a clear picture of the end state. |
| Reactive | Reflex. Needs a clear owner and fast, light governance. | Rapid evolution. Needs speed without chaos, and leaders who stay in the room. |
This isn’t a maturity model, and no quadrant is “better.” A healthy organization needs a fitting path for all four, because change doesn’t arrive in one package.
One quadrant does get starved, though: Adaptation. It never feels urgent, so it waits until something breaks. By then it’s reactive, and usually bigger. Most transformations are the bill for years of skipped maintenance.
Transformation always crosses functions
Transformational change doesn’t respect the org chart. Change the operating model in one place and the handoffs, data and decisions in the next team over change too.
That’s why transformation needs leadership, not just management. Someone has to own the whole picture, not just their slice of it. Incremental change crosses functions less often, and when it does, it’s usually two teams who need to agree on a handoff.
The in-between: when change quietly changes type
Initiatives don’t sit still. A local fix becomes an enterprise dependency. A tool rollout quietly changes who decides what. A pilot grows into a platform.
The work may not feel harder, but it has become a different kind of change. Leadership effort climbs while governance and expectations stay where they were. The people doing the work usually notice first, well before anyone updates the status report.
A simple checkpoint: if this initiative started today, would we lead it the same way? If not, it has crossed into a new category. Reclassify it, and adjust leadership and governance to match.
When leaders and teams see different changes
Classification isn’t only a leadership exercise. The people affected often see a change as more or less urgent than leadership does, or as bigger or smaller. Leaders may see a tune-up where the front line sees a rebuild, or a crisis where teams see an inconvenience.
Either gap stalls adoption. Asking before you decide how to run the change is far cheaper than discovering the gap six months in.
Match the governance to the change
Heavy governance on simple change slows it down and teaches people to route around the process. Light coordination on complex change invites risk. And no amount of project discipline makes up for leaders who haven’t said where the organization is going.
Leadership matters most not because it speeds up execution, but because it sets the destination. Not every change needs transformational leadership. The ones that do can’t succeed without it.
What this means for senior leaders
- Classify every initiative before you decide how to run it.
- Look at the portfolio as a whole: how many of each kind are you carrying, and does each have a path that fits?
- Protect capacity for proactive, incremental change. It’s the cheapest risk reduction you’ll ever buy.
- Recheck the classification as the work evolves, and ask the people closest to it.
Where to start
Every Planosaurus engagement starts with The Dig: an independent look at how change really moves through your organization. You’ll see which kinds of change your system handles well, which ones it mislabels, and where leaders and teams are seeing different things.

