Behaviour (Fogg B=MAP)
Implicit Prompt
Place, person, situation, emotion
What it is
An Implicit Prompt cues action through an association in memory — a place, a person, a situation, or an emotion. The cue lives in the user's environment, not in the product.
Why it works
An implicit prompt lives in the user''s environment rather than in the product: a time of day, a place, a preceding action, a recurring feeling. This is the mechanism behind habit formation as described in the research literature, where a stable context cue becomes automatically associated with a behaviour through repetition. Wendy Wood''s work on habit shows that a large share of daily behaviour is context-triggered rather than deliberate, and that stability of the cue matters more than motivation — which is why habits survive changes in intention but break when someone moves house or changes job. Implementation intentions, studied by Peter Gollwitzer, exploit this deliberately: specifying when and where an action will happen substantially raises the rate at which it does, because the plan hands control to the environment.
How to apply it in design
Design the product to attach itself to a recurring environmental cue (a time of day, a location, a feeling). Once attached, the cue itself triggers the behavior without external reminders.
Where you'll see it
- Onboarding that asks the user when and where they will do this
- Anchoring the behaviour to an existing routine rather than to a clock
- Location or context-aware entry points that appear where the need arises
- Widgets and surfaces that sit inside a routine the user already has
- Reminders that fade out as the routine becomes established
Example
A plant care app that ties watering reminders to "Sunday morning coffee" once — after that, the coffee becomes the prompt, and the app fades into the background.
Failure mode
Trying to be the prompt itself (constant push notifications) instead of attaching to an existing routine creates fatigue and gets the app muted or deleted.
When not to use it
Implicit prompts require a stable cue, so they do not work for behaviours with no natural home in the user''s day. Infrequent or unpredictable tasks are better served by an explicit reminder at the moment of need. They are also slow: a context association takes repetition to form, which makes them the wrong instrument for a launch or a time-limited campaign. And they fail during exactly the disruptions people most need help through — moving, travelling, changing jobs — which is when explicit support should temporarily take over.
The ethical line
Habits are durable by design, which makes their construction a responsibility rather than a neutral technique. The reasonable test is whether the user would endorse having this habit if they thought about it explicitly — someone who wanted to read more will thank you for attaching reading to their commute, while someone who did not choose to check a feed at every red light will not. The related obligation is exit: a product that deliberately builds a routine should make breaking it straightforward, with usage visible and controls that actually work rather than a settings page designed to be given up on.
What to measure
Look for consistency rather than volume — the share of users whose sessions cluster in a stable window, and how that share grows over weeks. The proof that a context cue has taken hold is retention that survives switching notifications off.
Frequently asked questions
What is an implicit prompt?
An implicit prompt is a cue in the user's environment — a place, a time, a preceding action or an emotion — that triggers a behaviour without any message from the product. It is the endpoint of habit formation: the routine itself now does the prompting, so the product no longer has to.
How do you build a habit into a product?
Attach the behaviour to a cue the user already encounters reliably, rather than trying to create a new one. Ask when and where they will do it, anchor it to an existing routine, and reduce explicit reminders as the association strengthens. Cue stability matters more than motivation.
What is an implementation intention?
It is a plan that specifies when and where an action will happen, studied extensively by Peter Gollwitzer. Stating 'I will do X after Y' substantially raises follow-through compared with intending to do X in general, because it delegates the triggering to the environment instead of to willpower.
What is the difference between implicit and explicit prompts?
Explicit prompts come from the product and carry the instruction inside them — a notification, a button, an email. Implicit prompts come from the user's context and require no message at all. Products usually start with explicit prompts and succeed when the behaviour transfers to an implicit one.
Implicit Prompt in a real redesign
- UX case study: onboarding redesign for a plant & botanical shop
Turned a signup form into meeting a companion: the plant gets a personality and a name before it asks the customer for anything.
Related skills
Source: Growth.Design — B=MAP (Prompt)
Practise Implicit Prompt on a real brief
Quest gives you a client brief that targets this skill and 60 minutes to ship an iteration.