Throughput

Throughput is the rate of acceptable output from a defined system. A capacity constraint can limit that rate, but actual flow also depends on demand, variation, rework, and the availability of inputs. Changes elsewhere can help when they reduce losses or interruptions affecting the constraint.

Throughput counts completed acceptable outputs per unit of time. Define the boundary before optimizing: applications submitted, applications approved, and people successfully served are different outputs. In a simple serial process with ample demand and no losses, its slowest required stage limits the achievable rate. Real processes also have interruptions, rework, variable arrivals, and missing inputs, so the longest visible queue is a clue to investigate rather than a complete diagnosis.

A practical improvement connects a proposed change to finished output. Speeding an already idle station may add nothing; preventing defects before a constrained station may free scarce capacity. Measure the whole process after the change and check quality, waiting time, and workload. A higher output rate can be useful without establishing that the outputs themselves are valuable.

When to use it

When building or iterating on products; when evaluating market opportunities; when deciding resource allocation; when scaling operations.

How it can help

Directly applicable to building, launching, and scaling products and businesses. Helps prioritize actions, identify market opportunities, and build sustainable competitive advantages.