# Bottleneck Check v1.3 | Aprixity

> Source: https://aprixity.run/en/bottleneck-check

Worksheet · v1.3 · 9 pages

# 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.

[Download the worksheet](/downloads/engpass-check-v1.3.pdf)[See the method](#method)[Go to the Aprixity Briefing](/en/briefing)

This is the German-language worksheet; the English page explains how to use it.

**Not an AI-tool quiz.**You map a real workflow, mark its queue, estimate the magnitude and only then decide where technology may help.

The path through the worksheet

## From a full calendar to a bottleneck diagnosis.

Four movements turn a diffuse sense of overload into something you can decide on.

1.  01
    
    **Choose the workflow**
    
    Take the workflow that truly determines revenue or delivery — not the loudest isolated irritation.
    
2.  02
    
    **Draw the flow**
    
    Map stations, handoffs and queues as the work actually moves now.
    
3.  03
    
    **Prove the queue**
    
    Mark waiting, rework and the valuable activity that cannot happen because capacity is trapped.
    
4.  04
    
    **Test the cause**
    
    Classify the constraint as process, people, data & knowledge, technology or organisation before buying a solution.
    

[See the method](/en/methodology)

Outcome

## Your score shows what is missing next.

The score is not a maturity badge. It separates four distinct starting positions for the next decision.

1.  0–6
    
    **Fog**
    
    The workflow is not yet drawn sharply enough. That clarity is the first lever.
    
2.  7–12
    
    **Suspicion**
    
    The queue is visible, but the irritation and the limiting station are not cleanly separated.
    
3.  13–17
    
    **Diagnosis**
    
    The bottleneck is credible. The first intervention now has to be right before money and technology follow.
    
4.  18–20
    
    **Lever-ready**
    
    The open question is the boundary: what belongs on the machine, and what remains human?
    

After completion

## 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.

[Deepen the diagnosis online](/en/?entry=worksheet#diagnostic)[Read the manifesto](/en/manifesto)[Deepen the human boundary](/en/wissen/guide/ai-first-nicht-ai-only)[Review with a person](/en/outside-view)

Aprixity Briefing

## A clear continuation — with separate permission.

The recurring Aprixity Briefing connects operating architecture, bottlenecks, AI-First practice, and dependable AI. The Bottleneck Check may appear as optional content; it does not define the publication.

[Go to the Aprixity Briefing](/en/briefing)Source: Bottleneck Check v1.3 · canonical edition