PORTFOLIO MANAGEMENT
The Hidden Cost of Bad Projects: Why Killing an Initiative Early Can Be a Win
A cancelled project often looks like failure. Sometimes it is the exact opposite. The real economics of an initiative go far beyond its visible budget.
Challengine · 23 September 2026 · 4 min read
A cancelled project often looks like failure.
Sometimes it is the exact opposite.
If an organization discovers early that a €500,000 initiative is unlikely to create enough value, stopping it before execution may be one of the best investment decisions it makes that year.
The problem is that organizations usually see the visible project budget.
They don't always see the true cost of saying yes.
A project costs more than its budget
Imagine a project with a €200,000 implementation budget.
Its real cost might look very different.
| Cost | What it includes |
|---|---|
| Direct investment | Software, consultants, equipment and implementation |
| Internal resources | Employee time, management attention and specialist capacity |
| Change cost | Training, communication and process changes |
| Delay cost | Value lost while implementation takes place |
| Opportunity cost | Better initiatives that cannot be funded or staffed |
| Execution risk | The possibility that expected benefits never materialise |
This changes the investment question.
Instead of:
"Can we afford this project?"
Ask:
"Is this the best use of our capital and capacity?"
The opportunity cost is often invisible
Suppose two initiatives require the same implementation team.
Project A could create €250,000 of annual value.
Project B could create €800,000.
Starting Project A first does not only cost its project budget.
It may also delay Project B.
That lost value rarely appears in the original business case.
But it is very real.
This is why initiatives should not be evaluated individually. They should be compared against the other ways the organization could use the same resources.
The dangerous sentence: "We've already invested so much"
Once an initiative starts, stopping becomes psychologically difficult.
Three months of planning becomes six months of development.
Six months becomes a year.
Eventually the argument for continuing becomes:
"We can't stop now. We've already invested too much."
But money and time already spent should not determine whether the next euro should be invested.
The better question is:
Knowing what we know today, would we still approve this initiative?
If the answer is no, continuing simply increases the cost of the original mistake.
Define the exit before starting
A strong business case should include conditions for continuing, and conditions for stopping.
For example:
| Trigger | Decision |
|---|---|
| Expected ROI remains attractive | Continue |
| Costs increase significantly | Re-evaluate |
| Critical dependency fails | Pause |
| Expected benefit disappears | Stop |
| Better alternative emerges | Compare again |
This turns stopping from an emotional decision into a normal part of investment governance.
Killing projects is not the goal
The objective is not to cancel more projects.
It is to invest in fewer weak ones.
Good portfolio management means being able to say yes, not yet and no with confidence.
Every weak initiative stopped early releases capital, capacity and attention for something better.
And sometimes the highest-return investment decision is the project you decide not to start.