What does it mean that process bottlenecks?

Inefficient processes create artificial constraints that can be designed away.

Example: You produce a weekly status report for your team. The actual writing takes 30 minutes. But the process you inherited requires seven steps: gather data from three different dashboards, paste it into a shared doc, format it according to a template from 2019, send it to your lead for review, wait for their edits (usually none), forward it to the department head for approval (always approved without changes), then post it to the team channel. Total elapsed time: 4 hours spread across two days, mostly spent waiting and formatting. The report has never been rejected. The review adds nothing. The formatting template references metrics your team stopped tracking eighteen months ago. The 30 minutes of value-creating work is buried inside 3.5 hours of process waste that nobody designed and nobody questions — because the process was there before you arrived, and you assumed it existed for a reason.

Try this: Pick one recurring process in your work or personal life — something you do at least weekly. Map every step from trigger to completion. For each step, classify it as one of three types: (1) value-adding — this step directly produces the output or moves it meaningfully forward, (2) necessary non-value-adding — this step does not produce output but is genuinely required by a real constraint (legal, safety, coordination), or (3) pure waste — this step exists because of habit, legacy, or assumption and could be eliminated without consequence. Count the steps in each category. Calculate the time spent on each category. Then ask: if I eliminated every pure-waste step and streamlined every necessary-non-value-adding step, how much faster would this process be? Write down the redesigned process with only the value-adding and genuinely necessary steps. Try running the redesigned version next week.