When your body tenses in a design review, name what…
When you feel chest tightening or jaw tension during a design review or technical discussion, write down 'I notice I want to protect [X]' before formulating your response to create separation between observation and defense.
When This Fires
- Someone challenges your design decision in a review meeting
- A code review comment feels like it's questioning your competence, not your code
- A junior engineer suggests an alternative approach to something you built
- Any technical discussion where you notice physical tension before intellectual disagreement
Common Failure Mode
Constructing a sophisticated technical argument while ignoring the somatic signal. Your body is telling you this is emotional, but your response sounds purely technical — and because it sounds technical, no one (including you) recognizes the defense for what it is. The argument may even be correct. But it's being generated by a threat response, not by genuine technical evaluation, which means you'll defend it beyond where the evidence supports it.
The Protocol
When you notice chest tightening or jaw tension in a technical discussion: (1) Do not respond immediately. (2) Write (on paper, in a notes app, anywhere) "I notice I want to protect ___" and fill in the blank honestly. (3) Ask yourself: "If I weren't protecting [X], would I still make this same argument?" (4) If yes — make the argument, now grounded in technical merit rather than defense. If no — consider the possibility that the critique has merit and your defense is emotional.