What is how to find bottleneck in workflow?

How to find bottleneck in workflow is a concept in personal epistemology: Improving anything other than the bottleneck does not improve the system.

Example: You have been frustrated with your personal productivity for months. You spend a weekend reorganizing your note-taking system — migrating apps, redesigning your folder structure, importing templates, watching tutorials on advanced features. The new system is beautiful. You feel the rush of progress. Monday morning arrives and nothing changes. Your weekly output is the same. Your projects move at the same pace. The backlog does not shrink. Three weeks later, you run a simple diagnostic: you track where every hour goes for five consecutive workdays. The data reveals that you spend eleven hours per week in meetings that produce no decisions, no actions, and no information you could not have received in a five-minute summary. Your bottleneck was never your note-taking system. It was the eleven hours of your week consumed by meetings that serve no purpose — hours that could have been focused work, synthesis, or execution. You optimized the wrong thing. The system did not care.

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