STEP 01
FOLLOW THE WORK.
NOT THE ORG CHART.
An operations audit is not an opinion survey and it is not a strategy session. It is an observation exercise. You follow a single unit of work from the moment it arrives to the moment it is finished, and you write down what actually happens.
Here is how to run one yourself this week, without hiring anybody.
Why you follow the work instead of interviewing people
Ask someone to describe their process and you will get the version they believe, which is usually the version from before the last three exceptions became permanent. This is not dishonesty. Nobody holds an accurate model of a process they perform automatically.
So you do not start with interviews. You start with an artifact: one real job, one real lead, one real invoice, one real customer complaint. You trace it. Every time it changes hands, changes system, or waits, you write a line. Interviews come afterward, and they are specific rather than general: not 'how does quoting work' but 'why did this one sit for four days.'
Trace three to five units, not one. One unit gives you an anecdote. Five give you a pattern, and the differences between them tell you where the process is actually improvised.
The four things you are looking for
Waits
Every period where the work exists but nobody is touching it. Waits are almost always longer than the work itself, and they are invisible because nobody is failing during one.
Rework
Anything done twice. Information retyped, a quote rebuilt, a measurement taken again, a file re-requested from a customer who already sent it.
Routing
Every point where the work stops until one specific person answers. Mark who. If the same name appears at five stages, you have found the constraint.
Invisible steps
The things people do that are not in any written process and that nobody mentions, because to them it is not a step. It is just what you do.
Notice what is not on that list: effort, attitude and headcount. An audit that concludes people need to work harder has found nothing. Those four categories all point at structure, which is the only thing you can actually change.
This page is part of a larger body of work — start with Ben Lovro's main site.
The self-audit you can run this week
- Pick one workflow. The one that produces revenue, or the one that generates the most complaints. Not both. Lead to closed job, or job completed to cash collected.
- Pull five recent real examples. Finished ones, from the last sixty days. Not hypotheticals.
- Build a timeline for each. Date and time at every touch. Email timestamps, CRM history, text messages, file dates. The system of record is whatever the evidence says, not what people remember.
- Mark every gap over twenty-four hours. For each one, answer in one sentence what the work was waiting on. A person, a decision, a document, or nothing at all.
- Circle every point that required you. Then write what specifically you supplied: a decision, a piece of knowledge, a relationship, or access to something nobody else can reach.
- List every step not in any written process. Ask each person involved what they did that is not on your timeline. This is where most of the undocumented work surfaces.
That is five examples and a few hours of careful reading. It will be more useful than a strategy offsite.
Reading what you found
Three patterns account for most of what an audit turns up in a small business.
The work is fine and the gaps are enormous. Total hands-on time is small relative to elapsed time. This is the most common finding and it is good news, because closing gaps does not require anyone to work faster. It requires a definition of done and a trigger for the next step.
The same name appears at every stall. Usually the owner, sometimes one long-tenured employee who has become the single source of a particular knowledge. That is not a compliment to them and it is not a character flaw. It is a structural risk with a person's name on it.
Two of your five examples do not resemble each other at all. That means there is no process, only individuals improvising competently. It works until volume rises or that individual has a bad month.
What an audit is not
It is not a performance review. If people believe the timeline will be used against them, you will get a clean timeline and a useless one. Say plainly, before you start, that you are looking at the process and not at the people, and then behave that way when you find something unflattering.
It is also not a redesign. Resist fixing anything while you are still looking. The first two problems you find will be the loudest, not the largest, and rewriting the process around them is how businesses end up with a documented workflow that addresses the wrong constraint.
Finish the observation. Then prioritize by what is costing the most: the longest wait, the most frequent rework, the routing point that appears in every example. Fix one. Measure it for three weeks. Then take the next.
Frequently asked
Questions people actually ask
How long does an operations audit take?
For one workflow and five real examples, a few focused hours plus short conversations with the people involved. The constraint is discipline, not duration.
What if my business has no records to trace?
Then that is the finding. Start a manual log for two weeks: every job, every touch, every date. The absence of a trail is itself the first thing to fix, because you cannot manage what leaves no evidence.
Should I tell my team I am auditing?
Yes, and tell them why. A covert audit produces defensive behavior and teaches everyone that measurement is a threat. Frame it as fixing the process, then prove it by fixing the process rather than reassigning blame.
What if the audit points entirely at me?
That is the most common result and it is the useful one. Every routing point with your name on it is a specific, removable item rather than a vague feeling of overload.
Do I need software to do this?
No. A spreadsheet with a row per touch is enough. Software becomes relevant after you know what the stages are and what has to be true to leave each one.
How often should this be repeated?
Once a year for a full pass, and immediately after any significant change in volume, staffing or service mix. Processes drift toward whatever the busiest person finds convenient.
Make your next move
A year from now, what will you be glad you started today?
You don't need another promise that everything will be easy. You need something useful to learn — and a next step you're willing to take.