Sanjay K Mohindroo
Most transformation failures come from continuing too long. Learn the five board-level tests every CEO and CIO should apply before investing further.
"The most difficult transformation I ever led wasn't the one that failed. It was the one I chose not to finish."
The room fell silent.
Months of planning had gone into the programe. Hundreds of people were involved. Significant capital had already been committed. Every dashboard showed progress. Every steering committee meeting ended with another milestone achieved.
Then I recommended reducing the scope.
Not because the programme was failing.
Because the business had changed.
That recommendation was far more controversial than cancelling an unsuccessful initiative would have been. Cancelling failure is easy to explain. Scaling back something that appears to be succeeding is much harder.
Over three decades leading enterprise technology across industries and geographies, I have learnt that one of the least appreciated leadership skills is knowing when not to continue.
Most transformation programes do not fail because the technology is wrong.
They fail because leaders become emotionally committed to a roadmap that no longer reflects business reality.
The Most Dangerous Assumption in Transformation
There is a belief that perseverance is always a virtue.
It isn't.
Transformation has become synonymous with endurance. Boards admire programes that continue for years. Consultants celebrate multi-year roadmaps. Vendors promote continuous expansion.
The underlying assumption is simple.
If you've started, you should finish.
I disagree.
That mindset confuses commitment with effectiveness.
The purpose of transformation is not to complete a roadmap.
The purpose is to improve business performance.
Those are two very different objectives.
When circumstances change, continuing to execute the original plan can become the highest-risk decision in the room.
Success Can Become the Biggest Risk
One programme I was involved with had clear objectives, executive sponsorship and strong delivery discipline.
The governance was solid.
The milestones were being achieved.
Budgets remained under control.
On paper, it was exactly what every transformation should look like.
Then the company's strategic priorities shifted.
A combination of market conditions and changing commercial realities meant leadership needed to redirect investment toward areas that would produce measurable business impact much sooner.
Nothing about the programme itself had deteriorated.
The business context had.
Continuing the programme exactly as planned would have consumed leadership attention, capital and organizational capacity that were suddenly needed elsewhere.
We had two options.
Continue because the original business case had once been correct.
Or reduce the scope because today's priorities mattered more than yesterday's assumptions.
We chose the second option.
Looking back, that decision probably created more value than completing the original programme ever would have.
Transformation Is Not an Asset. It Is an investment
Boards understand investments.
They also understand sunk costs.
Yet transformation programes are often treated differently.
Once organizations have invested significant money and executive attention, the programme starts acquiring an identity of its own.
It becomes something that must be protected.
Additional phases are approved because earlier phases have already been completed.
New workstreams appear because "while we're doing this, we might as well..."
Budgets quietly expand.
Timelines stretch.
Success metrics become increasingly focused on programme delivery instead of business outcomes.
The transformation begins serving itself.
This is classic sunk cost thinking.
No board would continue funding a business unit purely because substantial money had already been invested.
No CEO would maintain an unprofitable product simply because development took three years.
Yet organizations routinely do exactly that with transformation programes.
Completion becomes the objective.
Value quietly becomes secondary.
The Wrong Question
Whenever executive teams review large programes, the discussion usually revolves around familiar questions.
Are we on schedule?
Are we within budget?
Have milestones been achieved?
Have risks been mitigated?
These are important operational questions.
They are not strategic questions.
The real question is much simpler.
If we were making this investment for the first time today, knowing what we know now, would we still approve it?
That single question changes the conversation completely.
Because it forces leadership to ignore history.
It removes emotional attachment.
It removes sunk costs.
It removes organizational pride.
Instead, it evaluates the programme against today's business priorities.
That is exactly how capital allocation decisions should work.
Transformation deserves the same discipline.
Why Leaders Keep Going Anyway
If the answer is obvious, why do organizations continue programes that no longer make strategic sense?
In my experience, there are four recurring reasons.
1. Nobody Wants to Admit the Context Changed
Changing direction is often interpreted as admitting failure.
Executives worry about credibility.
Programme sponsors worry about reputation.
Project teams worry about morale.
So, everyone continues.
Not because it remains the right decision.
Because changing course feels politically harder.
Ironically, boards rarely criticize thoughtful course corrections.
They criticize organizations that ignore obvious reality.
2. Success Is Measured by Delivery, Not Outcomes
Large programes develop their own reporting structures.
Delivery milestones become the language of success.
Green dashboards create confidence.
But green dashboards do not necessarily create shareholder value.
I've seen programes receive excellent delivery ratings while producing very little measurable competitive advantage.
Execution quality is important.
Business relevance is more important.
3. Scope Expands Faster Than Value
Transformation rarely stays the same size.
Every department identifies additional opportunities.
Every vendor proposes another capability.
Every steering committee finds another dependency.
The programme gradually shifts from solving a business problem to modernizing everything.
Eventually, nobody remembers where the original value was supposed to come from.
Scope becomes momentum.
Momentum becomes strategy.
That is dangerous.
A Board-Level Framework: The Five Tests Before You Continue
When business priorities change, I encourage leadership teams to resist making emotional decisions.
Instead, apply five simple questions.
These are not technology questions.
They are business questions.
1. Is the original business problem still the business's biggest problem?
The reason you started may no longer be the reason you should continue.
Markets change.
Customers change.
Regulation changes.
Competition changes.
Capital becomes more expensive.
Growth priorities evolve.
If the original problem has fallen down the strategic agenda, the programme should not automatically retain its original priority.
Business relevance must always outrank historical commitment.
2. Would we approve this investment today?
Ignore everything already spent.
Ignore completed phases.
Ignore political ownership.
If this proposal arrived in today's investment committee, would it still receive funding?
If the answer is no, leadership already knows what needs to happen.
3. Are we creating competitive advantage, or simply keeping busy?
Every transformation reaches a point where activity can be mistaken for progress.
New workstreams are launched. Additional capabilities are added. More teams become involved. Steering committee meetings become longer. Dashboards become more detailed.
The programme appears healthy because everyone is working hard.
But effort is not the same as advantage.
Boards should ask a tougher question.
What measurable business outcome will this next phase create that competitors will struggle to replicate?
If the answer is vague, the programme is probably entering the law of diminishing returns.
Technology should create differentiation, improve resilience, increase speed, or strengthen customer value.
If it is merely modernising for the sake of completeness, it is consuming capital without strengthening the business.
4. What is the opportunity cost of continuing?
This is the question that is often missing from transformation governance.
Every pound, dollar, or rupee committed to an existing programme is capital that cannot be invested elsewhere.
Every senior executive spending time reviewing transformation dashboards is time not spent on growth, customers, acquisitions, or new markets.
Every specialist assigned to a programme is unavailable for another strategic priority.
Transformation programes are rarely evaluated against alternative investments.
They should be.
A board would never approve a capital allocation decision without considering opportunity cost.
Technology investments deserve the same discipline.
Sometimes the right decision is not to stop because the programme is underperforming.
It is to stop because another opportunity now offers a better return.
5. Can we stop with confidence, or are we simply afraid to?
This is ultimately a leadership test.
Fear keeps many programes alive long after their strategic value has declined.
Fear of criticism.
Fear of admitting circumstances have changed.
Fear that teams will interpret a reduced scope as failure.
In reality, mature organisations understand that strategy is dynamic.
Markets evolve.
Customer expectations shift.
Economic conditions change.
No credible board expects a three-year roadmap to remain untouched.
The question is not whether plans will change.
The question is whether leadership dares to acknowledge it.
Reducing Scope Is Not the Same as Losing Ambition
One misconception deserves addressing.
Whenever I argue for stopping or reducing a transformation programe, someone inevitably says, "Won't that send the wrong signal to the organization?"
Only if it is communicated poorly.
There is an important difference between abandoning a vision and adjusting the route.
A transformation should have a stable destination.
The roadmap to reach it should remain flexible.
The organizations that adapt fastest are not constantly changing direction.
They are constantly reassessing whether the next investment still serves the destination.
Reducing scope should never mean lowering ambition.
It should mean concentrating effort where it creates the greatest business value.
That distinction matters.
The Counterargument: Doesn't Stopping Create Transformation Fatigue?
A reasonable concern is that changing direction too often can erode confidence.
Employees begin to believe every initiative will eventually disappear.
Business sponsors hesitate to commit.
Momentum is lost.
That risk is real.
But it usually stems from poor governance, not from stopping itself.
Transformation fatigue is created when organizations repeatedly launch programes without clear business outcomes, continually redefine success, or chase the latest technology trend.
Stopping a programme for disciplined strategic reasons has the opposite effect.
It demonstrates that leadership is serious about capital allocation.
It reinforces that transformation exists to serve the business, not the other way around.
In my experience, people lose confidence when leaders refuse to make difficult decisions.
They gain confidence when those decisions are explained clearly and backed by evidence.
What Boards Should Expect from Every Transformation
Before approving another phase of funding, I believe every board should insist on five things.
1. A refreshed business case. Not the one written two years ago, but one based on today's strategic priorities.
2. Evidence of realized value. Focus on measurable business outcomes, not completed milestones.
3. An opportunity cost assessment. What alternative investments are being deferred by continuing?
4. A clear stop, continue, or reduce recommendation. Management should not present continuation as the default option.
5. A defined exit point. Every transformation should have conditions under which it will end, pause, or be scaled back.
If these conversations become routine, transformation governance changes fundamentally.
Programes stop becoming permanent fixtures.
They become investments that must continually earn the right to continue.
The Leadership Test That Matters Most
Looking back over the transformations I have been involved with, I do not judge success by whether every milestone was completed.
I judge success by whether the organization emerged stronger.
Sometimes that meant accelerating investment.
Sometimes it meant expanding the programe.
And occasionally, it meant reducing the scope of something that appeared to be succeeding because the business needed something else more.
Those were never easy decisions.
They were certainly unpopular at the time.
But leadership is rarely about defending yesterday's roadmap.
It is about making today's best decision with tomorrow's business in mind.
Transformation is not a promise to finish everything you started.
It is a commitment to invest where it creates the greatest value.
Sometimes the smartest transformation decision is not knowing how to begin.
It is knowing when to stop.