Start with a real decision
The easiest way to understand Implementation Intentions is to compare versions that look similar on the surface but do very different jobs. The practical purpose here is to connect a specific cue with a pre-decided response. That gives us a useful test: does the exercise make the next response clearer, or does it simply create more material to monitor?
Use one situation all the way through the comparison: finishing dinner, reaching for the phone, and wanting to begin a ten-minute portfolio block. Keeping the context fixed makes it easier to see which part of the method adds value and which part adds ceremony.
A strong example is concrete enough to test
Example: If I finish dinner and notice my hand going to the phone, then I will put the phone on charge, open the portfolio file and work for ten minutes before deciding whether to continue.
This version works because it keeps Implementation Intentions close to its actual mechanism: cue–response planning and prospective memory. It names a situation you could recognise in ordinary life and gives the practice a natural handoff. Once the useful response is clear, the exercise is allowed to finish.
With Implementation Intentions, notice what the example does not ask you to prove. No special mood or coincidence is needed; success is judged by whether the exercise improves the nearest decision, response or behaviour.
The weak version sounds fine but gives little guidance
Example: If I feel motivated, then I will work on my goals.
The problem is not that this sentence is insufficiently positive. It is that it leaves the important part undefined. With Implementation Intentions, vague language makes it harder to tell what the exercise is for, when it applies and what should happen afterwards.
A useful repair is to replace one abstraction with an observable detail. For this method, begin with one cue you can recognise without interpretation and one response small enough to start immediately. The resulting version may sound less grand, but it gives you something you can actually use.
Overcomplicated: when the method becomes the task
Example: Writing a separate if–then rule for every possible mood, interruption, time of day and imagined setback until maintaining the rule list becomes a task of its own.
This is where Implementation Intentions stops supporting the goal and starts competing with it. The characteristic risk is turning planning into overengineering, using vague cues, or adding so many rules that the real behaviour gets less attention. More steps are justified only when they help you make a better distinction or response. If complexity exists mainly to make the practice feel safer, more certain or more “complete,” it is usually a sign to remove something.
Compare the three versions by their after-effect
A strong Implementation Intentions example hands something usable back to the day. A weak one sounds encouraging but leaves the next move unclear, while an overbuilt one makes you manage the technique. That practical after-effect matters more than how polished the wording appears.
For Implementation Intentions, one useful metric is whether the cue was noticed and the planned response began. That measure is deliberately close to the practice. It avoids claiming that the exercise controls factors that depend on timing, skill, chance, other people or conditions outside your control.
A quick field test
Take the running situation—finishing dinner, reaching for the phone, and wanting to begin a ten-minute portfolio block—and write your own version in one or two sentences. Then ask three questions. Can I tell exactly when this applies? Can I tell what I will do or notice next? Can I stop the exercise without feeling that I have left it incomplete?
If you cannot comfortably stop Implementation Intentions after the exercise has done its job, remove a step before adding more practice. The method should support action without becoming a way to repeatedly seek certainty.
Keep the claim proportional to the evidence
The plan does not remove choice or guarantee success; it simply makes the intended response easier to retrieve at the right moment. That boundary does not make the practice pointless. It keeps the useful psychological part separate from claims that are much harder to establish.
When people report that Implementation Intentions “worked,” several things may be mixed together: clearer attention, more consistent behaviour, expectancy, ordinary luck and external circumstances. You can value a method without giving it credit for every event that follows.
Test the cue before you test the whole plan
Implementation intentions fail surprisingly often because the cue is badly chosen rather than because the response is weak. A cue that is visible in the environment—closing a browser tab, putting a mug in the sink, arriving at a desk—usually gives cleaner feedback than a cue such as “when I feel ready.” In the portfolio example, you can test whether finishing dinner reliably creates the opportunity to start. If the cue is inconsistent, change the cue first. That diagnostic step is specific to if–then planning and prevents you from rewriting the response when the real problem is that the trigger never becomes salient.
Bottom line
A good Implementation Intentions example is specific, bounded and connected to the job of connect a specific cue with a pre-decided response. A weak one stays vague. An overcomplicated one makes the ritual harder to maintain than the behaviour it was meant to support. Keep the version that improves the next real decision, and drop the extra machinery.