Operations9 min readPublished 29 August 2026

Your ERP Is Not a Management System

Software can organise transactions and make information visible. It cannot define the right process, correct weak data, hold a manager accountable or decide what happens next. Build the management system first.

The new ERP goes live after months of workshops, data cleaning and painful decisions. The system was meant to create one version of the truth. Six months later, production still has a private spreadsheet, the warehouse relies on a whiteboard and finance is correcting transactions at month end. The management team spends more time arguing about the numbers than acting on them.

The conclusion is usually that the software is wrong. Sometimes it is badly configured. More often, the business expected a software platform to solve problems that belong to management.

You cannot buy accountability off the shelf. Software records what happened. Management decides what happens next.

The ERP Illusion

A good ERP can connect sales orders, purchasing, stock, production, quality, dispatch and finance. That is valuable. But it cannot decide how those functions should work together. If order priorities are unclear before implementation, they will still be unclear afterward. Only now the disagreement happens inside a more expensive system.

Software exposes the operating model you already have. Clear processes become easier to repeat. Weak processes become easier to repeat too. When the business automates confusion, the result is faster confusion with better-looking dashboards.

What the Software Cannot Do

The Five Layers Of A Real Management System

Define the standard processThe business must agree how work should move, what information is required and where decisions sit. The ERP can enforce a process only after management has chosen the right one.

Assign data ownershipEvery critical field needs an owner and a standard: lead times, bills of material, stock, routings, costs, delivery dates and customer terms. Data quality is a management responsibility, not an IT clean-up exercise.

Create the review rhythmInformation becomes useful when the right people review it at the right frequency. Daily exceptions, weekly operations and monthly commercial performance require different conversations and decisions.

Make accountability visibleWhen a date, cost or quality result misses the standard, someone must own the response. The system can flag the exception. It cannot have the honest conversation or insist on follow-through.

Define decision rightsManagers need to know what they may change, approve or escalate. Without decision rights, the ERP becomes another route for sending every problem back to the founder.

Fix the Process Before Configuring It

Before configuring a critical workflow, map what should happen from start to finish without discussing screens or software menus. What triggers the process? Which information is required? Who owns each step? Where does approval add value? Which exceptions genuinely need escalation? What outcome proves the process worked?

This often reveals unnecessary approvals, duplicate entry and habits that grew around individual people. Do not pay a consultant to automate every historical workaround. Simplify the process, agree the standard and then use the software to support it.

One Number Needs One Owner

If sales believes the delivery date means one thing and production believes it means another, the dashboard is not the problem. If nobody owns routing times, capacity planning will be unreliable. If stock accuracy belongs vaguely to the warehouse team, purchasing recommendations will always be questioned.

Name the person responsible for the definition, accuracy and correction of each critical data set. That person may not enter every record, but they own the standard. Shared ownership sounds collaborative and usually produces an argument.

Stop Building Shadow Systems

Private spreadsheets usually appear because the official system is slow, unclear or not trusted. Simply banning them will not solve the cause. Ask what decision the spreadsheet supports, why the ERP cannot support it and whether the problem is configuration, training, data or process design.

The Rule

A temporary workaround must have an owner, a reason and an expiry date. Otherwise it becomes a permanent second system, and the business loses the single source of truth it paid for.

Run the Business, Not the Dashboard

A red indicator does not improve performance. The value comes from the management response. What changed? Why? What is the operational and commercial impact? What options exist? Who will act? By when? When will the team know the action worked?

Keep the rhythm focused. Use the ERP to prepare the truth, not to create lengthy presentations. The meeting should move quickly from data to decision and from decision to named ownership.

Your Action Checklist

.Choose one process that still fails despite being in the ERP and map how it should work
.Assign clear owners to the critical data behind planning, stock, cost and delivery
.Identify every shadow spreadsheet and decide whether to integrate, replace or retire it
.Create a short weekly exception review that ends with actions, owners and deadlines
.Fix process, ownership and training before buying another module or custom report

Final Thought

An ERP can become a powerful operating backbone. But software will not provide discipline that leadership has avoided. Put clear processes, good data, management rhythm and decision rights around the system, and it will earn its place. Leave those gaps open, and it becomes an expensive record of the same old problems.

The ERP should support the way a well-managed business works. It should never be mistaken for the management itself.

Put This Into Practice

Find Where Your Business Is Stuck

The CEO Scorecard gives you a clear view of the constraints affecting profit, cash, the team and your time.

Take the CEO Scorecard Explore CEO Advisory

Back to all articles