Automating an enterprise starts with a map of processes and losses; buying a system comes later. First the process itself is put in order, then the systems already in use are connected, and only after that is something new added. What works and does not hold back growth is left as it is.
Three questions before you start
- Where is the company losing? Downtime, rework, waiting for approvals, lost enquiries, manual transfer of data between systems.
- What should change in the numbers? Order lead time, equipment utilisation, the defect rate, the time it takes to prepare a report.
- Who answers for the area? Without a process owner, any system turns into one more place where data is entered.
The order of work
- A map of processes. How an order, money and documents actually pass through the company, not how the regulations say they should.
- Bottlenecks. Where work stands still, is duplicated or depends on one person.
- Priorities. Each area is assessed on two axes: what effect a change will have and what it puts at risk.
- Order in the process. Unnecessary steps are removed before automation. A bad process stays bad after automation; it just runs faster.
- Connect what exists. The accounting system, production, warehouse and sales are often already there. Exchanging data between them gives more than replacing any one of them.
- Automate one area. One, with a measurable result. The old way runs in parallel until the new one has proved itself.
- Train people and measure. Then move on to the next area.
What to leave alone
- Systems that do their job and do not hold back growth. The age of a program is not a reason to replace it.
- Areas where manual work is rare and cheap.
- Processes that will soon change for another reason: a reorganisation, a new product, a relocation of production.
Signs that automation has gone wrong
- Employees keep parallel records in spreadsheets.
- A report from the new system has to be checked by hand.
- The project is run by the software vendor, and nobody answers for it on the company’s side.
- Deadlines and budget are discussed more often than the result of the area.
The owner’s role
The owner does not need to understand the software. Three things are required of them: to name the goal in numbers, to appoint the people responsible and to look at the result once a week. The rest is done by the team, internal or external.
If it is unclear which area to start with, an audit helps: a short study that leaves you with a map of the company and a plan with priorities. How automation grows into management by data is covered in the note on digital transformation.