Most organisations know something is not working. The harder part is knowing which something, and in what order to fix it. An operations audit is a structured way to find out. It does not have to be expensive or complicated, but it does have to be honest.
Start with the people doing the work, not the people managing it ¶
The most useful information in any audit comes from the people closest to the process. Not because managers are wrong, but because the gap between how a process is described and how it is actually run tends to live at the operational level. Interview individually, not in groups. People say different things when their manager is not in the room. Ask open questions: what slows you down, what do you work around, what would you fix if you could. Take notes. Do not filter yet.
Map what is actually happening, not what should be happening ¶
Resist the urge to map the ideal process. Map the real one. That means following a piece of work from start to finish and noting every handoff, every wait, every decision point, and every place where someone has to chase someone else. You will find workarounds that have become standard practice, steps that duplicate effort, and handoffs that nobody owns. These are the things worth fixing.
Look for the three things worth fixing first ¶
A good audit produces a long list of things that could be improved. A useful audit produces a short list of things worth fixing now. The filter is impact versus effort. What is causing the most friction? What has a fix that is actually achievable in the next quarter? Prioritise those. Leave the rest on a parking list. Trying to fix everything at once is how change initiatives stall.
Write it up in plain language ¶
The audit report does not need to be long. It needs to be clear. One page of findings, one page of recommendations, and a short appendix with the process maps if you made them. The people reading it are busy. Make it easy to act on. If you find yourself writing more than fifteen pages, you are probably including things that belong in a later document.
Decide what you are going to do before you share the findings ¶
Before you present the audit to leadership, know which recommendations you are prepared to act on. An audit that surfaces problems and then produces no action is worse than no audit at all. It tells your team that you looked, you saw, and you did nothing. If the findings are bigger than you can act on right now, say so explicitly and give a timeline.
Running an audit internally is entirely possible. It takes honesty, time, and a willingness to hear things that are uncomfortable. If you want a second set of eyes, or if the politics make an internal audit difficult, that is what we are here for. Have a look at how to reach us.