Straight answer

Why does our ERP project keep slipping?

Usually because the go-live date was set before anyone understood the work, and nobody has been asked what must be true for it to hold. ERP projects rarely slip because of one big failure. Data, testing and business readiness each run a little late while the status report stays green.

How can the board tell whether it is under control?

Signs it is under control

  • Each status report lists the conditions for go-live, not just a colour.
  • When a date moves, it moves early and openly, with a reason.
  • The business, not the implementation partner, owns readiness and signs it off.

Signs it is not

  • The programme has reported green for months while milestones keep shifting.
  • Data migration and full testing keep being rescheduled.
  • The cost-to-complete forecast has not been redone since the last slip.

What is the one question to ask?

Ask at the next meeting

What has to be true by the next board meeting for the go-live date to hold?

A strong answer

Three or four named conditions, each with an owner and a date, and a plain view of which one is weakest today.

A weak answer

“We are tracking green overall.”

Why does the date keep moving?

An ERP go-live is the switch from old systems to a new core system for finance, supply chain and operations. It depends on a handful of things finishing together: clean data, tested processes, trained people and a business that is ready to stop using the old system. Each of them can drift by a few weeks without anyone raising an alarm. Together, they move the date by months.

It is worth asking what “green” means in your programme’s reports. Often it means the work has started, not that the condition for go-live has been met. A programme can be green on every workstream and still miss its date.

What might the board be getting wrong?

Be fair to management before blaming them. The date the board approved may have come from the original business case, before anyone had looked closely at the data. Contingency may have been trimmed to get the budget through. A request to cut scope may have been treated as failure rather than good judgement. If any of that happened, part of the slippage was decided in the boardroom.

What should the board ask for instead?

Stop asking whether the programme is on track. Ask what has to be true, by a named date, for go-live to hold, and ask to see those conditions in every report from now on. Ask too what a three-month delay would cost, and how much contingency is left. A team that can answer clearly is in control, even when the news is bad. If the answer comes back as activities and colours, the conditions have probably not been defined yet. That is something to fix together, not a reason to lose confidence in the team.

Where to go from here