Sample frameDay 042·Operations · Flow

Good morning. One point in your business sets the pace of everything else. Today you find it.

Operations.

Theory of Constraints

5 min read·Apply by lunch

The question

Where does work visibly queue in your business — the unanswered quotes, the approval that waits on one person, the step everything routes through — and if you can name that point without looking anything up, why haven't you pointed this week's effort straight at it?

The idea

Eliyahu Goldratt was an Israeli physicist who took an unusual route into management: he wrote a novel. The Goal (1984) follows a plant manager with ninety days to save his factory, and it built a whole discipline — the Theory of Constraints — around one claim: every system has one constraint, and that constraint alone sets its throughput. A chain does not get stronger when you thicken its strongest links. Improve any step that isn't the bottleneck and you have bought local efficiency: machines run, people look busy, work-in-progress piles up in front of the same choke point, and nothing more comes out the other end. Most people improve whatever is easiest, most visible, or most theirs — which is almost never the constraint, because the constraint is usually another department, an awkward conversation, or the founder's own diary. Throughput moves only when the bottleneck does.

The framework

01
Find the constraint — follow the queues, not the noise.
The constraint announces itself as waiting: walk your process from enquiry to delivered work and note where things pile up — the quotes that sit unanswered, the review only one person can do, the approval that takes a week for an hour's work. In a small company the constraint is very often the founder's own diary, which is precisely why it goes unnamed. Resist the urge to list five bottlenecks; a system has one at a time, and the discipline is in choosing it.
02
Exploit it before you spend a single dollar on it.
Exploiting means extracting full capacity from the constraint exactly as it stands: strip away every task it does that a non-constraint could do, make sure only qualified work reaches it, and never let it sit idle waiting for inputs. Goldratt's point was blunt — an hour lost at the bottleneck is an hour lost to the entire system, while an hour saved anywhere else is a mirage. Most 'we need to hire' conversations dissolve under this step, because the constraint was never actually full; it was doing someone else's admin.
03
Subordinate everything else — let efficient people slow down.
This is the step organisations refuse, because it means pacing every other part of the system to the constraint's rhythm and telling capable people to produce less. Upstream output beyond what the bottleneck can absorb is not progress; it is inventory — half-done work that ties up cash and attention while flattering everyone's utilisation numbers. Measure the system by what comes out the end, not by how busy each station looks.
04
Elevate — then go and find the new constraint.
Only when the constraint is fully exploited and everything else subordinated do you spend money on it: hire the second reviewer, buy the machine, build the automation. The moment you do, the constraint moves somewhere else in the system, and the steps begin again from the top — Goldratt's fifth step is a warning against inertia, against running rules written for a bottleneck that no longer exists. Treat it as a cycle you re-run each quarter, not a project you complete.

Members only · 4 principles + template + AI mentor

364 more frameworks are waiting.

Theory of Constraints is Day 1 of 365. One framework every morning for a year — across strategy, sales, negotiation, leadership, and more.

$1 /day

Billed $365/yr · cancel any time

365 frameworks

12 topics · templates · AI mentor

Reserve your place — $365/yr →

One payment a year · the whole library · no auto-renewal.

More Operations frameworks

All 24 operations frameworks →