What is how to find and fix bottlenecks in your workflow?

How to find and fix bottlenecks in your workflow is a concept in personal epistemology: Identify exploit and elevate your personal bottlenecks systematically.

Example: You are a product manager who ships a weekly analysis memo to your leadership team. The memo requires three inputs: customer data from your analytics dashboard, competitive intelligence from your research notes, and a written synthesis that frames the implications. You have been trying to improve your output by getting faster at pulling customer data — automating queries, building dashboards, streamlining exports. After three weeks of optimization, your memo still takes the same eleven hours to produce. You step back and map the actual flow. Data extraction takes ninety minutes. Competitive research takes two hours. The synthesis — sitting down and writing the actual analysis — takes seven hours, spread across three days because you keep getting interrupted and losing your thread. The constraint is not data extraction. It never was. The constraint is uninterrupted synthesis time. You have been optimizing a non-constraint while the bottleneck sits untouched. Applying Goldratt's Five Focusing Steps, you first exploit the constraint: you block a four-hour window on Tuesday mornings, silence all notifications, and write the synthesis in a single session instead of fragmented bursts across three days. Synthesis time drops from seven hours to three and a half. You then subordinate everything else to the constraint: you move data extraction and competitive research to Monday afternoon so the inputs are ready before your Tuesday writing block. Finally, you elevate: you develop a synthesis template that gives you a structural scaffold so you spend less time deciding how to organize the analysis and more time actually analyzing. Your weekly memo now takes five hours instead of eleven. The improvement came entirely from focusing on the constraint. Every hour you spent optimizing data extraction was wasted.

This concept is part of Phase 48 (Bottleneck Analysis) in the How to Think curriculum, which builds the epistemic infrastructure for bottleneck analysis.