Bottleneck

The narrowest place, through which everything must pass: the resource whose capacity sets the throughput of the whole.

A system moves only as fast as its slowest necessary part. Effort spent anywhere else adds stock, not Throughput — work pools in front of the narrow place and hands stand idle beyond it. Every system has one; widen it and another becomes the narrowest, because narrowest is a relation and not a fault. This is why aiming resources at the bottleneck is the highest-leverage move available to any body, and why aiming them anywhere else feels productive and is not (Flow, Waste, Theory Of Constraints).

Five steps, in order. Identify — name the one that sets the rate, not the loudest problem. Exploit — make every unit of its capacity count; nothing reaches it unready, nothing waits there that could be done elsewhere. Subordinate — pace everything else to it; local efficiency upstream is waste. Elevate — only now raise its capacity, with hands, tools, wider authority, or a redesign, since a bottleneck fully exploited is often enough. Return — it will have moved; read it again next week, so that yesterday's answer does not become today's bottleneck.

The pacing has three parts. The bottleneck sets the beat; a small store of ready work stands in front of it so it never starves; work enters the whole system at its pace, so nothing floods and nothing idles (Buffer, Pull planning).

At a table the bottleneck is seldom hands. It is far more often a decision only one person can give — a ruling, a resonance, a word. The exploit is to bring that person decision-ready questions: the options, a recommendation, and what would settle it. The elevate is to widen, on track record, what others may decide alone. A holder who cannot be bypassed has become the bottleneck of the whole, and no amount of willingness fixes it (Decision Making, Delegation, Prescribed and discretionary trust).

At a world's scale the bottleneck is rarely material at all. Money, technology and knowledge are comparatively abundant against what is needed; what the canon names as the primary constraint is the developed capacity of people to hold trust, complexity, and shared intent (The Meta Crisis, Design To The Goal).

Also called: the constraining resource · the drum Stands on: Throughput · Theory Of Constraints · Flow · Critical Path Opens onto: Limiting Factor · Buffer · The Queue · Load · Resource Leveling · Constraint · Waste · Make-Ready Process · Throughput In play: the table — named aloud every week Sources: Projects/the term pages/Bottleneck.md (draft, unreviewed; Theory of Constraints lineage named plainly on the page) · Projects/the term pages/Limiting Factor.md, Buffer.md (drafts) · Theory Of Constraints, Throughput (wiki root) · lionsberg.wiki: Theory Of Constraints Open: A collision the page names and does not resolve: the discipline this reading comes from calls the bottleneck the constraint, while the canon keeps Constraint for what stops one activity being ready. Two disciplines, one word, and the pages are not exchanged. · Queue likewise carries two senses (The Queue).