Our IT project is getting out of hand. How do we regain control?

When an ERP project gets out of hand, you do not regain control with more speed, but with a sober assessment. It shows within days where the project really stands, in scope, data and responsibility. Only this clarity makes control tangible again. The decision follows afterwards, not before.

How do you recognise that the overview is missing?

Out of hand almost always means the same thing: the overview is missing. No one can say with certainty anymore what is done, what is open and who decides what. In this state, acting fast feels right, but makes it worse, because you navigate without a map.

The most reliable sign is not the postponed date but the disagreement about where things actually stand. When two people describe the same project status differently, no information is missing; a decision about what counts is missing. From that point on, no further status meeting helps.

The first step is therefore not a new plan, but an assessment. It soberly examines scope, schedule, budget, data quality, open items and the actual maturity of the delivery, measured against the original requirements. This diagnosis takes days, not weeks, and it is the map you need to take control again.

How do you regain control?

Regaining control means three concrete things, and in this order, because each step is what makes the next one possible:

• A scope freeze, so the project does not keep growing while you get your bearings.
• An honest assessment that separates symptom and cause.
• A clear assignment of who makes which decision bindingly.

The scope freeze is the least popular and the most effective step. It costs nobody any money, but it buys exactly the calm in which a diagnosis can stay valid at all. Without it you are assessing a state that has already changed while you were assessing it.

Without the third point, any steering stays theoretical, because the open questions simply sit there. The useful test for it is a single question: who decides the next conflict between the date and data quality, and by name?

Why does the decision belong at the end?

Only on that basis does the solid decision follow: carry on with corrected steering, set individual parts up again, or secure the foundation before the next date is set. That decision belongs at the end of the diagnosis, not at the start, otherwise you are only guessing faster than before.

The reason is simple: all three routes are defensible, but they rest on different findings. Whoever settles on the route beforehand then only looks for the evidence to support it, and that is exactly how second attempts arise that repeat the same mistakes. Control stays on your side, with Business Central as home.

So before you take the next step, get hold of the map first: arrange a first conversation for a short, senior-led assessment that shows where you stand and how you regain control.