Skip to toolkit
REQUEST AN ASSESSMENT
All operations tools / Workflow diagnostic

Workflow Bottleneck Diagnostic Tool

Where does your work keep waiting? Let's follow one workflow, compare the time spent working with the time spent waiting, and decide what you should investigate first.

Use the workflow diagnosticRead the companion guide

A ranked delay table, waiting share and next investigation.

Enter your own evidence, or try the clearly labeled fictional example. Generate a report, print it or save an editable copy to reopen later.

Your inputs stay in this page; they aren't sent to us or saved automatically. Before you leave, save an editable copy if you want to return to your work, and choose where to keep that download.

Prepared by the Regal Nexus Group editorial team. Version 1.0 · 21 October 2026.

Find the delay worth investigating

Let's follow where your work waits. Use timings from the same cases so you can compare stages and choose what to investigate.

You will create: A ranked delay table, waiting share and next investigation. Read the companion guide.

Define the review

For example, customer onboarding.

Required.

For example, the previous four weeks.

Use the same period for all observations.

Record sample size, timestamps used and any missing evidence.

Workflow stages

Use at least two sequential stages. Do not add parallel or overlapping times.

Stage 1

Required.

Convert minutes to hours: minutes ÷ 60.

Exclude active work and overlapping waits.

A snapshot count, measured consistently.

Separate what you observed from what you suspect.

Stage 2

Required.

Convert minutes to hours: minutes ÷ 60.

Exclude active work and overlapping waits.

A snapshot count, measured consistently.

Separate what you observed from what you suspect.

How this tool works

  1. Choose one workflow and agree where it starts and ends. Use the same representative cases to record active and waiting hours at each stage.
  2. You'll see the sequential cycle time, the share spent waiting and the stages ranked by mean wait. Keep your backlog count separate: it is a snapshot of cases waiting, not another time measurement.
  3. Start with the longest wait, then ask what's causing it. Check capacity, dependencies and missing inputs before deciding you've found the constraint limiting throughput.

A worked example

Try the fictional client-onboarding example. You'll see contract approval waiting 18 hours per case within a 25.25-hour sequential cycle. That gives you somewhere to investigate; you still need to check approval timing and capacity before choosing a fix.

Questions before you use it

Does the longest wait tell me where the bottleneck is?

It tells you where to investigate first. Batching, missing inputs or dependencies can all create a long wait. Check what limits the complete workflow before you commit to a change.

Can I include work happening in parallel?

Review one sequential path at a time. If two activities overlap, don't add their timings as though one follows the other. Write down your measurement boundary so you can interpret the result correctly.

Download the companion checklist (PDF) · Read the full guide

Discuss this workflow delay

Bring your brief to a free 30-minute assessment. We'll look at where your work waits, what you still need to verify and whether a focused operational diagnostic would help.

Discuss this workflow delay

Your inputs and report are not sent automatically when you open the booking page.

Explore our services · How we work