What an operations diagnostic is, and what you get at the end of one
A diagnostic turns "things feel slow" into a measured, written answer about where your time and money go. Here is what happens during one and what you walk away with.
Most operational problems are felt long before they're understood. Everyone agrees things are slow, or messy, or too dependent on a few people, but nobody can say exactly where the time goes or what fixing it would be worth.
An operations diagnostic exists to close that gap. It's the first paid stage of every engagement we run, and it's designed to be useful even if you never hire us for anything else.
What happens during one
A diagnostic typically takes two to three weeks. It's mostly observation and measurement, not workshops.
We watch the work as it actually runs
Not the documented process. The real one. We sit with the people doing the work and follow jobs, quotes, orders and invoices from start to finish. The gap between how a process is supposed to work and how it actually works is usually where the cost is hiding.
We measure three things
- Cycle time: how long something takes from start to finish, including the time it sits waiting.
- Touch count: how many times a person has to handle it along the way.
- Rework: how often it has to be fixed, chased or redone.
These three numbers show waste far more reliably than opinions do, and they become the baseline everything afterward is measured against.
We review the systems you already have
Most businesses already own more software capability than they use. Part of the diagnostic is working out what you have, what it can already do, and where data gets stranded between systems.
What you get at the end
A written assessment. It covers:
- Where the time and money go, with numbers rather than impressions.
- The three to five changes worth making first, ranked by what they'd remove and what they'd cost.
- What we'd remove rather than automate. Often the fastest gains come from cutting steps nobody needs.
- What we'd leave alone. Not everything is worth fixing, and saying so is part of the job.
The document is yours whether or not we continue. You can act on it yourself, hand it to your own team, or take it to another firm.
Why not skip straight to the fix?
Because it's very easy to spend a lot of money solving the wrong problem. A new system bought before the diagnosis tends to get fitted around the old process, keeping all of its problems while adding a new subscription.
The diagnostic is also the only way to know afterward whether the work paid off. Without a baseline, "it feels better" is the best anyone can say. With one, you can see exactly what changed.
What comes after
If the findings justify it, the next stages are design, build and handover: writing the plan in full, building it in pieces that each stand on their own, running the new way alongside the old one until it's proven, and leaving your team able to run it without us.
You can stop after any stage. Each one produces something concrete you can hold us to.
If you're not sure whether your problem warrants a diagnostic at all, that's what the first conversation is for. Get in touch; it costs nothing, and we'll tell you honestly if it isn't worth doing.