Eliyahu Goldratt Bottleneck Audit
This workflow session applies the Goldratt constraint identification routine to locate system bottlenecks, maximize capacity, and streamline team throughput.
5 time blocks, 45 minutes in total.
Time blocks
- Map Throughput and Find Constraint: 10 min
Locate the single process step where work piles up longest - Exploit Existing Capacity: 10 min
Remove interruptions and ensure the bottleneck operates continuously - Subordinate Surrounding Workflows: 10 min
Match the pace of upstream and downstream tasks to the bottleneck - Elevate the Bottleneck Capacity: 10 min
Add targeted resources or automation directly to the bottleneck - Guard Against Inertia: 5 min
Check if the bottleneck moved and schedule the next system review
About this routine
Eliyahu Goldratt introduced the Theory of Constraints in his 1984 book The Goal. Using the Goldratt constraint identification routine, teams isolate the single operational bottleneck limiting overall throughput before making any major investments.
The core idea rests on a simple premise: any manageable system has at least one constraint that limits its performance. Trying to speed up non-bottleneck steps generates inventory, clutter, and stress without delivering more finished results. By following five structured focusing steps, you concentrate energy where it yields measurable output.
This 45 minute review guides you through mapping work in progress, maximizing current constraint performance, aligning upstream input, investing in bottleneck expansion, and resetting before inertia takes over.
Why this routine works
- Identifies the true rate limiting factor in your work system
- Prevents wasted effort on non-critical process steps
- Increases finished output without immediate financial spending
- Creates smooth flow across cross-functional team projects
FAQ
What is the Eliyahu Goldratt constraint identification method?
It is a systematic five step process created by Eliyahu Goldratt to identify the single weakest point in a process and improve overall throughput.
How long does a bottleneck review session take?
This structured template takes 45 minutes to evaluate a single workflow or project stream.
Why focus on only one bottleneck at a time?
Goldratt demonstrated that a system has only one primary constraint at any given moment. Improving non-constraints does not increase total output.
Sources
- The Goal: A Process of Ongoing Improvement, Eliyahu M. Goldratt
More routines
Wondering which app to use? Compare the best morning routine apps.
Updated August 2026
Compiled from public sources and reviewed before publishing.