Ask most teams where their biggest bottleneck is, and you'll get a confident answer based on whatever felt frustrating most recently. That's usually not the same thing as the actual constraint slowing down the whole system, which tends to be quieter and less visible than the loudest recent complaint.
Finding the real one takes a slightly different approach than trusting the first guess.
Most teams are guessing, not measuring
The stage of a process that generates the most complaints isn't necessarily the one causing the most delay. A visible, annoying step gets noticed; a quiet stage where work sits for three days without anyone commenting can easily be the bigger problem, simply because nobody's complaining about it.
Look for where work actually piles up
The most reliable signal is where work accumulates. Look at every stage of a process and ask where items sit the longest before moving to the next step. That stage, not the one people talk about most, is very often the real constraint.
In Stelaah, project and task views show exactly how long work has sat in each stage, making a genuine pileup visible instead of a matter of impression. See how projects works.
Check if one person is quietly the constraint
Sometimes the bottleneck isn't a stage of the process at all, it's a single person whose approval or input every path runs through. If one name shows up as a dependency on an unusually large share of stalled work, that's the actual bottleneck, no matter what the process diagram says.
Confirm it by removing it, even briefly
Before committing real effort to fixing a suspected bottleneck, test the theory cheaply. Temporarily add capacity to that one stage, even informally, for a short period, and see whether the whole system speeds up. If it does, you've found the real constraint. If it doesn't, look elsewhere.
Resist fixing the first bottleneck you notice
Once one bottleneck is fixed, another one, previously hidden behind it, will usually appear. That's expected, not a sign the first fix failed. Treat bottleneck-finding as an ongoing practice, not a single project with a defined end.
A simple checklist
If you do nothing else, do these five things:
- Don't trust the loudest recent complaint as the real bottleneck.
- Look for where work actually piles up longest, stage by stage.
- Check whether one person is a dependency on an unusual share of stalled work.
- Test a suspected bottleneck cheaply before committing to fix it.
- Expect a new bottleneck to appear once the current one is resolved.
Do that, and you're fixing the constraint actually slowing the system down, instead of whichever step happened to generate the most recent complaint.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
