Implementation Intention¶
Core Idea¶
An implementation intention pre-binds a specific future cue to a specific action — "when X occurs, I will do Y" — so that at the moment of execution the cue triggers the behavior without re-deliberation. The decision is made once, in advance; at runtime the system only matches and dispatches.
How would you explain it like I'm…
When-Then Plan
Before bed you decide once: 'When I wake up, I'll put on my shoes by the door.' Then in the morning you don't have to think — seeing the door reminds you, and you just do it. An implementation intention is deciding ahead of time 'when THIS happens, I'll do THAT,' so later it happens almost by itself.
Decide-Ahead Trigger
An implementation intention is a plan shaped exactly like 'when X happens, I will do Y,' made AHEAD of time so you don't have to decide in the moment. Normally, wanting to do something and actually choosing to do it right now are two separate steps, and the second step is where people freeze or forget. By picking the trigger and the action in advance — 'when the bell rings, I start my homework' — you hand the decision off to the fast, automatic part of you. Then when the trigger shows up, you just match it and go, no arguing with yourself. It works best when the trigger is specific, the link is strong, and nothing else is competing to grab you at that moment.
Pre-Wired If-Then
An implementation intention pre-binds, in advance, a specific future cue to a specific action — 'when X occurs, I will do Y' — so that at the moment of execution the cue triggers the behavior without re-deliberation. It decouples the intention to act from the decision to act NOW by compiling the conditional ahead of time and handing it to whatever fast, low-attention mechanism runs the trigger. The power comes not from the if-then shape itself — any rule is a conditional — but from the pre-binding-under-absent-deliberation condition: the decision is made once, in advance, and at runtime the system only matches and dispatches. The load-bearing parts are a cue specification (a future condition named precisely enough to be recognized), a bound action paired with it ahead of time, a registration step that installs the binding wherever it will fire, and an execution path that doesn't consult deliberation once the cue fires. Robustness depends on three things: cue specificity, binding strength, and the absence of competing triggers that could hijack the dispatch.
An implementation intention pre-binds, in advance, a specific future cue to a specific action — 'when X occurs, I will do Y' — so that at the moment of execution the cue triggers the behavior without re-deliberation. The pattern decouples intention to act from decision to act now by compiling the conditional ahead of time and shipping it to whatever fast, low-attention mechanism runs the trigger. The structural force comes not from the conditional shape itself — any rule is a conditional — but from the pre-binding-under-absent-deliberation condition: the decision is made once, in advance, and at runtime the system only matches and dispatches. The load-bearing components are a cue specification naming a future condition with enough precision to be recognized; a bound action paired with that cue ahead of execution time; a registration step that installs the binding in whatever mechanism — memory, rule table, handler — will fire it; and an execution path that does not consult the deliberative process once the cue fires. The pattern is the generic mechanism that ships a decision from a slow, deliberative subsystem to a fast, automatic one, and it applies wherever such a two-tier execution architecture exists. Robustness depends on three things: cue specificity, binding strength, and the absence of competing triggers that could capture or override the intended dispatch.
Broad Use¶
- Health psychology: "when I finish lunch, I will take my medication" converts an open-ended goal into an executable conditional.
- Software systems: event handlers, interrupt vectors, and trigger-action rules (IFTTT) fire automatically when the cue matches.
- Military doctrine: standing orders and battle drills precompile action so it runs under load when deliberation is too slow.
- Aviation and medicine: branching checklists — "if cabin altitude exceeds the threshold, masks on" — bind responses to named cues.
- Organizations: pre-mortems and tripwires name a threshold and the action it triggers before bias can bend the decision.
Clarity¶
Separates holding a goal from having a precompiled rule to execute toward it, so the intention-behavior gap reads as a missing binding, not weakness of will.
Manages Complexity¶
Pushes branching decisions out of the hot path: the system pre-binds responses to a sparse set of named cues, so load at execution drops to cheap recognition.
Abstract Reasoning¶
Cleanly separates the cue lattice (what is recognized) from the action policy (what is bound), so a failure localizes to recognition, binding, or execution.
Knowledge Transfer¶
- Embedded systems: an interrupt service routine fires reliably where a polling loop with manual dispatch would not.
- Organizational finance: a board tripwire binds a painful action to a named burn-rate threshold before motivated reasoning intervenes.
- Product design: nudges encode the answer rather than asking the user what to do.
Example¶
An aviation rapid-decompression checklist binds "if cabin altitude exceeds 14,000 feet" to "don masks, descend" via prior briefing, so the crew fires the precompiled response under hypoxia rather than deliberating.
Relationships to Other Abstractions¶
Current abstraction Implementation Intention Prime
Parents (1) — more general patterns this builds on
-
Implementation Intention is a kind of Prospective Memory Prime
An implementation intention is prospective memory specialized by pre-binding a future cue to a particular action.
Hierarchy paths (5) — routes to 4 parentless roots
- Implementation Intention → Prospective Memory → Associative Memory → Search and Retrieval → Problem Space → Representation → Abstraction
Show alternative paths (4)
- Implementation Intention → Prospective Memory → Associative Memory → Search and Retrieval → Trade-offs → Constraint
- Implementation Intention → Prospective Memory → Associative Memory → Network → Reservoir-Flux Network → Conservation Laws → Invariance
- Implementation Intention → Prospective Memory → Associative Memory → Search and Retrieval → Problem Space → State and State Transition → Phase Space
- Implementation Intention → Prospective Memory → Associative Memory → Search and Retrieval → Problem Space → Problem Representation → Representation → Abstraction
Not to Be Confused With¶
- Implementation Intention is not a Commitment Device because a commitment device binds future choice by making defection costly (fighting temptation), whereas an implementation intention binds future execution by precompiling a cue-action link (fighting forgetting and hesitation).
- Implementation Intention is not Conditioning because conditioning installs a cue-response link gradually over many trials, whereas an implementation intention installs it by a single explicit declaration, then must survive against consolidated habits.
- Implementation Intention is not Foresight because foresight keeps options open by surveying possible futures, whereas an implementation intention closes options by pre-binding one response to one cue.