Straight answer
Should we stop our ERP programme?
Usually no, unless the business case no longer holds at today's remaining cost and date, or a reset has already failed to produce a credible route to go-live. Most troubled programmes need a pause, a reset and a smaller first release, not cancellation. Decide on the cost and value still ahead, never on the money already spent.
How can the board tell whether it is under control?
Signs it is under control
- Management can show the remaining cost and the remaining benefit side by side, refreshed since the last slip.
- A smaller first release has been costed, with the business agreeing what it can live without.
- The sponsor has said in writing what would make them recommend stopping.
Signs it is not
- The main argument for continuing is how much has been spent so far.
- The business case has not been refreshed since the board approved it.
- Each reset ends with a new date and the same scope, team and plan.
What is the one question to ask?
If we were starting today, knowing what we now know, would we approve this programme at its remaining cost?
A strong answer
A plain yes or no, backed by a refreshed cost to complete, the benefits still realistic, and the options considered (continue, reduce scope, pause, stop) with the cost of each.
A weak answer
“We have come too far to turn back now.”
When is stopping the right call?
Stopping is right when the reasons for the programme have gone. The business may have changed shape, the benefits may have shrunk, or the remaining cost may now exceed what the outcome is worth. It is also right when the programme cannot describe a credible route to go-live, even after a reset. In those cases, every further month adds cost without adding certainty.
Most programmes that come to the board in trouble are not in that position. They are late and over budget, but the need for a new core system is still real. The old systems still have to be replaced at some point. For them, the useful choice is between carrying on as before and changing something material: scope, sequence, supplier arrangements or leadership.
What might the board be getting wrong?
Boards often frame this as a choice between full speed and cancellation, because that is how the paper is written. That framing pushes management to defend the plan rather than to offer honest options. Directors may also be weighing the money already spent, which cannot be recovered whichever way the board votes. And if the board has punished earlier bad news, it should not be surprised that the trouble arrived late and all at once. Before questioning the team’s judgement, ask whether the board made it hard to say “stop” earlier.
How should the board make the decision?
Ask for a short options paper, not a recovery plan. It should set out at least three choices, with the cost to complete, the benefit still expected and the main risk of each. Ask who outside the programme has tested the numbers. Agree in advance what evidence would change the decision, so the next review is a check against that, not another debate. If the board decides to continue, it should be a fresh decision with a fresh set of conditions, minuted as such. If it decides to stop, plan the exit as carefully as the go-live: what is kept, what is written off, and how the business keeps running on the old systems.