The system got bought, the training happened, the teams use it every day. A year on, someone asks in a meeting whether operations are better than they were — and the room goes quiet.
It isn't reluctance. It's that nobody can answer, because the only thing there is to compare is today's impression against a year-old memory. And memory, in these matters, is a terrible witness: it either flatters the past or flatters the investment.
Turnover doesn't help here
The temptation is to look at sales. It's the number that's always to hand, and it's the worst possible indicator for judging a management system.
If turnover went up, it might have been the system, the market, the new salesperson, or a big client who happened to turn up. If it went down, the same applies in reverse. You can never separate out each factor's contribution, and the arguments that follow go nowhere.
What management technology changes is operational, and that's where it has to be measured.
Four measurements you can take without any tools
- Hours a week spent moving information from one place to another. Ask the people who do it, don't estimate. It's usually more than any manager assumes.
- Days between the start and end of a process. Pick one type of job and track ten cases from start to finish.
- How many times a week someone corrects a piece of data by hand because it came through wrong from another system.
- How many days after month-end the management report is ready — and how long it took to put together.
That's four numbers. They fit on a sheet of paper, need no dashboards, and nobody has to install anything to get them.
Missed the before? Measure today anyway
The usual advice is to record the starting point before you implement. True, and useless for anyone who implemented two years ago.
The way out is simple: measure now, write the four numbers down somewhere they won't get lost, and measure them again in three months. You've lost the comparison with the past, but you gain the comparison with the future — and that's the one that actually helps decide what to do next.
And if you're preparing a new rollout, make the most of it: measure in the week before switching anything on. It's two hours of work worth more than the report your supplier will hand you.
When the answer is "it hasn't improved"
It happens, and it doesn't necessarily mean you bought the wrong thing. There are three explanations more likely than the fourth.
It's being used at half throttle. Half the features were never configured, and people keep doing outside the system what it would already handle.
The process around it never changed. A new tool got bolted onto an old workflow. The tool does what it can; the workflow calls the shots.
It's isolated. It does its own part well and talks to nothing else, so someone still transcribes by hand — and that transcription is what's eating the hours.
Only after ruling out these three does it make sense to question the choice of system. None of them gets solved with training.
Measuring also protects the next investment
There's a useful side effect here. A company with four numbers before and four numbers after can defend its next budget with evidence instead of conviction — and can also say no to a supplier promising what's already been shown not to happen.
It's the same discipline we ask for before any process automation project: state upfront, in numbers, what's expected, then measure again afterwards.
Not sure if what you have is paying off?
Tell us what systems you use and where manual work still lingers. We'll help you measure it and find out where the waste is.