Where work actually slows down.
And whether that is the constraint.

What the Throughput lens looks at

Throughput is the rate at which finished work — closed deals, shipped tickets, billable hours invoiced, patients seen — exits the business. A throughput problem feels like a capacity problem. It almost never is.

Every operating system has exactly one true constraint at a time. The Throughput lens names the suspected one. The other four lenses confirm or break the suspicion.

Signals that trigger this lens

• Output volume has plateaued despite adding people, tools, or hours.
• Work-in-progress is piling up at one specific stage — and the stage owner sounds tired, not lazy.
• You have more demand than you can serve, and adding revenue creates more pain, not less.
• "We're busy" is the most-said phrase in the weekly stand-up.
• Hiring is the default proposed answer for almost every operational problem.

Sample constraint statements this lens surfaces

• "Senior capacity is being burned on work two levels below their pay grade — the bottleneck is delegation discipline, not headcount."
• "Marketing produces more qualified leads than sales can sequence. Lead-volume is not the constraint; sales-process throughput is."
• "Onboarding ships 3 customers a week. Sales books 8. The bottleneck is the implementation handoff, not the funnel."

Why operators miss this

Throughput problems hide because every individual function looks busy. The constraint is not a person or a team — it's the rate-limiting step in the chain between them. Most owner-operators have never been taught to look at the seams.

How Throughput interacts with the other four lenses

Throughput is the suspect. Friction, Decision, Information, and Inference are the witnesses. A real constraint shows up in at least three of the five lenses. If only Throughput sees it, you have a symptom, not a constraint.