The ERP implementation drags on forever. Why?

When an ERP implementation drags on endlessly, the system is rarely the reason. Three things almost always are. The first is unresolved processes: if they are only clarified while the project runs, the team debates anew every week instead of building, and every debate pulls decision-makers out of day-to-day business. The second is the data foundation. An unclean foundation only shows itself during migration, and then it costs unplanned rounds right in the critical path. The third and most expensive is missing decision governance: where it is not settled who may decide what, every open question simply sits there while everyone's cost clock keeps running. A useful early indicator is decision latency, the time between a question being raised and a decision being made. It rises measurably long before the deadline visibly breaks. A short, senior-led stocktake reveals within days where the time is going.

What are the three time sinks?

Three time sinks explain almost every delay. The first is unclarified processes: if they are only settled during the project, every week brings new discussion instead of building, and every discussion pulls decision-makers out of the day job. The second is the data foundation. An unclean base only shows during migration, and then it costs unplanned rounds right in the critical path.

The third and most expensive is missing decision control. Where it is not defined who may decide which question, every open question stays open. Everyone's cost clock keeps running without progress. Decision latency is worth tracking as an early indicator: the time between a question being raised and a decision being made. It rises measurably long before the date visibly breaks.

What rarely helps is additional staff. When decisions are stuck or the scope is growing, more people merely spread the waiting across more of them.

What does a project stocktake deliver?

A stocktake makes visible within days where the time is actually going, instead of pushing the plan back again. It checks the remaining effort on an actuals basis, the number of open scope items, the test coverage of the core processes and the decision latency of recent weeks. These four values fit on one page and answer whether the plan can still be healed.

An implementation can then be accelerated through decisions, not pressure: accept the standard, cut the scope small, give decision-makers time, cleanse data early. For distributing settings and master data, Business Central offers configuration packages that considerably shorten repetitive setup work.

Source: Microsoft Learn: Set up company configuration packages

What the stocktake does not deliver is a new wishful date. It provides the basis on which your organisation can set a solid one. Control stays on your side throughout, with Business Central as home.