What does it mean that workflow bottlenecks?

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.

Try this: 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.