← Writing
·7 min read

Beyond the Fluff: Running a Product Organization by Goldratt’s 'The Goal'

A pragmatic look at Eliyahu M. Goldratt’s 'The Goal' — stripped of corporate fluff and translated directly for SaaS and digital product leadership.

Theory of Constraintsflowvaluewriting

In business, there is just one goal: to make money.

Delivering value to customers is a vital means to achieve that goal, but it is not the goal itself. If a company delivers immense value but fails to monetize it, the business goes bankrupt.

To make this concept operational, Eliyahu M. Goldratt introduced the Theory of Constraints (TOC), which breaks down all operational decisions into three simple, interconnected measurements, prioritized in this specific order of importance:

  1. Throughput (T) — The Top Priority The rate at which the system generates money through sales. In a product company, this is revenue generated from acquiring new customers, expanding accounts, and retaining existing subscriptions (MRR/ARR). Crucially, it is measured not by what we build or ship, but by what we actually sell.

  2. Inventory (I) Money tied up in things the system intends to turn into Throughput. In a digital product environment, physical raw materials are replaced by Work in Progress (WIP). This includes unlaunched new features, unmerged code, staging environments, and unvalidated product designs. It represents cash spent that is not yet generating revenue.

  3. Operating Expense (OE) Money the system spends continuously in order to turn Inventory into Throughput. This includes engineering and product payroll, cloud infrastructure hosting, third-party software licenses, and marketing acquisition costs.

Ultimately, the goal is translated into a highly focused operational strategy: maximizing Throughput as the primary driver of infinite growth, while accelerating feedback loops to minimize Inventory (WIP), and eliminating operational waste to control and reduce Operating Expense.

Why This Framing Changes Product Delivery Behavior

  • Writing code is an expense, not an asset: Until code is live in production and a customer pays for it, it sits in Inventory.
  • The Danger of Micro-Inventory: Inventory isn't just giant features waiting for a quarterly release. It is the sum of all the tiny bits stuck in columns on a Kanban board (Ready for Review, In Testing, Blocked). These columns act exactly like piles of half-assembled parts on a factory floor, silently bloating lead time and cycle time.
  • Feature utilization beats feature output: Building a feature that cannot be sold or that customers do not use increases Inventory and Operating Expense without moving Throughput.
  • Focus over busyness: It prevents the trap of keeping developers 100% busy writing random code just to justify their salary, which only serves to bloat Kanban boards and clog up the deployment pipeline.

The Asymmetry of Growth

It is vital to understand the mathematical asymmetry between our three core metrics. Operating Expense ($OE$) and Inventory ($I$) both have a hard floor: you can only ever reduce them to zero. Throughput ($T$), however, has an infinite upside.

While traditional management focuses heavily on the defensive strategy of cutting expenses, true Theory of Constraints leadership focuses on the offensive strategy of unlocking the bottleneck to drive continuous, unlimited revenue growth.

A company that cannot find a lever to increase Throughput and instead relies solely on minimizing Inventory and cutting Operating Expenses is caught in a corporate death spiral. Because $OE$ and $I$ yield diminishing returns remarkably fast, a leadership team that pivots exclusively to cost-cutting is no longer managing a constraint to grow—they are simply managing the rate of their own decline. You cannot starve an organization into high performance.

Why "Growth Statements" Are Not a Strategy

In the corporate world, you will frequently encounter statements disguised as strategy that sound like this: "We want to earn more money by acquiring more customers with our core products, and increasing the average order value with our existing customers through cross-selling and upselling."

This is not a strategy. It is an operational wish list. It fails for two fundamental reasons:

  1. It Relies on Truisms: Saying a business wants to make money by selling core products to new and existing customers is the corporate equivalent of a football coach saying, "Our strategy is to score more points than the opponent by running and passing the ball." It is completely obvious. It represents the baseline expectation of running a business, not a competitive advantage or a strategic choice.
  2. It Mistargets the Bottleneck: A real strategy requires a kernel: a clear diagnosis of a challenge, a guiding policy to deal with it, and a set of coherent, focused actions. Generic growth statements focus entirely on goals rather than identifying how the organization will unblock the specific operational constraint currently preventing those goals from happening. If you aren't acquiring customers because your self-service onboarding flow is broken, "wanting to acquire more customers" fixes nothing.

What a Genuine Strategy Looks Like in TOC

To turn a wish list into an actual strategy, leadership must make a specific, falsifiable bet on where their constraint lies and take a calculated risk on the future—deciding what not to do in order to concentrate resources where they matter most:

"Our diagnosis is that our core product’s time-to-value is too long, which is our primary bottleneck to acquiring new customers ($T$) and is bloating our onboarding support costs ($OE$).

Our strategic bet is to halt all secondary feature development for the next two quarters (minimizing $I$) and dedicate 100% of our engineering capacity to rebuilding our self-service setup. We are choosing to let competitor feature-parity slip in the short term because we believe a frictionless onboarding experience is the single lever that will unlock massive market volume."

The Illusion of Inorganic Growth (The Masked Bubble)

When a company can no longer leverage organic growth, it often turns to inorganic growth—using investor capital to acquire other SaaS companies. This financial engineering masks a decaying core with external money, creating a temporary "Throughput Mirage" on the balance sheet by stacking revenues together.

In reality, this is often a "Greater Fool" bubble. Under the hood, you aren't just merging revenues; you are merging completely distinct, unintegrated codebases, product backlogs, and organizational cultures. In TOC terms, your Inventory (WIP) multiplies exponentially due to technical debt, while the promised "infrastructure efficiencies" rarely materialize. Instead of reducing $OE$, maintaining two legacy architectures requires more engineering overhead, leaving the next buyer with a ticking time bomb.

The Qualifying Argument: The Strategic Bridge

Is there an ethical, sustainable path out of this bubble? Can investor capital and inorganic acquisition be used as a temporary defensive shield to buy the time and market share necessary to return to organic growth?

Theoretically, yes. But it requires an extraordinary level of leadership discipline to execute a hyper-specific Theory of Constraints playbook:

  1. Ruthlessly Treat Integration as the Ultimate Bottleneck: If you buy another SaaS company to achieve market dominance, you cannot leave the product as a standalone silo forever. The bottleneck to organic growth is now Product Integration. Leadership must resist the temptation to build new features and instead dedicate capital to unifying the infrastructure, sunsetting redundant systems, and paying down the technical debt. This is the only way to actually reduce $OE$ and shrink the combined $I$ (WIP).
  2. Fund the "Strategic Bet" with the Acquired Cash Flow: The inorganic revenue must not be used to buy more companies. It must be used to fund a genuine, high-risk strategic bet on the core product. You use the market-share insulation to figure out what your customers actually love, dramatically shorten your feedback loops, and build an organic engine where the core product begins selling itself again.
  3. Transition from Financial Metrics to Operational Metrics: Investors look at EBITDA and ARR growth. To survive the bridge, internal leadership must look at Cycle Time, Lead Time, and Feature Utilization. You must transition the culture from "how much revenue did we buy this quarter?" to "how fast can we turn a customer insight into a live, revenue-generating feature?"

The Verdict

Using financial engineering and inorganic acquisition to prop up a company represents an incredibly narrow, dangerous tightrope.

If leadership uses investor capital to buy market share while simultaneously possessing the courage to halt the feature factory, consolidate the architecture, and find a real strategic bet, it can save a company. It uses capital as medicine.

But if the leadership team lacks a real strategy and uses acquisitions simply because they don't know how to build a product people want to buy organically, then it isn't medicine—it's an addiction. And eventually, the investor cash runs out.