tech
Bottleneck
The single constraint that limits how much output the whole system can produce.
Definition
A bottleneck is the slowest step in a process - the constraint that limits total throughput. Adding capacity anywhere except the bottleneck doesn't help; only relieving the bottleneck speeds up the whole system. In service businesses, the bottleneck is usually the founder (selling, delivering, deciding) early on, then shifts to specific delivery roles, then to systems. Theory of Constraints: identify the bottleneck, exploit it (maximize its output), subordinate everything else to it, elevate it (add capacity), repeat.
Theory of Constraints applied to US small businesses
Eli Goldratt's Theory of Constraints (from 'The Goal') has five steps that work in any US service or product business. Step one, identify the constraint (the slowest step in the process; can be a person, a tool, a process step, or a market condition). Step two, exploit the constraint (maximize output from the bottleneck without major investment; remove non-bottleneck work from it, schedule it carefully, eliminate interruptions). Step three, subordinate everything else (other steps work in service of keeping the bottleneck fed and protected, even at the cost of their own efficiency). Step four, elevate the constraint (add capacity or change capability where bottleneck sits). Step five, when constraint is relieved, return to step one because a new bottleneck has now emerged. The discipline of constantly identifying the current bottleneck and concentrating effort on it produces 2 to 5x output improvements in most US small businesses.
Where bottlenecks typically sit in US small businesses
Predictable patterns by business stage. Early stage (founder plus 1 to 3 people): bottleneck is almost always the founder. Founder is selling, delivering, deciding, recruiting, accounting. Removing founder bottleneck requires deliberate delegation, hiring, and systematization. Growth stage (5 to 25 people): bottleneck shifts to specific delivery roles (senior implementer, lead designer, senior consultant). Removing requires hiring, training, and process documentation. Scale stage (25 to 100 people): bottleneck shifts to systems and processes. Removing requires investments in technology, workflow design, and organizational structure. Mature stage (100+ people): bottleneck shifts to strategic capacity (leadership, market access, capital). Each stage requires different intervention; founders sometimes try to fix the wrong bottleneck (e.g., investing in marketing when delivery is the bottleneck creates worse problems).
How to identify the actual bottleneck
Three diagnostic methods. One, observe where work piles up. Look at the workflow: where do tasks queue, where do clients wait, where does decision-making stall. The pile reveals the bottleneck. Two, ask the team. Front-line people know where the bottleneck is; they live it daily. A 30-minute conversation with each team member reveals the constraint with surprising clarity. Three, follow the cash. Where does money slow down (sales close, invoice send, payment collect)? Where the cash slows is often where the bottleneck sits. Most US small business founders intuitively know the bottleneck but resist naming it because the fix is uncomfortable (the founder is the bottleneck, the favorite team member is the bottleneck, the legacy tool is the bottleneck). Naming it is the first hard step.
Non-bottleneck waste
Counter-intuitive Theory of Constraints insight. Investing in non-bottleneck capacity creates waste, not improvement. Example: a US service business with a sales bottleneck (cannot close enough deals) hires more delivery capacity to prepare for future growth. Result: existing delivery team has idle time, costs rise, sales bottleneck remains, business loses money. The correct move would have been to invest in sales capacity. Common US small business mistakes. Hiring delivery when sales is bottleneck. Buying more software when process is bottleneck. Increasing marketing when conversion is bottleneck. Adding team when management capacity is bottleneck. Each mistake feels productive but creates idle resources elsewhere. The discipline of investing only at the bottleneck saves significant resources while accelerating throughput.
FAQ
How do I know where the bottleneck is in my business?
Look for queue or wait time. Where do tasks pile up, where do customers wait, where does work stop? That is the bottleneck. Specific diagnostic questions. Where do we lose deals? (sales bottleneck). Where do projects fall behind? (delivery bottleneck). Where do customers complain about response time? (operations bottleneck). Where do bills pile up? (finance bottleneck). Where do hiring delays slow growth? (recruitment bottleneck). Where do decisions stall? (leadership bottleneck). The signal is queue; the bottleneck is wherever the queue grows.
Can I have multiple bottlenecks at the same time?
Technically only one true bottleneck exists at any moment (the slowest step). However, in practice US small businesses often have one primary bottleneck plus several near-bottlenecks that become primary as soon as the current one is relieved. The correct approach: focus all elevation work on the current primary bottleneck. Secondary bottlenecks reveal themselves naturally as the primary is fixed. Trying to fix multiple bottlenecks simultaneously fragments effort and produces incomplete improvements on all of them.
What if the founder is the bottleneck and cannot be replaced?
Common situation in US small businesses. Founder is the primary salesperson, the primary deliverer of expertise, the primary decision-maker. Three paths forward. One, accept the cap and design the business around it (lifestyle business model that does not require founder removal). Two, hire a counterpart and document founder knowledge over 18 to 36 months (slow but creates option value). Three, refactor the business model to require less founder time (productize, automate, hire managers). The choice depends on founder's life goals; not every business needs to scale past founder, but consciously choosing whether to scale matters.
Should I invest in non-bottleneck areas to prepare for future growth?
Generally no, with one exception. Theory of Constraints says investment in non-bottleneck capacity creates waste because the bottleneck still caps overall throughput. The exception: long lead-time investments that must start now to be ready when the current bottleneck is relieved. Example: hiring senior team members takes 3 to 6 months; starting now is appropriate if you expect to need them in 6 to 12 months and the current bottleneck will be resolved by then. Most US small businesses err on the side of investing too broadly; the discipline of concentrating on the bottleneck typically saves 20 to 40 percent of operating expense.
What is the difference between bottleneck and constraint?
Often used interchangeably in US small business operations conversations. Strictly: a bottleneck is an operational slowdown (a specific step where work piles up). A constraint is a broader limit on what the system can produce (could be operational, market-based, capital-based, or strategic). Most operational bottlenecks are constraints; not all constraints are bottlenecks. Theory of Constraints uses both terms; common usage treats them as synonyms. The actionable insight is the same: identify the limiting factor, work on that.
In your business
- →Identify the current bottleneck explicitly - it's usually obvious once you look
- →Don't invest in non-bottleneck capacity - it just creates inventory
- →When you relieve one bottleneck, the next one becomes visible - the cycle continues