Sanjay K Mohindroo
After three decades leading enterprise IT, here's why killing the wrong transformation program can create more value than completing it.
The Transformation Programs I Have Killed, And Why It Was the Right Call
A CEO once asked me a question that changed the course of a nine-figure transformation.
"Are we too far in to stop now?"
My answer was immediate.
"No. We're just early enough to avoid making a very expensive mistake."
We shut the program down that week.
Months of work stopped. Several consulting teams left. Budgets were reallocated. People questioned the decision.
Eighteen months later, the company launched a completely different transformation. It was smaller, faster, tied directly to business priorities, and delivered measurable returns within the first year.
Killing the first program was not a failure.
It was one of the best transformation decisions we ever made.
That experience wasn't unique. Over nearly three decades leading enterprise technology across industries and regions, I have approved major transformation initiatives. I have rescued others. And yes, I have deliberately killed several.
Not because transformation is risky.
Because continuing the wrong transformation is far riskier.
The Dangerous Myth That Every Transformation Must Continue
Corporate culture has unintentionally created a dangerous belief.
Once a transformation starts, it must continue.
The thinking sounds reasonable.
"We've already invested millions."
"The Board has approved it."
"We've announced it internally."
"The implementation partner is already mobilized."
"We're halfway there."
None of those are business reasons.
They're emotional reasons.
They're symptoms of the sunk cost fallacy, one of the most expensive biases in executive decision-making.
Capital already spent should never determine future investment.
Future value should.
Yet organizations continue funding transformation programs that no longer solve the problems they were created to address.
That isn't leadership.
It's avoidance.
Technology Is Rarely the Real Problem
When transformations fail, technology usually receives the blame.
The platform wasn't mature.
The vendor underperformed.
Integration became too complex.
AI wasn't ready.
Cloud migration took longer than expected.
Those explanations are convenient.
They are rarely accurate.
The real problem is almost always strategic misalignment.
Technology projects begin as business initiatives.
Somewhere along the way, they quietly become technology delivery programs.
Success starts being measured by deployment milestones instead of commercial outcomes.
Suddenly the organization celebrates activities instead of results.
Applications are implemented.
Infrastructure is modernized.
Dashboards are built.
But customers don't notice.
Revenue doesn't improve.
Margins remain unchanged.
Decision-making stays slow.
Nothing meaningful has actually transformed.
The Meeting That Told Me Everything
One experience still stands out.
A global manufacturer operating across four continents had invested heavily in a multi-year digital transformation.
The steering committee reviewed progress every month.
Hundreds of milestones were reported.
Thousands of tasks had been completed.
Every dashboard was green.
Then I asked one question.
"What business metric has improved because of this program?"
The room went quiet.
Not because executives didn't know.
Because nobody had asked the question.
The transformation team could explain architecture.
They could explain implementation.
They could explain timelines.
Nobody could explain commercial value.
That was the moment I knew the program had lost its purpose.
The technology wasn't failing.
The governance was.
Why Boards Need Different Questions
Transformation governance often focuses on execution.
Is the program on schedule?
Is spending within budget?
Are milestones being achieved?
Those questions matter.
But they are secondary.
Boards should begin somewhere else.
Is the original business problem still important?
If we started today, would we fund this program again?
Has market reality changed?
Is this still our highest-return investment?
If those answers become uncertain, stopping deserves serious consideration.
The objective isn't finishing transformation.
The objective is creating enterprise value.
The Conventional Wisdom I Challenge
Conventional wisdom says this:
Successful leaders finish what they start.
I disagree.
Successful leaders finish what still deserves finishing.
Everything else should be questioned.
Persistence is admirable.
Persistence without evidence is expensive.
Business environments evolve faster than transformation roadmaps.
Competitive pressures shift.
Customer behavior changes.
Economic conditions tighten.
Regulatory priorities evolve.
Technology itself changes.
Programs designed three years ago often solve yesterday's problems.
Continuing them simply because they exist creates opportunity cost.
And opportunity cost rarely appears on project dashboards.
The Five Tests Before Every Major Transformation Continues
Over the years, I developed a simple executive framework.
Before approving another funding cycle, I ask five questions.
If several answers become "no," stopping becomes the responsible decision.
1. Does the Business Problem Still Matter?
Many programs continue solving problems that no longer exist.
Markets evolve.
Strategies change.
Customer expectations shift.
The first question should always be whether the original problem remains strategically important.
If the answer is no, the transformation has already become obsolete.
2. Can We Measure Business Value?
Technology metrics are not business metrics.
Servers migrated.
Applications deployed.
Users trained.
Those are implementation statistics.
Boards should instead ask:
Revenue increased by how much?
Operating cost reduced by how much?
Cycle time improved by how much?
Customer retention improved by how much?
If value cannot be measured, it probably isn't being created.
3. Would We Approve This Investment Today?
This may be the single most revealing question.
Ignore previous spending.
Ignore politics.
Ignore internal commitments.
If the proposal landed on today's investment committee agenda, would leadership approve it again?
If the answer is no, continuing makes little sense.
4. Is Leadership Still Personally Committed?
Transformation cannot survive executive indifference.
When senior leaders stop talking about outcomes and start asking only for status updates, momentum disappears.
Technology teams notice.
Business teams disengage.
The program becomes operational rather than strategic.
That is usually the beginning of decline.
5. Are We Creating Competitive Advantage?
Modernization alone isn't transformation.
Replacing old technology with newer technology may reduce technical debt.
That matters.
But competitive advantage comes from changing how the business competes.
Customers should experience something different.
Employees should make decisions differently.
Leaders should allocate capital differently.
If competitors can achieve the same outcome by buying the same software, you haven't transformed.
You've upgraded.
Those are not the same thing.
Isn't Killing a Transformation Too Risky?
A fair challenge.
Stopping a major initiative creates disruption.
It affects credibility.
It impacts people.
It may even attract uncomfortable Board conversations.
But continuing an ineffective transformation creates larger risks.
More capital disappears.
Management attention remains consumed.
Strategic opportunities are delayed.
Confidence erodes gradually instead of visibly.
Visible failure often gets attention.
Invisible waste quietly destroys enterprise value.
That's the greater danger.
The Best Transformations Often Start After the First One Ends
The transformation we cancelled years ago wasn't replaced by nothing.
It was replaced by clarity.
The organization redefined the business objective.
Investment became more focused.
Technology became an enabler rather than the destination.
The second transformation delivered in eighteen months what the first hadn't achieved after several years.
Not because execution improved dramatically.
Because strategy did.
That's an important distinction.
Good execution cannot rescue poor direction.
Leadership Means Knowing When to Stop
We often celebrate executives who launch ambitious initiatives.
We should spend more time recognizing leaders willing to stop them.
Stopping isn't surrender.
It's capital discipline.
It's strategic accountability.
It's evidence-based leadership.
The best CIOs, CEOs, and Boards I've worked with all shared one characteristic.
They were emotionally detached from programs but deeply committed to outcomes.
That's a powerful difference.
Programs exist to serve strategy.
Strategy does not exist to justify programs.
Too many organizations have forgotten that.
Perhaps it's time we remembered.
I'd be interested in your perspective.
Have you ever stopped a major transformation initiative? Looking back, was it the right decision, or do you wish you'd pushed through?
If this perspective resonates, subscribe to Technology Trends or join the conversation by leaving a comment.