Index

Strategic Frameworks

Theory of Constraints

A management philosophy that identifies the most limiting constraint in a system and restructures operations around improving that constraint before optimizing anything else.

Theory of Constraints focuses improvement effort on the single bottleneck that currently limits overall system throughput.

Core question

What is the one constraint that, if relieved, would increase the throughput of the entire system?

Example

An engineering team speeds up CI builds and code reviews but deploys remain slow. They discover the bottleneck is manual QA sign-off. Automating that single gate doubles release frequency.

How to apply

  1. 1.Identify the current constraint — the step where work queues up most.
  2. 2.Exploit the constraint by ensuring it is never idle or blocked by non-essential work.
  3. 3.Subordinate other processes to the constraint's pace instead of local optimizing.
  4. 4.Elevate the constraint with investment, then find the next one and repeat.

Pitfalls

  • ·Optimizing non-bottleneck steps, which adds cost without increasing throughput.
  • ·Failing to re-identify the constraint after the original one is resolved.
  • ·Confusing symptoms like slow output with root-cause constraints deeper in the system.

Questions

How do you find the constraint in a knowledge-work environment?

Look for where work-in-progress accumulates. The step with the longest queue or highest wait time is usually the active constraint.

Is Theory of Constraints only for manufacturing?

No. It applies to software delivery, sales pipelines, hiring funnels, and any system where throughput matters.

Related