Design triggers for your worst cognitive day…

When This Fires

• When designing any new trigger — ask "would this work when I'm exhausted?"
• When a trigger works on good days but fails on bad days — it was designed for peak state
• When reviewing trigger reliability data that shows day-of-week or energy-level patterns
• Complements Emotional trigger actions must be executable while… (emotional trigger design) with the general cognitive-state principle

Common Failure Mode

Designing triggers during a motivated Sunday planning session: "I'll notice the visual cue on my desk and immediately start deep work!" On a depleted Wednesday afternoon, you walk past the cue without registering it because your attentional bandwidth is consumed by the day's accumulated demands. The trigger was calibrated for Sunday-morning attention levels, not Wednesday-afternoon levels.

The Protocol

(1) After designing a trigger, apply the minimum-state test: "Would this trigger work if I were tired, distracted, and unmotivated?" (2) If no → the trigger is too subtle for worst-case conditions. Amplify it: louder alarm, more obstructive physical cue, additional redundant channels (Stack time + location + preceding action into compound…, When triggers fail to fire, increase signal strength…). (3) If the action requires cognitive resources that won't be available when depleted → simplify the action to its minimum viable version (Start every new agent at under two minutes with zero…). (4) Test on an actual bad day: the trigger's effectiveness on your worst day is its true reliability ceiling. Good-day performance is a misleading overestimate. (5) Design principle: if it works when you're depleted, it definitely works when you're sharp. The reverse is not true.