Question
What is workflow bottleneck identification?
Quick Answer
Identify the slowest step in each workflow — that step determines your throughput.
Workflow bottleneck identification is a concept in personal epistemology: Identify the slowest step in each workflow — that step determines your throughput.
Example: You run a weekly content pipeline: research on Monday, draft on Tuesday, edit on Wednesday, design graphics on Thursday, publish on Friday. You spend weeks refining your editing process — better checklists, tighter prose, faster turnaround. Editing now takes two hours instead of four. But your total pipeline still takes five days, because the research step on Monday consistently runs until Tuesday morning, pushing the draft to Wednesday, which pushes everything else. You optimized the wrong step. Editing was never the bottleneck. Research was. Every hour you invested in editing speed was wasted effort, because the workflow could never move faster than the research step allowed.
This concept is part of Phase 41 (Workflow Design) in the How to Think curriculum, which builds the epistemic infrastructure for workflow design.
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 →