← Skills library

Behaviour (Fogg B=MAP)

Anticipation

Seeking hope, avoiding fear

What it is

Anticipation is the motivation lever of hope and fear — what's coming, what could be gained, what could be lost. The clearer the imagined future state, the stronger the pull.

Why it works

In BJ Fogg''s Behavior Model, behaviour happens when Motivation, Ability and a Prompt converge at the same moment. Anticipation is one of the three motivation levers — the pull of hope and the push of fear, both oriented toward a future state. What makes it operate is vividness rather than magnitude. A future the user can picture in concrete detail exerts force; an abstract benefit does not, because there is nothing for the imagination to hold. Loss aversion means the fear side is typically stronger than the hope side for an equivalent stake, but it is also more fragile — fear that turns out to be unfounded costs credibility, while hope that is met builds it. This is why anticipation is best built by making the future specific and then delivering exactly what was pictured.

How to apply it in design

Frame the action around a vividly imagined future state (better, finished, safe) or a vividly imagined loss (missing out, falling behind). Specificity creates anticipation; vagueness kills it.

Where you'll see it

  • A concrete picture of the after state rather than a list of benefits
  • Countdowns to something whose contents are already partly revealed
  • Progressive reveals that build a mental image before launch
  • Preview of the actual output the user will get, using their own inputs
  • Naming the specific cost of not acting, in units the user recognises

Example

A music drop countdown with the band's voice notes leaking on Instagram builds anticipation no static landing page can match — the future becomes textured.

Failure mode

"Sign up to be notified" with no clear image of what's coming generates no anticipation. The user has nothing to picture.

When not to use it

Anticipation is wasted on immediate, low-consideration actions — nobody needs to imagine a future state before clicking a search result. It also collapses when the wait is longer than the interest: a countdown running for six weeks trains people to stop looking. Avoid the fear side entirely in categories where the user is already anxious, such as health and money, where amplifying worry to drive action is both ineffective and unkind. And never build anticipation you cannot satisfy; the gap between the pictured future and the delivered one is where churn comes from.

The ethical line

Manufactured fear is the abuse here — inventing a risk, exaggerating a consequence, or implying a deadline that does not exist in order to move someone. It works in the short term and it is corrosive, because the user eventually discovers the threat was not real. The hope side has a quieter equivalent: promising a future state the product cannot deliver. Both fail the same test — would the user, knowing what actually happens next, feel the anticipation you built was honest? Build the picture out of things that are going to be true.

What to measure

Track waitlist-to-activation conversion rather than waitlist size, and measure how many people return during the wait without being prompted. For launches, the honest signal is what proportion of those who anticipated actually showed up.

Frequently asked questions

What is anticipation in the Fogg Behavior Model?

Anticipation is one of the three motivation levers in BJ Fogg's B=MAP model, covering hope and fear — motivation drawn from an imagined future gain or loss. Its strength depends on how vividly the user can picture that future, which is why concrete, specific imagery outperforms abstract benefit statements.

Is fear or hope more motivating in product design?

Fear is generally stronger for an equivalent stake, because losses loom larger than gains. It is also riskier: unfounded fear damages trust permanently once discovered, while hope that is met compounds it. Most durable products lead with hope and use loss framing sparingly.

How do you build anticipation for a launch?

Give people something specific to picture and reveal it progressively rather than all at once. Partial reveals, real artefacts and a fixed date work better than a generic 'coming soon', because anticipation needs raw material for the imagination to work on.

Why do long countdowns stop working?

Because attention decays faster than the timer. A countdown longer than the audience's interest window trains people to stop checking, and by the time it expires the anticipation has dissipated. Shorter windows with more reveals sustain attention better than one long wait.

Anticipation in a real redesign

Related skills

Source: Growth.Design — B=MAP (Motivation)

Practise Anticipation on a real brief

Quest gives you a client brief that targets this skill and 60 minutes to ship an iteration.