Bottleneck journal: 6 fields, under 2 minutes — sustainability beats thoroughness
Record bottleneck journal entries in under two minutes using six fields only (date, constraint name, severity 1-5, type, intervention, result) to maintain practice sustainability.
Why This Is a Rule
Tracking practices die from friction. A 15-minute journal entry produces rich data for one week, then gets abandoned. A 2-minute journal entry produces leaner data for months — and longitudinal data always beats rich-but-short data for pattern detection.
The six-field constraint is the minimum viable bottleneck record: date (when), constraint name (what's the bottleneck), severity 1-5 (how bad), type (capacity/policy/knowledge/coordination), intervention (what you tried), result (what happened). These six fields capture enough structure to detect patterns across entries while keeping each entry under the 2-minute threshold where journaling feels effortless rather than burdensome.
The Theory of Constraints insight underlying this rule: sustainable constraint tracking produces compound returns. After 30 entries, you can see which constraint types recur, which interventions work, and which bottlenecks migrate when you fix them. This meta-level visibility is impossible from any single thorough analysis but emerges naturally from sustained lightweight tracking.
When This Fires
- Starting a bottleneck tracking practice for personal or team productivity
- When a previous tracking system was abandoned because entries took too long
- During any continuous improvement effort that requires longitudinal data
- When you want to identify recurring constraints without committing to heavy process
Common Failure Mode
Adding fields "for completeness" — root cause analysis, stakeholder impact, priority matrix. Each additional field pushes the entry time up, and the practice dies within two weeks. The six fields are a carefully chosen minimum. If you need deeper analysis for specific entries, do it separately — don't add complexity to the daily recording.
The Protocol
Daily (or per-incident): (1) Open your bottleneck journal (spreadsheet, note, structured form). (2) Fill six fields: date, constraint name, severity (1-5), type (capacity/policy/knowledge/coordination), intervention attempted, result. (3) Close. Total time: under 2 minutes. (4) Weekly: scan the last 5-7 entries for patterns. Monthly: review all entries for recurring constraints and intervention effectiveness. The patterns that emerge from 30+ lightweight entries are more actionable than any single detailed analysis.