A Practical Guide to Running an Operations Diagnostic

An operations diagnostic answers a deceptively simple question: where is the work actually getting stuck? Done well, it gives leadership a ranked list of fixes and the confidence that you're solving the right problems in the right order. This guide walks through the approach we use.

Step 1 — Map the core process end to end

Pick the process that most directly creates value for your customer and follow it from trigger to completion. Document every hand-off, approval, and wait state. Resist the urge to map the idealized version — map what really happens, including the workarounds.

Step 2 — Quantify the leaks

For each step, estimate two things: how long it takes and how often it has to be redone. Rework and waiting are usually where the biggest losses hide, and they're invisible until you measure them.

• Cycle time — elapsed time from start to finish.
• Touch time — actual hands-on effort (often a small fraction of cycle time).
• Rework rate — how often a step has to be repeated.

Step 3 — Find the constraint

Every process has a bottleneck that governs its overall throughput. Improving anything other than the constraint feels productive but changes nothing. Find it first.

An hour saved at the bottleneck is an hour gained for the whole system. An hour saved anywhere else is a mirage.

Step 4 — Prioritize by effort and impact

Plot each opportunity on a simple effort-versus-impact grid. Start with the high-impact, low-effort fixes to build momentum and fund the harder work with early wins.

Step 5 — Leave behind a system, not a slide

The diagnostic's real value is the operating rhythm it creates: a dashboard your team watches, a cadence for reviewing it, and the habit of asking "where's the constraint now?" every quarter.