Fogg Behavior Model: Motivation, Ability, and Prompt

What does the model say?

BJ Fogg, who founded the Behavior Design Lab at Stanford University, presents the model as the foundation of what he calls Fogg Behavior Design. The central idea is practical: for someone to do something, they need to want to do it, be able to do it, and be reminded to start at that moment.

The simplest form of the model is B=MAP. The B is the behavior. The M is motivation, the A is ability, and the P is the prompt. Fogg presents it as a convergence: all three must come together at the same moment, and if the behavior does not happen, at least one of them is missing.

Why does this matter for a junior designer?

Because when a product fails to get people to do something, the usual response is to add a reminder or a notification. Fogg suggests a more useful question: what is missing? Perhaps people lack motivation, the action is too hard, or nobody asked them to do it at the right moment.

That question changes the solution. A reminder does not fix a hard action, and a simple action does not fix a lack of motivation. Diagnosing which of the three factors fails is the first step in behavior design.

How do you design for motivation?

Fogg describes motivation with three pairs of opposing forces:

• Sensation: pleasure versus pain.
• Anticipation: hope versus fear.
• Belonging: acceptance versus rejection.

For a designer, this suggests concrete questions. What does the user feel when they finish the task? What do they expect to happen next? Do they want to feel part of a group? Motivation cannot be manufactured with a screen, but design can show the benefit, reduce the fear of making a mistake, or give a sense of progress.

Fogg also notes that motivation and ability trade off: when one is high, the other can be lower and the behavior still happens. That explains why an easy action can happen even with low motivation.

How do you design for ability?

Fogg ties ability to simplicity: simplicity depends on a person’s scarcest resource at that moment. The official site gives two examples, time and money: a ten-minute behavior is not simple if you do not have ten minutes. It proposes three ways to increase ability: train people (the hard path, best avoided unless necessary), give them tools or resources, and scale back the target behavior.

To design ability, ask which resource is missing. If the user has little time, reduce the steps. If they have little attention, remove unnecessary text. If the action requires leaving their routine, find a way to do it within what they already do (these applications are this wiki’s judgment).

This is where the model is most practically useful. Hick’s law and interaction cost describe how each extra decision uses up the user’s capacity, using a different framework.

How do you design the prompt?

The prompt is what reminds the user to act at that moment. Fogg distinguishes three kinds of prompts: facilitator, signal, and spark. The official site mainly develops the facilitator, with the example of a prominent sign-in button that makes the behavior easy; signal and spark are only named. The page sums it up this way: without a prompt, the behavior will not happen.

A prompt works best when it appears at the moment the user already has motivation and ability. A reminder that arrives when the person cannot act becomes an annoyance.

When should you NOT apply the model?

• When the behavior depends on long-term automatic habits. According to the Halonen critique cited below, Fogg’s model treats each behavior as a moment of convergence, and sustained change needs more than that.
• When the problem is structural. If the environment blocks the behavior, through a rule, a price, or a lack of access, no prompt will solve it.
• When the goal is to manipulate. The model explains how to make an action easier, but it does not justify using motivation against the user. That boundary is covered in the article on dark patterns.

A critique by Elina Halonen (blog Thinking About Behavior, October 2024) compares the Fogg model with COM-B. It argues that Fogg’s model does not separate reflective from automatic motivation, treats ability as immediate simplicity, and that prompts do not change the underlying physical or social context. Its conclusion is that Fogg may get you through the door, while COM-B helps you stay in the game over the long run. It is a conceptual critique without empirical data, and should be read as one.

Example

Illustrative example: a health app wants users to log their blood pressure every morning.

• Diagnosis: users are motivated at first, but drop off in the second week.
• Ability: logging blood pressure takes four screens and writing the time by hand. Ability is low.
• Change: logging is reduced to one tap, with previous values prefilled.
• Prompt: the notification is sent around the time the person usually opens the app in the morning, not at a fixed hour.
• Motivation: a weekly trend is shown, to give a sense of progress.

Each change targets one factor. None asks the user for more motivation than they already have.

For how these decisions are organized, the article on choice architecture shows how the order of options affects behavior without forbidding anything.

Common mistakes

• Answering an ability problem with more reminders.
• Confusing ability with skill: Fogg ties ability to simplicity, and training people is the hard path. An action can be easy for an expert and hard for someone just arriving.
• Sending prompts when the person cannot act.
• Treating the model as a universal law without testing it with users.
• Using fear as motivation without considering the harm it causes.
• Applying the model to a problem of price, access, or policy.

Sources

• BJ Fogg, Fogg Behavior Model
• BJ Fogg, Motivation (Fogg Behavior Model)
• BJ Fogg, Ability (Fogg Behavior Model)
• BJ Fogg, Prompts (Fogg Behavior Model)
• Elina Halonen, Thinking About Behavior, Comparing the Fogg Behavior Model and COM-B (October 22, 2024)