Capture emotions now, interpret them later in review…
Defer emotional interpretation to review sessions when multiple entries enable pattern recognition, rather than explaining emotions during initial capture.
When This Fires
- During journaling or emotional logging when you catch yourself writing "because..."
- When a strong emotion arrives and you want to understand why
- Any moment when you're tempted to explain a feeling in real-time
- During daily captures that will later feed weekly or monthly reviews
Common Failure Mode
Writing elaborate causal stories during capture: "I feel frustrated because Sarah doesn't respect my expertise, which is part of a pattern where the team undervalues technical input." This feels insightful but is confabulation — your frustrated brain constructing a narrative that justifies the frustration. The narrative hardens into a belief before you've checked whether the pattern actually exists across multiple data points.
The Protocol
During capture: write only (1) what happened (observable events), (2) what you felt (emotion label), and (3) what your body did (physical sensations). Stop there — do not add "because." During weekly review: look across 5-7 entries and ask "what patterns emerge across these captures?" Patterns visible across entries are genuine signals. Explanations generated inside a single emotional moment are almost always confabulation.