Random skipped captures = friction problem; clustered…
Classify each skipped capture by checking whether failure frequency is random across topics (friction problem requiring tool improvement) or clustered in specific domains (resistance problem revealing avoidance patterns).
When This Fires
- During weekly reviews when evaluating capture system health (Ask four diagnostic questions during weekly review…)
- When you notice you're "bad at capturing" but can't explain why
- After improving capture tools and still missing important thoughts
- Any time you're trying to diagnose why your capture practice has gaps
Common Failure Mode
Assuming all skips are friction and endlessly optimizing tools. You buy a better app, configure a faster shortcut, get a voice recorder — and still miss the same captures. Because those specific skips were never about friction. They were about the discomfort of writing down what the thought implies. No tool optimization can fix an avoidance pattern.
The Protocol
Over two weeks: (1) When you notice a skipped capture (a thought you had but didn't write down), log it: what was the thought about, and why did you skip? (2) After two weeks, review the log. (3) Check distribution: are skipped topics scattered randomly? → Friction problem. Improve tools and reduce capture latency. (4) Are skipped topics clustered in specific domains (relationships, money, career, health)? → Resistance problem. The cluster reveals what you're avoiding. Those domains are your highest-priority capture targets.