Raf Alencar
Running on DefaultMAR 25, 2026

The Last Checkpoint

Every transformation initiative has a Last Checkpoint. It's not the budget. It's not the technology. It's a person — and your org chart won't tell you who it is.

The core argument

Every transformation initiative has a Last Checkpoint. It's not the budget. It's not the technology. It's a person. And your org chart won't tell you who it is.

The Last Checkpoint — one person every meaningful change has to pass through, and most of them don't

Every initiative that dies in your organization dies at the same place.

Not at the board. Not at the budget committee. Not in the market. At one person. One function. One layer of the organization that every meaningful change has to pass through — and most of them don't.

You know who it is. You've worked around them. You've built strategies specifically designed to avoid them, or to get to them through a more sympathetic channel, or to time things so that their calendar was full and the decision could move without them.

And somehow, it still got stuck.

This isn't new. It didn't start with AI. Companies have been failing at real innovation for decades — not because the ideas were bad or the budgets were small, but because the same pattern plays out every time. The only projects that consistently get through are large, inevitable, IT infrastructure-level initiatives. The kind where the vendor contract is already signed and the alternative is the lights going off.

Everything else — the real innovation, the process reinvention, the capability-building that would actually change how the company competes — gets approved to death.

Same person. Every time. Different decade.

Bureaucracy Slows Everything. The Last Checkpoint Is Selective.

Selective obstruction — fast when in control, slow when someone else built it; the tell is the pattern, not the pace

That's what makes this archetype different from ordinary organizational friction.

Bureaucracy slows things down uniformly. The Last Checkpoint moves fast when they're in control of the outcome. They move slowly — or not at all — when someone else built the thing, owns the relationship, or would get the credit.

The tell is the pattern, not the pace.

Watch what they approve quickly versus what gets stuck in review. Watch who they loop in versus who they quietly exclude. Watch how they respond to a proposal from their own team versus one from finance, or operations, or — worst of all — from someone below them who went slightly around the process.

The obstruction isn't ideological. It's territorial. There's a difference.

They Call It Protecting the Business. They're Protecting Their Position.

When the Last Checkpoint slows an initiative, the stated reason is always legitimate-sounding. Security risk. Misalignment with strategy. Need more stakeholder input. Not the right time. Each reason, taken individually, is defensible.

Taken together, across years and multiple initiatives, they form a pattern that has nothing to do with protecting the business and everything to do with protecting a budget line, a vendor relationship, a team headcount, or simply the feeling of being impossible to route around.

The cover story is coherent because they've been telling it long enough that they believe it themselves. You're not dealing with someone who knows they're obstructing. You're dealing with someone who has genuinely convinced themselves that their obstruction is stewardship.

That distinction matters — not because it makes their behavior acceptable, but because it tells you how the conversation has to go. You can't argue someone out of a position they didn't reason themselves into.

The Mike's Excel connection. Someone in the trenches got tired of waiting and built something real. It worked. The whole team used it. For years. But it never got formalized. Because formalizing it would have meant someone owning it officially — which meant someone getting budget for it — which meant the Last Checkpoint losing a line item, a dependency, or both. That's not a technology failure. That's an ownership failure. And the ownership failure was a choice.

But Here's the Part the CEO Doesn't Want to Hear.

The Last Checkpoint only exists because someone above them keeps rewarding the behavior.

They didn't build this pattern in isolation. They built it in response to an environment that promoted caution over outcomes, visibility over results, and loyalty over capability. Every year they survived another reorg, every budget cycle they came out larger than they went in, every initiative they quietly killed without consequence — that was the organization teaching them that control is the right strategy.

They're not a rogue element. They're a product.

Replacing this person without changing the environment that built them will grow you another one. Faster, probably, because the environment is now proven.

The hard question isn't who your Last Checkpoint is. The hard question is what decisions you made — about performance, about reward, about what you chose not to confront — that gave them permission to become one.

Now the Uncomfortable Part.

You've been reading this as a diagnostic. A way to identify the person in your organization who fits this description.

Stop for a moment and run it the other way.

Think about the last initiative that came to you from below. The one that had real energy behind it, a credible person driving it, a legitimate case for moving forward.

Did you sponsor it clearly and remove the obstacles in its path? Or did you ask for more data, add a stakeholder, suggest it needed more alignment before moving forward?

Did you give it air, or did you give it process?

The most dangerous version of this archetype isn't the one you can easily identify and name. It's the one sitting in your own chair. Making decisions that feel measured and appropriate, while the people below you are quietly learning that real ideas don't survive contact with your calendar.

What AI Changed — And Why This Suddenly Matters More.

The competitive cost — measurable in weeks now, not years; the cover story is running out of room

For years this pattern was survivable. Painful, wasteful, demoralizing — but survivable.

That window is closing.

The gap between what's possible now and what most organizations are actually doing is measurable in weeks, not years. An analyst with the right access can build in two hours what used to require a six-month IT project.

When that's the environment, a Last Checkpoint doesn't just slow you down. They become the single largest competitive liability in your organization.

And they're still being promoted.

Next: The environment didn't just tolerate this leader. It built them. And until you change what the environment rewards, you'll keep growing more.

Common Questions

What is the Last Checkpoint?
The Last Checkpoint is one person — or one function — every meaningful change in your organization has to pass through. They aren't necessarily the highest-ranking person involved. They're the one whose tacit veto, slow review, or quiet reframing kills initiatives that don't originate with them.
How is the Last Checkpoint different from ordinary bureaucracy?
Bureaucracy slows things down uniformly. The Last Checkpoint is selective: fast when they own the outcome, slow when someone else built it. The tell is the pattern, not the pace — what they approve quickly versus what gets stuck in review.
Is the Last Checkpoint acting in bad faith?
Almost never. They've genuinely convinced themselves that obstruction is stewardship. The cover story is coherent because they've been telling it long enough to believe it. That distinction matters, because you can't argue someone out of a position they didn't reason themselves into.
Why does AI make the Last Checkpoint a bigger problem now?
Because the gap between what's possible and what most organizations actually ship is now measurable in weeks, not years. An analyst with the right access can build in two hours what used to take a six-month IT project. In that environment, a Last Checkpoint isn't a slowdown — they're the single largest competitive liability.
Related Reading
Does this pattern show up in your organization? The Environment Design Assessment measures five dimensions of organizational alignment. It takes eight minutes and tells you specifically where the design was left to chance.
Take the Assessment →