The goal of a business is to make money — now and over time.

The goal

Profit, growing over time.

A business exists to make money, and to make more of it over time. That's it.

Serving customers well, treating employees right, contributing to the community — those matter. But the discipline that keeps the lights on, pays the people, and lets you keep doing all the other things is profitability that grows.

Most operational improvement work loses sight of this. Efficiency rates, utilization curves, automations-deployed-per-quarter — these can all rise while the business is making less money. They are activity, not progress. We anchor every decision against the goal itself, not its proxies.

Throughput

The rate at which the business turns sales into money.

Throughput is not the same as:

• Gross profit — which subtracts all cost of goods sold, including fixed labor
• Net income — which subtracts everything, including interest and depreciation
• Revenue — which doesn't subtract anything

In cost-accounting language it's closest to contribution margin. The distinguishing emphasis is the word rate — throughput is per-unit-of-time. How much money the system is generating this hour, this week, this year.

Throughput matters because, of the three operating measures — throughput, inventory, and operating expense — it's the only one with unlimited upside. You can always sell more. You cannot reduce inventory below zero. You cannot reduce operating expense below the floor of being open at all. Every other lever has a hard limit. Throughput doesn't.

Flow

The smooth movement of work through your operation.

Flow is the unobstructed movement of work from the moment a customer becomes aware of your business through to the moment the money returns to your account.

A bakery with good flow: orders come in, ingredients are on hand, the team produces in the right sequence, products move to the front of the house, customers buy, the register fills.

A bakery with broken flow: orders pile up at the only decorator trained on wedding cakes. Production sequence is wrong, so cakes wait while croissants bake. Customers see empty cases at ten on Saturday morning. Money is leaking, and nobody can quite say where.

Flow is what produces throughput. Where flow is interrupted, money is interrupted too.

Why this isn't "be more efficient"

Efficiency at the wrong stage is a mirage.

Most operational improvement work focuses on efficiency — how fast each stage runs, how busy each resource stays, how little waste each step produces. Efficiency is fine when applied to the right stage. Applied to the wrong stage, efficiency hurts throughput.

Imagine a bakery whose binding constraint is the decorator's hours. The oven runs at 70% utilization. A consultant who "improves the oven's efficiency" to 90% has done nothing for throughput — the decorator's hours haven't moved, so the system's output hasn't moved. Worse, the bakery has now invested in oven improvements that produce no return.

An hour saved at a non-constraint is a mirage. An hour gained at the constraint is real money.

This is what most general improvement work gets wrong. It treats every stage as equally worth optimizing. Theory of Constraints treats them differently: the binding constraint determines throughput; everything else should be in service of the constraint, not optimized in isolation.