Insights

Why we build around the process, not the software

Close-up of network cables connected to a patch panel

Most ERP projects fail for the same reason: the business is asked to reshape itself around a product. We start the other way round.

Enterprise resource planning has a reputation problem. Projects run late, cost more than planned and leave staff working around the system rather than with it. Spreadsheets reappear within months. The expensive new platform becomes a very sophisticated place to re-key data.

The cause is rarely the technology. It is the order in which decisions are made.

The usual sequence — and why it fails

A typical project begins with a product demonstration. A platform is chosen, configuration starts, and the business is then mapped onto the modules the product happens to offer. Where the real process does not fit, the process is told to change.

Sometimes that is right. A standard process is often a better process. But in operationally intense businesses — multi-depot distribution, temperature-controlled logistics, regulated transport — the awkward exceptions are frequently where the margin, the risk and the customer promise actually sit. Force them into a generic workflow and they move into email, phone calls and private spreadsheets, invisible to everyone else.

Starting with the process

When we built an operations and ERP platform for a multi-depot foodservice distributor, the first months involved very little software. We followed the work: order intake, picking, loading, routing, delivery, returns, credits and invoicing, across day and night shifts and across sites.

Three questions shaped everything that followed:

  1. Where does information enter the business, and who owns it? One order, one customer record, one price — entered once, trusted everywhere.
  2. Where do decisions actually get made? Not where the organisation chart says, but where the night shift supervisor decides what goes on which vehicle.
  3. Where does work fall between the gaps? Credits that are never raised, short deliveries never invoiced correctly, temperature records kept on paper and lost.

Only once the process was clear did we design the data model and the screens. The system reflects how the operation runs, and where the process needed improving, we improved the process first and built the better version.

What that changes

  • Adoption is not a battle. People recognise their own work in the system, so they use it.
  • Reporting becomes possible. When data is captured once at source, margin by customer, cost to serve by route and performance by shift stop being guesses.
  • The business can change. A system designed around a clear process can be extended as the process evolves, without starting again.
  • Knowledge stops walking out of the door. The way the business works is written into the system, not held in a few people’s heads.

Bespoke, packaged or both

This is not an argument for building everything from scratch. Accounting, payroll and many standard functions are best served by proven products. The point is to decide deliberately: buy where the process is standard, build where the process is your advantage, and integrate the two so information moves without re-keying.

Our view

Technology should make a well-run business easier to run. It cannot make a poorly understood business well run. Start with the process, design the information around it, and choose — or build — the software last.

If your systems no longer fit the way your business actually works, we would like to hear about it.