When pressure changes your decision, document both…
When pressure causes your actual decision to differ from what you would decide without pressure, document both the decision and the pressure type (social, authority, time, emotional, financial) to build a personal pressure vulnerability map.
Why This Is a Rule
Everyone has specific pressure vulnerabilities — types of pressure that reliably cause decision-quality degradation. Some people cave to social pressure but resist time pressure. Others resist authority pressure but fold under financial pressure. Without a vulnerability map, you can't design pre-commitments for your specific weaknesses — you're defending generically against all pressure types when specific types are your actual attack surface.
The documentation protocol is simple: when you notice your actual decision differs from what you'd choose without pressure, record: what you decided, what you would have decided without pressure, and which pressure type drove the deviation (social — fear of judgment or disapproval, authority — deference to power, time — artificial urgency, emotional — guilt/sympathy/anger, financial — money-driven override of judgment).
After 10-20 documented pressure deviations, the pattern emerges: maybe 70% of your pressure-induced deviations are social (people-pleasing), 20% are authority (deference to hierarchy), and 10% are time (urgency compliance). Now you know exactly where to invest in structural protection: Design pre-commitments when calm to constrain behavior… pre-commitments targeted at your dominant pressure vulnerability.
When This Fires
- When you notice yourself deciding differently than you would have chosen in calm conditions
- When a decision "felt wrong" but you went along with it — the pressure type explains why
- During decision journal reviews (Review decisions in three steps) when identifying which decisions were pressure-influenced
- Complements Ask 'Given that I compromised this value, what… (pre-mortem for values vulnerability) with the real-time pressure documentation
Common Failure Mode
Attributing all pressure-influenced decisions to "weakness" without differentiating the pressure type. "I need to be stronger" doesn't tell you what to protect against. "I fold under social pressure from authority figures in meetings" tells you exactly when and how to prepare (Pre-write responses to 3-5 predicted boundary tests… pre-written responses for predicted tests).
The Protocol
(1) When you notice a pressure-influenced decision, document: Actual decision: what you chose. Counterfactual: what you would have chosen without pressure. Pressure type: social, authority, time, emotional, or financial. (2) No self-judgment — this is data collection, not self-criticism. The goal is a vulnerability map, not a shame record. (3) After 10+ entries: analyze. Which pressure type dominates? Which contexts trigger the most deviations? (4) Design targeted protection for the dominant vulnerability: pre-commitments (Design pre-commitments when calm to constrain behavior…), pre-written responses (Pre-write responses to 3-5 predicted boundary tests…), or structural barriers (Upgrade commitment enforcement to Level 3+…). (5) Track: does the deviation rate for the targeted pressure type decrease after intervention?