Find the point where your operation traps capacity.
The Bottleneck Check takes you from one critical workflow through the visible queue to a defensible first diagnosis. Direct access, no email gate.
This is the German-language worksheet; the English page explains how to use it.From a full calendar to a bottleneck diagnosis.
Four movements turn a diffuse sense of overload into something you can decide on.
- 01Choose the workflow
Take the workflow that truly determines revenue or delivery — not the loudest isolated irritation.
- 02Draw the flow
Map stations, handoffs and queues as the work actually moves now.
- 03Prove the queue
Mark waiting, rework and the valuable activity that cannot happen because capacity is trapped.
- 04Test the cause
Classify the constraint as process, people, data & knowledge, technology or organisation before buying a solution.
Your score shows what is missing next.
The score is not a maturity badge. It separates four distinct starting positions for the next decision.
- 0–6Fog
The workflow is not yet drawn sharply enough. That clarity is the first lever.
- 7–12Suspicion
The queue is visible, but the irritation and the limiting station are not cleanly separated.
- 13–17Diagnosis
The bottleneck is credible. The first intervention now has to be right before money and technology follow.
- 18–20Lever-ready
The open question is the boundary: what belongs on the machine, and what remains human?
Keep the diagnosis. Deepen it only if it holds.
Bring the completed result page into an outside review. You receive the likely bottleneck, likely cause, first lever and a clear boundary for AI — without a tool list or a hidden project pitch.
The worksheet finds the point. The check determines the direction. The outside view tests both from the outside.