How do I practice optimize the bottleneck first?

The most direct way to practice optimize the bottleneck first is through a focused exercise: Map a system you operate — a workflow, a daily routine, a project pipeline, a learning process. List every sequential step. For each step, estimate the time it takes and whether downstream steps must wait for it. Identify which step most frequently causes the rest of the system to wait. This is your current bottleneck. Now list the last three improvement efforts you made to this system. For each, answer honestly: did you improve the bottleneck, or did you improve a non-constraint? If you improved a non-constraint, estimate how much system-level throughput actually changed. The answer is likely close to zero. Finally, generate three specific actions that would reduce the duration or increase the capacity of your actual bottleneck. Rank them by effort-to-impact ratio. Execute the highest-ranked action this week and measure whether system throughput changes.

Common pitfall: The most common failure is optimizing what is visible rather than what is constraining. The step that annoys you most, the step that feels slowest, the step where you have the most expertise — these are the steps that attract optimization effort. But annoyance, subjective slowness, and expertise availability are not indicators of constraint status. A step can be annoying without being the bottleneck. A step can feel slow because you dislike it, not because it limits throughput. And your expertise makes non-constraint optimization easy, which makes it tempting, which makes it a trap. The second failure is optimizing the bottleneck without re-identifying the constraint afterward. When you successfully improve a bottleneck, the constraint moves — to the next weakest link. If you keep optimizing the old bottleneck past the point where it is no longer the constraint, you have reverted to non-constraint optimization. Bottleneck-first is not a one-time diagnosis. It is a continuous discipline of re-identification.

This practice connects to Phase 29 (Agent Optimization) — building it as a repeatable habit compounds over time.