If–Then Plans for Habits: Turn Intention Into a Cue

An if–then plan removes a decision from the moment of action:

If I finish lunch, then I will walk outside for ten minutes.

The “if” identifies a situation. The “then” defines one observable response.

The short answer

Choose a cue that reliably occurs and a response that can begin in that context. Write one sentence, prepare the required tools, and test it during an ordinary week. Add only one fallback for the most common disruption.

Why context matters

Studies of context stability associate more consistent repetition contexts with stronger automaticity and goal attainment. A later randomized walking study found that stable context supported automaticity but did not guarantee maintained walking volume. An if–then sentence is therefore a design aid, not a guarantee.

Write a usable plan

A strong cue happens often enough, is easy to notice, and occurs when the action is possible. A strong response is specific and small enough for the available context.

“If it is morning, I will be productive” is too broad. “After I pour coffee, I will open the report and write the next heading” is testable.

Use four checks:

Part	Question
Cue	Does it happen often enough?
Noticeability	Will I recognize it?
Opportunity	Are time, place, and tools available?
Response	Is completion observable and realistically sized?

Then prepare the environment before the cue. A good sentence cannot compensate for shoes in another location or a document you cannot access.

Add one fallback without creating a complex decision tree:

If lunch ends before 2 p.m., I will walk for ten minutes.
If a meeting replaces lunch, I will walk for five minutes after my last call.

Test and revise in five steps

1. Choose one intended behavior.
2. List three situations that already repeat.
3. Select the cue with the best real opportunity.
4. Define the normal response and one fallback.
5. Review after a week using facts.

After a miss, ask whether the “if” event happened and whether you noticed it. If the cue is unstable, choose another anchor. If it worked but the action was unavailable, reduce or move the response.

One interruption may require no change. Repeated misses in the same context justify adjusting one parameter. Avoid adding several nested contingencies, raising frequency and difficulty together, or writing a response such as “be productive” that still requires interpretation.

Signs that the design is improving include remembering at the cue, needing fewer preparation decisions, and returning more easily after disruption. Automaticity is not the same as enjoyment or perfect execution.

Match the sentence to the actual frequency. A weekly review does not need a daily cue, and a recovery-dependent action should not fire regardless of sleep or symptoms. Where necessary, make the condition include the real safety or capacity boundary instead of treating every occurrence as mandatory.

How to use Flamy

Record the sentence in the task name or description and award XP for the baseline response. Review the cue and completion pattern after several repetitions rather than preserving a broken design for the streak.

For more cue design, read habit cues and from planning to action.

Write one plan today

1. Name the cue.
2. Name the response.
3. Check opportunity and tools.
4. Add one fallback.
5. Test it for a week.

Test an if–then plan in Flamy