HomeFrameworksProblem Solving › Theory of Constraints
// framework

Theory of Constraints

Eliyahu Goldratt, 1984

Every system has one primary bottleneck that limits all throughput — find it, exploit it, then find the next one. Stop optimising everywhere at once, which is the same as optimising nowhere.

// description

A management philosophy based on the insight that any system has one primary bottleneck (constraint) that limits overall throughput. The goal is to identify, exploit, subordinate everything else to, elevate, and then find the next constraint in an ongoing improvement cycle.

// history

Eliyahu Goldratt introduced the Theory of Constraints in his 1984 business novel "The Goal," co-written with Jeff Cox. The story of a struggling factory manager became one of the best-selling business books ever written. Goldratt formalised the five focusing steps and the Thinking Processes (including the Evaporating Cloud and Future Reality Tree) in subsequent works. TOC has been applied in manufacturing, project management, healthcare, education, and software development.

// example

You want to publish more KDP books, but you're spending most of your time on cover design. Your constraint isn't writing — it's design. So: exploit (batch your design sessions, use templates), subordinate (write more during design sessions only when design is unblocked), elevate (hire a designer, buy pre-made templates, use AI design tools). Now output increases. Find the next constraint.

// katharyne's take

This one genuinely changed how I look at my business. I kept trying to optimise everywhere at once — which is basically optimising nowhere. The question isn't "what can I improve?" It's "what's the one thing stopping everything else from flowing?" In a creator business, your constraint is usually time, energy, or a single skill gap. Find it. Fix it. Find the next one. That's the game.

// creative uses
// quick actions
// prompt ideas
Help me identify the primary constraint in my [KDP / Etsy / digital product] business. My production workflow goes: [describe your steps from idea to live product]. I produce about [X] products per month and the most time-consuming step is [name it]. Confirm whether this is really my bottleneck, or whether I might be mistaken about where the constraint actually sits.
Using the Theory of Constraints five focusing steps — identify, exploit, subordinate, elevate, repeat — help me work through my current bottleneck: [describe it]. For each step, give me one specific, practical action I can take this week without hiring anyone or spending more than [£/$ amount].
My [course creation / Etsy shop / KDP publishing] output is stuck at [current pace] and I want to reach [target pace]. Walk me through a constraint analysis: what are the possible bottlenecks, how would I measure which one is actually limiting throughput, and what's the highest-leverage first move to break through it?
See also: Systems Thinking · PDCA Cycle · Fishbone Diagram
← PDCA Cycle Systems Thinking →