Theory of Constraints

A decades-old principle still in use

The Theory of Constraints comes from Eliyahu Goldratt's 1984 business novel The Goal: every team operates with some bottleneck in its process, and the system's throughput is governed by that single constraint, so the highest-leverage management act is to identify the bottleneck and remove it.¹ George Bonaci, VP of Growth at Ramp, cites the book as a recent re-read and uses it to make a broader point: business tactics such as channels and tools change, but fundamentals do not. He argues the concept existed 40 years ago and still exists today, offering it as proof that a decades-old business book still yields a transferable principle if it is vetted for the right idea, a counter to the view that leadership books are outdated.²

The single prioritizing question

Bonaci presents the value of the framework as reducing a manager's job to one question rather than optimizing everything at once: what is the one thing limiting throughput right now. On his account, removing a non-bottleneck step does not increase output, because only the constraint governs the system. He describes identifying and removing the binding constraint as one of the core jobs of being a manager and as how a leader gets the most out of a team.²

The named constraint at Ramp

Asked for the biggest bottleneck in his own role, Bonaci names the velocity of experimentation. He argues there are many opportunities and not enough time or resources, and that, zoomed out far enough, experiment velocity is probably the constraint for most businesses.² The concrete drags he identifies are external dependencies: vendors, lead sources, and legal teams reviewing terms of service all move slowly. He praises Ramp's instinct to optimize for speed in response, accepting reasonable terms, launching, testing, and working out details later only if something proves worth scaling. This makes the framework the diagnostic underneath velocity-as-design-principle: if experiment velocity is the constraint, the management job is clearing what throttles it. The instinct he praises is the one Eric Glyman describes designing Ramp around, and Bonaci applies the framework to operations by reducing management to a single limiting variable.

Why the founders treat it as load-bearing

For a growth organization, naming experiment velocity as the constraint reframes the leader's leverage as removing blockers such as legal turnaround, vendor latency, and headcount rather than running more tactics. Bonaci presents this as the operations-theory sibling of the delete-and-simplify-before-optimize heuristics that circulate in engineering culture: clearing the limiter comes before improving anything else.

Open questions the framing leaves

By the framework's own logic, constraints move. Remove one bottleneck and another becomes binding, so it is a continuous diagnostic rather than a one-time fix, and Bonaci names experiment velocity only as today's constraint. His preferred response, accepting legal terms quickly to move fast, also trades a velocity gain for risk exposure. That is defensible for small tests, but the deferral to figure out details if something scales assumes the team actually circles back, the same debt risk that attaches to moving fast without rigor.