What does it mean that the bottleneck journal?

Track your bottlenecks over time to see whether they are shifting or chronic.

Example: You start a bottleneck journal in January. For the first six weeks, the entries tell a monotonous story: decision paralysis, severity 4, every week. You try interventions — decision frameworks, time-boxed choices, pre-commitment rules — and the severity drops to 2. Then in March, the journal shifts. Decision-making barely registers. The new constraint is information overload: three major projects launched simultaneously, and you cannot process the incoming data fast enough to act on any of them. By April, information overload fades and energy becomes the binding constraint — spring allergies, disrupted sleep, a severity-5 wall every afternoon at 2 PM. When you review the quarter's entries in a single sitting, the pattern is unmistakable: your bottleneck is seasonal and context-dependent, not chronic. Winter produces decision constraints. Q1 planning produces information constraints. Spring produces energy constraints. No single-point measurement would have revealed this. The journal did.

Try this: Open whatever capture tool you will actually use — a notebook, a spreadsheet, a daily note in your knowledge system — and create your first bottleneck journal entry right now. Record today's date. Write one sentence naming the constraint that most limited your throughput today. Rate its severity from 1 (minor friction) to 5 (system halt). Classify it: human, tool, process, information, decision, or energy. If you attempted an intervention, note what you did and what happened. If you did not intervene, write 'observed only.' Commit to making this entry every workday for the next four weeks. Set a weekly review reminder for the same day each week. The journal has no value until it has at least seven entries. Start today so that your first weekly review is possible in seven days.