Question
How do I practice workflow bottleneck identification?
Quick Answer
Select a workflow you perform at least monthly — a content pipeline, a client onboarding process, a project delivery cycle, a weekly review. Write out every step and estimate how long each step takes in practice (not how long it should take — how long it actually takes, including delays, procrastination, and waiting).
Now identify which single step takes the longest or causes the most downstream waiting. That is your bottleneck. Ask three questions about it: Can I break this step into smaller sub-steps to find where time is actually lost? Can I start this step earlier or give it more resources? Can I remove a hidden dependency that is making this step wait unnecessarily? Design one concrete change to the bottleneck step and test it on your next cycle. Measure whether total workflow time decreases.
Common pitfall: The most common failure is optimizing a non-bottleneck step. You make your fastest step even faster while the slowest step remains untouched. Total throughput does not change. The second failure is identifying the wrong bottleneck — confusing the step that feels most painful with the step that actually constrains throughput. Pain and constraint are not the same thing. A step might feel tedious without being slow. A step might feel easy while quietly consuming the most calendar time because of hidden waiting. The third failure is fixing one bottleneck and then stopping, failing to recognize that a new step has now become the constraint. Bottleneck management is a cycle, not a one-time fix.
This practice connects to Workflow Design — building it as a repeatable habit compounds over time.
Learn more in these lessons
- Workflow bottlenecks
Identify the slowest step in each workflow — that step determines your throughput.
Go beyond the answer
This topic is part of Build Systems Beyond Yourself — a guided sequence of 20 lessons.
After completing this path you will have documented your key workflows, identified where YOU are the bottleneck (your bus factor is currently 1), built delegation criteria for systems, tools, habits, and people, and begun the identity shift that makes letting go feel like freedom instead of failure — because operational excellence means your systems run reliably without your constant attention.
Start the path →