Every operations team has a feeling that something is slow. Almost none of them can say what, exactly, or what it costs. That gap is usually the whole problem: not the process itself, but that nobody has ever measured it. You do not need a consultant to close it. You need two hours and a notebook.
Start with the Monday morning test
Pick the process that makes someone sigh when it comes up. Usually it involves a spreadsheet, an inbox, or both. Sit with the person who actually does it, not their manager, and watch one full cycle start to finish. Do not ask them to describe it. Descriptions are always cleaner than reality.
Track four numbers for one week
How many times does this happen per week? How long does one cycle take, door to door? How often does it go wrong and need rework? What happens when the person who owns it is out sick? Write down real numbers, not estimates. Most teams are shocked once they count instead of guess.
What counts as worth fixing
Our rule of thumb: if a team does something manually more than ten times a week, it is worth automating. Below that, fix it with a checklist, not a system. The build cost rarely pays back. Above ten times a week, every one you wait on is a week you paid the manual tax again.
What this does not replace
This exercise will not tell you how to fix it, what it will cost, or which of your six broken processes to fix first. That is a prioritization call, and it is genuinely hard to make about your own business. But you walk into that conversation with real numbers instead of a vague sense that things are slow. That alone changes it.