What are persistent bottlenecks?

A persistent bottleneck is a specific weak spot in a process that constantly slows everything down, no matter how much you try to speed up other parts.

Imagine your kitchen faucet. If the pipe leading into the sink is narrow, water dribbles out slowly even if the big water tower behind it is full and pressurized. You can turn the handle as wide open as possible, but that small pipe still dictates how fast the bowl fills. That tiny pipe is the bottleneck. It persists because it limits the entire flow of your "water" (or tasks, or cars, or products).

Bottlenecks are persistent when they don’t disappear just because you add more resources elsewhere. For example, if you hire three more chefs but only have one oven, the extra chefs will stand around waiting for the oven to finish baking cookies. The oven remains the bottleneck because its capacity is fixed. You cannot fix the problem by simply making the chopping faster or plating food quicker; those parts are already fast enough. The constraint sticks out like a sore thumb until you specifically address it, perhaps by buying a second oven or redesigning how the food enters it.

Think of it like a playground slide. If ten kids run up the ladder quickly but must wait in a line to go down one slide, the slow part isn’t climbing up; it’s that single narrow opening at the top. Adding more ladders doesn’t help much. The bottleneck persists because the physical limit (the slide width) hasn’t changed. To solve it, you have to widen the slide or add another one, not just make the kids climb faster.