Make implementation intention triggers highly specific…
When using implementation intentions to create behavioral pauses, specify the triggering situation at high detail ('If I receive code review feedback challenging my approach...') rather than generically ('If I get criticism...') to increase cue detectability.
When This Fires
- Creating implementation intentions for emotional regulation (pausing before reacting)
- Designing if-then rules for habit formation or behavior change
- When existing implementation intentions aren't firing in the relevant situations
- Any behavior-design context where you want a pre-loaded response to a specific trigger
Common Failure Mode
Writing generic intentions: "If I feel stressed, I'll take a breath." "Feeling stressed" is too broad and constant — you're always somewhat stressed, so the cue never stands out from background noise. Specific: "If I notice my jaw clenching during a design review, I'll take three breaths before responding." The jaw-clenching cue is detectable because it's physically specific and context-bound.
The Protocol
When creating an implementation intention: (1) Describe the triggering situation with sensory detail: where are you, what just happened, what physical sensations or environmental cues are present? (2) "If I [specific situation with sensory detail], then I will [specific behavior]." (3) Test: can you vividly imagine the situation? If the mental image is blurry, the cue needs more detail. (4) Rehearse: mentally simulate encountering the specific cue and executing the behavior. 3-5 mental rehearsals significantly increase firing probability.