Theory of Constraints, introduced by Eliyahu Goldratt in The Goal (1984), says every system has exactly one bottleneck that limits its total throughput. Improving anything other than that bottleneck is an illusion of progress. A faster engineering team does not matter if the work piles up waiting on sales. The chain only moves as fast as its weakest link, so effort spent anywhere else is wasted motion that feels productive but changes nothing.
It works because output is governed by a single constraint at a time, not by the sum of all your activity. Speeding up a non-bottleneck just builds inventory in front of the real one. Founders use this when progress feels slow despite effort everywhere: trace the flow from idea to revenue, find the stage where work backs up, and pour your attention there exclusively until it stops being the limit.
The classic founder case: your product team ships fast but sales closes nothing. The constraint is distribution, not development. Stop building features and fix the funnel. Then re-find the new bottleneck and repeat.
Common mistake
The most common mistake is improving whatever you are best at or most comfortable with instead of the actual bottleneck, which feels like progress but leaves total throughput unchanged because the real constraint still caps everything downstream.
How to use it
Three ways to put it to work.
Everyday life
Mornings run late no matter how early you wake
Map the morning as a pipeline: shower, breakfast, dressing the kids, packing bags, the drive. Time each step and the bottleneck is the kids picking outfits, eating 25 minutes while everything waits. Waking 15 minutes earlier just adds idle time before that one jam. Lay out their clothes the night before so that step drops to two minutes.
Tech
Feature velocity is high but releases still crawl
Trace a ticket from commit to production: coding and review are fast, but every release sits two days in a manual QA queue run by one person. That stage caps throughput, so hiring more developers only piles work in front of it. Focus on the constraint: add automated regression tests and a second reviewer, and make that this sprint's only priority.
Small business
Cafe has a full room but the line stalls
Watch where orders pile up: tables are full and people order fast, but every drink waits on one espresso machine with one barista. A second cashier does nothing because everything backs up at that machine. Focus on the constraint: buy a second machine this month and cross-train a floor staffer to pull shots during the 8 to 9am peak.
Reckon · Thinking tool
Theory of Constraints
Eliyahu Goldratt, The Goal (1984)
What it is
Every system has one bottleneck that limits total throughput. Improving anything other than that bottleneck is an illusion of progress.
When to use it
When progress feels slow despite effort everywhere. Identify the single constraint preventing shipping and focus exclusively on that.
Work through it.
Print this (use the Save as PDF button up top) and fill it in on paper. Identify the single bottleneck choking your entire system and fix that before touching anything else.
01
THE SYSTEM: Describe the workflow or pipeline where progress feels slow despite effort everywhere.
02
THE BOTTLENECK: Walk the flow step by step. Where does work pile up, wait, or get handed off incomplete? Name that one step.
The constraint is where output of everything upstream sits unprocessed.
03
THE EXPLOIT: Without adding resources, how can you get more throughput out of the bottleneck as it exists today? List two actions.
04
THE SUBORDINATION: What are you currently improving that is not the bottleneck? Write it down, then commit to stopping that work until the constraint is solved.
05
THE NEXT CONSTRAINT: Once you fix this bottleneck, the constraint shifts. Name where you predict the next one will appear so you see it before it surprises you.
Reckon · reckon.report · flip for the working template
Reckon · Working template
Theory of Constraints
Print double-sided. Read the how-to on the front; do the work here.
Write your workflow stages. Circle the one where work piles up.
1
2
3
4
5
The bottleneck: how to get more out of it
Where the next bottleneck appearsonce you relieve this one