Systemize vs Hire vs Tolerate the Bottleneck Decision Matrix
Why this matters
Every growing shop hits choke points: the one person who does all the quotes, the dispatch that only the owner can run, the invoicing that piles up because nobody else knows the system. You have three honest responses to a bottleneck, and only three: build a system so it takes less effort, add a person to do it, or decide to live with it for now. Owners get into trouble by reaching for "hire" when the real answer is "systemize," or by tolerating a bottleneck so long it strangles growth. Picking the wrong response wastes the scarcest things you have: payroll and your own time.
This is a field-card for choosing the right one.
First, confirm it is the bottleneck
A bottleneck is the single step that limits how much work the whole shop can push through. It is not just the busiest person; it is the one whose backlog forces everyone else to wait. Signs you have found the real one:
- Work piles up in front of this step and starves the steps after it.
- Speeding up anything else does not increase total output.
- When this person is out, the shop visibly stalls.
Fix the wrong step and nothing improves, because the true bottleneck still caps the flow. Find the real constraint before you spend a dime or an hour on it.
The three responses
Systemize means changing the work so the step takes less skill, time, or attention: a checklist, a template, a form that captures it right the first time, a software step that automates it. You keep the same headcount and get more out of it.
Hire means adding capacity: a person (or fractional help) to carry the load the system cannot remove. You add cost in exchange for throughput.
Tolerate means consciously deciding the bottleneck is acceptable right now, watching it, and revisiting later. This is a legitimate choice when the fix costs more than the pain - but only if it is a decision, not avoidance.
The decision matrix
| Question | Systemize | Hire | Tolerate |
|---|---|---|---|
| Is the work repetitive and rule-based? | Yes - first choice | If it is judgment-heavy | If volume is still low |
| Does it need scarce skill or relationships? | Hard to systemize | Yes - the right tool | Maybe, short term |
| Is the step buried but the person capable? | Yes - free up their time | No, that adds cost | No |
| Is volume high and still climbing? | Do this first, then hire | Yes, once systemized | Risky - it will get worse |
| Is the fix expensive and the pain small? | Maybe | No | Yes - revisit later |
| Will this break a customer promise if ignored? | Yes, urgently | Yes, urgently | No - it is failing |
Sequence: almost always systemize before you hire
The default order is systemize first, hire second, because hiring into an unsystemized mess just buys you a second person doing chaos at twice the cost. A bad process with two people is worse than a bad process with one - more handoffs to drop, more to retrain.
Work the step down with a system as far as it will go. Then, if volume still exceeds what one systemized person can carry, you hire - and you hire into a defined, documented role instead of "help me with the stuff I can't get to." The new person ramps in days instead of months because the job is written down.
The exception: when the bottleneck is genuinely skill or relationship work that no checklist replaces (closing big quotes, leading a crew, handling escalated customers), hire sooner. You cannot template trust or judgment.
When tolerate is the right call
Tolerating gets a bad name, but it is correct when:
- Volume is low enough that the pain is occasional, not daily.
- The fix (system or hire) costs clearly more than the bottleneck costs you.
- You are deliberately steering resources at a bigger constraint first.
The rule that keeps "tolerate" honest: write down the trigger that ends it. "We revisit dispatch when we pass a steady run of jobs that one dispatcher cannot clear by end of day." Without a trigger, "tolerate" silently becomes "ignore until it breaks a customer promise," and then you are firefighting from the back foot.
Re-check after every fix
Constraints move. The moment you relieve one bottleneck, a new one appears at the next-slowest step - that is normal, not failure. After any systemize or hire, walk the flow again and find where work piles up now. Chasing the moving constraint, one at a time, is how a shop scales without bloating payroll.
References
- See related: When to Add an Office Role vs Stay Lean Decision Tree
- See related: The Recurring Firefight - Root Cause vs Bandaid Decision Tree
- Theory of Constraints, standard operations-management framework for bottlenecks
- U.S. Small Business Administration guidance on staffing and operational scaling