The Most Expensive Moment in an ERP Program Is the One Where Nobody Speaks

Most ERP programs don’t fail suddenly. They drift. And the drift almost always starts in the same place: a meeting where someone noticed something and decided not to say it.

The silence that looks like good governance

Steering committees are designed to keep things calm. There is an agenda, a status report and a set of milestones, and the meeting is meant to move through them in order.

That structure is useful, but it has a side effect. It rewards keeping the peace, and it quietly penalises disruption.

So when a committee member senses that the reported status doesn’t match reality, the easiest path is to say nothing. The milestones are green. The project manager seems confident. Raising a concern would mean challenging someone in front of the sponsor, slowing the meeting down and perhaps looking difficult.

The concern gets noted privately, and the meeting moves on.

That is not a failure of intelligence. It is a failure of courage at the moment courage is cheapest.

Why the cost compounds

An unraised concern does not stay the same size.

Month one: the gap between the report and reality is small. Raising it costs one awkward conversation.

Month three: the gap has widened. Raising it now means explaining why nobody raised it earlier. The personal cost of speaking has gone up, so silence becomes more likely.

Month six: the issue can no longer be hidden. It is not a conversation any more. It is a recovery, with budget variations, schedule resets, vendor disputes and a breakdown of trust between the committee and the delivery team.

Every month of silence adds interest. By the time the bill arrives, the organisation is paying for the original problem and for every month it was left alone.

The signs your program is accruing this debt

In my work with WA local governments and Aboriginal corporations, I see the same signals again and again:

• Status reports stay green while informal conversations turn anxious.
• Committee members raise concerns one-on-one but not in the meeting.
• Questions are framed as “just checking” rather than “I am concerned.”
• The same risk appears on the register month after month with no change in rating.
• Nobody can clearly explain what would cause the project to report amber.

None of these is a crisis on its own. Together, they show a governance forum that has stopped testing what it is being told.

Choosing when to pay

Not every concern deserves escalation. Part of good governance is knowing what to let pass.

The risk is not that executives sometimes choose to let things go. The risk is that they stop choosing at all, and silence becomes the default because it feels like diplomacy.

Every program pays for its unresolved issues eventually. The only question is whether it pays early and deliberately, while the cost is small, or late and under pressure, when every option is expensive.

Where independent oversight helps

That is the gap independent oversight is designed to fill.

An independent adviser has no stake in keeping the meeting comfortable, no reporting line to protect and no vendor relationship to preserve. That makes it far easier to ask the question in the room while it is still cheap to answer.

If your program has started to feel calmer in the meeting than it does in the corridor, that difference is worth examining now. An Executive Visibility Review gives you an independent picture of where your program actually stands, before the interest comes due.