How do I recognise that my ERP project is failing?

Five warning signs are more reliable than any status meeting: the go-live has been postponed more than once, the budget is exceeded, data quality stays poor, the project team is chronically overloaded, and no one can say clearly who makes which decision. If two or more apply, a course correction is overdue.

Which five warning signs count?

Five signals are more reliable than any status meeting. First the date: the go-live has been postponed twice or more without the underlying plan changing. Second the budget: costs have left the agreed frame, and the forecast rests on assumptions rather than actuals.

Third the data: data quality stays poor despite the migration, and reports have to be debated before anyone believes them. Fourth the team: the project team is permanently overloaded, tickets pile up, and key users fall back into the day job. Fifth governance: decision paths are unclear and nobody is steering with authority.

A single signal is everyday life in any project. When two or more apply at once, corrective action is overdue, and not at the level of symptoms. Decision latency works well as a measurable early indicator: the time between a question being raised and a decision being made.

How do you separate symptom from cause?

In an ERP project, symptom and cause lie far apart, and confusing them is expensive. The postponed date is a symptom. The cause usually sits weeks earlier: a scope that was not documented and agreed, data that was not cleansed, or a decision nobody was allowed to make. Postponing the date without touching the cause means postponing it again.

The practical test is simple: ask what has changed substantively in the plan. If only dates have moved back, the cause was not addressed. If scope, staffing or decision paths have changed, something has happened.

A structured assessment therefore examines four dimensions together: schedule reality, budget integrity, scope clarity and governance effectiveness. Several signals at once almost always point to a structural cause, and that is only found by looking at all four together. Control stays on your side throughout.