Another status meeting won’t fix a stalled implementation
Why stalled ERP and enterprise software implementations rarely recover through more reporting — and the one question that does move them.
Every stalled implementation has a rhythm. A weekly status meeting. A monthly steering committee. A RAG report that has been amber for so long that nobody notices any more. An issue list with a few hundred lines, colour-coded.
None of this is laziness. People are working hard. The problem is that the governance has quietly changed its job. It used to steer delivery. Now it mostly documents why delivery hasn’t happened.
How you can tell
A few signs that the meetings have stopped being part of the solution:
- The same issues come back week after week with new comments but no new decisions.
- Most of the discussion is about the past: who agreed what, when, and what the contract says.
- The go-live date is discussed as a forecast, not a commitment.
- Different parties bring different versions of the same list.
- Senior people leave the room less sure than when they came in.
When that happens, more reporting doesn’t help. A more detailed plan doesn’t help. A new project manager often doesn’t help either, because the problem isn’t the quality of the administration.
The question that does help
The useful question is blunt: what is actually preventing this investment from becoming operational?
Not “what is the status?”, and certainly not “whose fault is it?”. What, specifically, stands between today and a working system in daily use?
The honest answer is usually shorter than the issue list. In most stalled implementations a handful of blockers matter — a missing decision, an unclear acceptance criterion, an integration nobody owns, a go-live scope that has quietly grown to include everything anyone ever wanted. The rest is noise that has accumulated around them.
Why it takes someone from outside
Everyone inside the project has a position, and usually a reasonable one. The customer has paid and wants what was promised. The supplier has delivered a lot and wants to be paid. Users want something that works for them. Each of them is partly right, which is exactly why nobody can move.
An independent view doesn’t replace those people. It gives them a shared picture of the real blockers — and a way to act on it without anyone having to lose face first.
That is the moment a project starts moving again. Not because anyone won the argument, but because everyone started pointing at the same problem.