Why operations audits often fail
Many operational reviews produce the same result: dozens of observations, a long process map and a recommendation to “improve efficiency.” The problem is not a lack of observations. It is a lack of prioritization.
A 90-day audit works differently. It is designed to move from diagnosis to action quickly, while creating enough evidence to distinguish symptoms from root causes.
Days 1–15: Understand the operating system
The first phase is about establishing a fact base. Review performance data, customer commitments, process documentation, organization structures, policies and recent operational incidents.
Then go to the work. Observe how orders move, how approvals happen, how exceptions are handled, where information waits and where employees create workarounds.
Typical baseline measures include cycle time, on-time delivery, backlog, first-pass yield, rework, inventory turns, utilization, productivity and service-level performance.
Days 16–30: Find the bottlenecks
Not every problem deserves equal attention. The audit should identify the constraints that create disproportionate downstream impact.
A useful question is: where does work accumulate, wait or return? That often reveals the real constraint more clearly than a high-level process diagram.
Trace a sample of transactions end-to-end. Compare planned versus actual lead times. Identify handoffs, approvals, data gaps and recurring exceptions.
Days 31–45: Quantify the opportunity
Convert operational friction into a business case. For example, excessive rework consumes capacity; delayed approvals extend cycle time; poor scheduling creates overtime; stockouts create lost sales; and excess inventory ties up working capital.
The exact calculation will vary by business, but the principle is consistent: prioritize problems according to impact, not noise.
Days 46–60: Design targeted interventions
Interventions should be specific enough to implement. Examples include simplifying an approval chain, changing a scheduling rule, redesigning a handoff, clarifying decision rights, standardizing a high-variation process or creating a performance dashboard.
Avoid launching a transformation program when a focused process change can solve the constraint.
Days 61–75: Pilot and measure
Test the highest-priority changes in a controlled area. Define the baseline, target and measurement method before the pilot starts.
Good pilots answer three questions: Did performance improve? Why did it improve? Can the change be sustained when volume, people or conditions change?
Days 76–90: Institutionalize the gains
The final phase converts successful pilots into a management system. Update standard operating procedures, assign owners, define KPIs, establish review routines and document escalation rules.
Leadership should leave the 90 days with a clear view of the operational constraints, quantified opportunity, actions completed and next-wave priorities.
The output should fit on one page
A strong executive summary can show five things: the top constraints, their estimated impact, actions already taken, owners and the next 90-day priorities.
Final thought
Operational improvement is not primarily about finding more problems. It is about finding the few problems that control performance and then building the discipline to remove them.