Log contradictions instead of resolving them — patterns…
Before forcing resolution of contradictory observations or beliefs, accumulate multiple instances in a contradiction log to enable pattern detection impossible from individual contradictions.
When This Fires
- You encounter evidence that contradicts a belief you hold
- Two credible sources disagree about the same phenomenon
- Your experience contradicts what theory predicts
- Any time you feel the urge to immediately decide "which one is right"
Common Failure Mode
Resolving too quickly by dismissing one side. "That study must have had a flawed methodology" or "my experience is probably an outlier." These dismissals feel like thinking but are actually cognitive dissonance reduction — you're protecting your existing belief by explaining away the contradicting evidence. The log prevents this by requiring you to hold both sides as unresolved until the pattern clarifies.
The Protocol
When you encounter a contradiction: (1) Do not resolve it. (2) Log both sides explicitly: "Observation A: [claim + evidence]. Observation B: [contradicting claim + evidence]." (3) Note the context for each: when, where, under what conditions did each observation arise? (4) Add to your contradiction log. (5) Review the log periodically (monthly). After 3-5 instances in a domain, ask: "What pattern do these contradictions reveal about the domain's structure?" The resolution, when it comes, will be richer than any single-instance resolution could be.