Large organizations do not lose control of critical transformation programs because they lack capability.
They lose control because they systematically keep their best people out of them.
It happens again and again. The organization launches a multi-million ERP, CRM, HCM, or core banking program. The stakes are obvious. If it fails, it disrupts operations, damages clients, and consumes capital at a scale that is hard to recover.
And yet, when you look at who is actually working on the program, you rarely find the strongest operators in the business.
That is not an accident. It is the result of how incentives are designed.
From a purely economic perspective, this makes no sense.
Take a simple benchmark. At a 10 percent net margin, every million spent requires ten million in additional revenue just to break even. Most large-scale technology programs do not just consume the initial budget. They overrun. They absorb management attention. They reduce productivity during transition. The true cost is significantly higher than what is ever written into the business case.
If there is any place where you would expect an organization to deploy its strongest people, it is here.
Instead, the opposite happens.
Executives hesitate to release their top performers because those individuals are critical to current revenue. Line managers resist because losing their best people directly impacts their own targets, bonuses, and internal standing. And the individuals themselves understand very quickly that participation in such a program is asymmetric.
If the project succeeds, it is considered expected.
If it struggles, the exposure is immediate.
In most organizations, project work is layered on top of the day job. The message is implicit but clear. You are responsible for transforming the organization, but your career still depends on your existing role. That creates a simple and entirely rational behavior. People protect what is measured.
The result is predictable.
The project is staffed with available people, not the right people. Decision-making slows down because the individuals involved lack authority or context. Issues escalate late because nobody wants to surface problems that could be career-limiting. And the gap between the designed solution and the operational reality of the business grows with every iteration.
At the executive level, the dynamic becomes even more distorted.
Unless you are directly accountable for technology or operations, your primary expectation remains external. Revenue, clients, market presence. Internal programs are seen as necessary overhead. At the same time, these programs consume budget at a scale that requires constant justification, while the probability of staying within that budget is low.
So the executive narrative shifts quickly from value creation to damage control.
This is the point where morale starts to erode.
The organization senses that the program matters, but also that it is not truly owned by the people who define success elsewhere. The people closest to the work carry the operational burden without corresponding recognition. And the people who could make the biggest difference are structurally incentivized to stay away.
What looks like a resource allocation issue is in reality a misalignment of incentives.
And as long as that misalignment persists, the outcome is largely predetermined.
If you want a different outcome, you have to change the rules under which people make decisions.
That starts with a simple but uncomfortable step. Your best people need to be on the program, and they need to be there in a way that reflects the importance of the work. Not part-time. Not as an additional responsibility. But as a primary role.
That requires trade-offs. Delivery in the core business will slow down. Short-term targets may be missed. But this is already happening implicitly. The difference is whether it is managed deliberately or absorbed through declining performance and hidden inefficiencies.
Equally important is how success is measured.
If bonuses, promotions, and visibility remain tied to the day job, people will optimize for the day job. No communication campaign will change that. Incentives have to be aligned with the program. Career progression has to reflect contribution to the transformation, not absence from it.
Finally, the organization has to be explicit about priority.
A critical transformation program is not another initiative competing for attention. It is a redefinition of how the business operates. If that is true, it has to be treated as such in how decisions are made, how conflicts are resolved, and how time is allocated.
Without that clarity, the organization will continue to behave rationally at the individual level and irrationally at the system level.
In simple terms: critical transformation programs do not fail because organizations lack talent.
They fail because the system is designed in a way that keeps that talent elsewhere.