THE MOST UNDERRATED FRAMEWORK IN BUSINESS

A bad system will beat a good person every time

​Most teams I’ve worked with don’t struggle because of a lack of talent, effort, or ideas. The real issues are usually systemic (i.e. hidden constraints disrupt their flow). Teams often make fast progress at first, but momentum fades as bottlenecks emerge, handoffs stall, and priorities collide. Everyone’s busy, but the outcomes can often lag.
That’s where the Theory of Constraints (TOC) comes in.

Developed by physicist-turned-business-thinker Dr. Eliyahu Goldratt, TOC offers one of the simplest yet most powerful insights in operations:

A system’s performance is limited by its most critical constraint

Whether it’s a slow approval process, a resource bottleneck, or an overloaded developer, the idea is the same: find the bottleneck, focus on it relentlessly, and everything else improves.
​
Maybe even more importantly, any efforts to improve other aspects of your process or system will be ineffective until the bottleneck is addressed. ​

What Is the Theory of Constraints?

TOC is a management philosophy that views any organization as a system of interdependent processes. The goal of the system (e.g., profit, customer value, on-time delivery) can only be improved by elevating the weakest link which is known as the constraint.

TOC is perhaps best known from the business novel “The Goal”, which walks through how a manufacturing plant turned its performance around by changing how it viewed work (another great read is "The Phoenix Project" which brings these concepts into an IT context).
​
One thing I've learned as I've had a chance to work across different industries is that TOC applies far beyond factories. It’s just as powerful in software teams, marketing departments, healthcare operations, or startups.

Getting Started with TOC

At the heart of TOC is a practical method for continuous improvement called the Five Focusing Steps:

1. Identify the Constraint: Where’s the real bottleneck? This might be a machine, a person, a policy, or a market condition. It’s the one place where flow is truly limited—everything piles up before it.

Tip: Look for work-in-progress queues, long wait times, or delays in handoffs.

2. Exploit the Constraint: Make sure the constraint is being used to its fullest potential. That means no idle time, fewer interruptions, better prioritization.

Example: If a key designer is overloaded, can you reduce rework or distractions around them?

3. Subordinate Everything Else: Align the rest of the system to support the constraint. This might mean slowing down upstream work or changing priorities to avoid overwhelming the bottleneck.

Lesson: Pushing more work into the system won’t help—it’ll only increase chaos (like a traffic jam).

4. Elevate the Constraint: If the constraint is still limiting performance, find ways to increase its capacity. That might mean adding resources, automating tasks, or changing policies.

Caution: Don’t jump here too soon—exploitation and subordination often unlock far more capacity than expected (and adding more resources can often make the problems worse).

5. Repeat (Go Back to Step 1): Once a constraint is broken, another will emerge. This is a natural part of the process as improvement is a continuous cycle, not a one-time event.

Reminder: Avoid inertia. Continuous improvement means always scanning for the next constraint (this is particularly important when you are working on improving an overall system vs. individual parts of the whole).

Why It Works

The beauty of TOC is its focus. Instead of optimizing everything, it helps you optimize what matters most. It cuts through complexity, aligns teams, and accelerates throughput (often without big investments).
​
It’s not about working harder; it’s about working smarter on the right problem.

Final Thought

If your team is struggling with overload, delays, or conflicting priorities, TOC is a simple, logical, and remarkably effective place to start.
​
Have you tried using TOC or the five focusing steps with your teams? What has your experience been like? ​