IX Coach

The Fogg Behavior Model, Made Practical

Motivation, ability, and prompt — diagnosing exactly what’s blocking behavior

How does BJ Fogg’s behavior model explain habits?

The Fogg Behavior Model is B = MAP: a behavior happens only when Motivation, Ability, and a Prompt arrive at the same moment. If a behavior is not happening, at least one of the three is missing — and which one tells you what to change, because high motivation cannot compensate for a behavior that is too hard or a prompt that never fires. Stanford behavior scientist BJ Fogg developed it as a practitioner framework: its parts rest on established cue and reinforcement research, but the MAP formulation itself has not been tested as a whole in controlled trials.

BJ Fogg, a behavior scientist at Stanford, built this model after noticing that most behavior change advice fails because it diagnoses the wrong bottleneck. If ability is low, adding more motivation won’t help. If there’s no prompt, neither motivation nor ability matter. The Fogg Behavior Model gives you a diagnostic framework to identify the actual gap rather than defaulting to more willpower.

Practices

How these practices connect

Every practice on this page is a way of managing the same equation: a behavior only fires when motivation, ability, and a prompt are all above threshold at the same instant. Because that convergence is fragile and none of the three elements is fixed, the practices split into two jobs — diagnosing which element is actually failing, and then engineering the more controllable elements (ability and prompt) so the behavior no longer depends on motivation staying high. Celebration closes the loop by wiring the successful instance into a habit so the diagnosis has to happen less often over time.

Is this the same thing as the action line, or something different?

They describe the same threshold from two angles. Behavior diagnosis (behavior-diagnosis) is the practical checklist you run when a behavior isn't happening — is it motivation, ability, or the prompt that's missing. The action line (action-line) is the underlying curve that diagnosis is checking against: the point where motivation times ability crosses high enough, given a prompt, for the behavior to occur. Diagnosis is the troubleshooting step; the action line is the model of what you're troubleshooting.

Why does lowering difficulty work better than trying to get more motivated?

Because motivation and ability trade off on the same action line, but they aren't equally controllable. Ability calibration (ability-calibration) argues you can directly reduce how much a behavior demands by matching it to your worst days rather than your best ones, which moves the action line down in a way you can engineer on purpose. Motivation, by contrast, arrives in waves you don't control (motivation-wave) — you can time around it, but you can't manufacture it at will. Tiny behavior design (tiny-behavior-design) takes this to its logical endpoint: shrink the behavior until the ability requirement is so low the action line sits below almost any motivation state, including bad days.

What should I actually do when I feel really motivated?

Don't just use the motivation to push through a hard version of the behavior once — use it to change the system so future attempts need less motivation. The motivation-wave practice specifically prescribes spending a motivation spike on redesigning the prompt and lowering the ability requirement, not on a single heroic performance. Ability calibration and tiny behavior design are what that redesign looks like in practice: a high-motivation moment is when you set the easier version up, so that on an average or bad day the behavior can still fire without needing that same motivation to return.

Do I need a reminder or notification for this to work?

You need a prompt, but a phone notification is one of the least durable ways to provide it. Prompt design (prompt-design) distinguishes person-internal prompts like hunger or fatigue, contextual prompts tied to a stable environment, and external prompts like notifications — and notifications specifically decay in salience within days as they become background noise. Tiny behavior design gets around this partly by anchoring the tiny version to an existing routine as its trigger, which functions as a more durable contextual prompt than an app reminder.

Why do I keep failing at the same habit even though I care about it?

Caring about it is motivation, and motivation is usually not the actual bottleneck — which is exactly the mistake behavior diagnosis warns against: treating low motivation as the problem when the real issue is that the behavior is calibrated to a best-case day, or that no reliable prompt exists at the moment you're capable of acting. Ability calibration explains why a habit that worked Monday can fail Friday with no change in commitment: ability varies with stress, time, and competing demands, so a fixed-difficulty habit is inconsistent by design, not because willpower dropped.

Does celebrating after a habit actually make a difference, or is that just motivational fluff?

It's doing mechanistic work, not just morale-boosting: shine-celebration identifies immediate positive emotion right after a behavior as the signal that wires it into long-term habit, which lines up with how reinforcement learning encodes behaviors followed closely by positive affect. The catch is timing — celebrating at the end of a week rather than right after each instance is dramatically less effective, because the reinforcement has to be immediate to attach to that specific repetition. This is also why tiny behavior design pairs naturally with celebration: a behavior small enough to complete in seconds leaves room to celebrate immediately, every time, rather than only after a rare big win.

Do you have to follow these steps in order, or can you start anywhere?

There's a natural entry point, but it's diagnostic rather than sequential. Behavior diagnosis is where you start any time a behavior isn't happening, because it tells you which of the other practices actually applies — if the prompt is missing, prompt design is the fix; if the behavior is too hard on a bad day, ability calibration or tiny behavior design is the fix; if motivation is the honest bottleneck, motivation-wave is about timing your effort rather than forcing it. The action line is the shared reference point all of this maps onto, and shine-celebration is what you do after the behavior fires, regardless of which element you had to fix to get there.

How do you choose between these?

Start with behavior diagnosis whenever a behavior isn't happening at all — that tells you which lever is actually broken before you spend effort on the wrong one. If the behavior happens sometimes but not reliably, check ability calibration first, since inconsistent execution is usually a sign the behavior is sized for a good day rather than an average one. If motivation genuinely feels like the gap, don't try to sustain it — use motivation-wave timing to spend a high-motivation moment redesigning the prompt or shrinking the behavior via tiny behavior design, so less motivation is needed going forward. Once the behavior is firing at all, however small, shine-celebration is what converts that single instance into a repeatable habit, so it belongs in every cycle rather than being optional.

What these approaches do not settle

These practices are mechanistically coherent and drawn from a widely used practitioner framework, but several of the strongest-sounding claims are not backed by comparative trials: the specific action line curve and the MAP formulation are tools for intuition and diagnosis rather than precisely measured constructs, and the Tiny Habits method has not been tested in large-scale RCTs against other behavior-change approaches. The ability-calibration rationale sometimes gets attributed to ego depletion, but a large preregistered replication of that mechanism failed, so the recommendation to design for low-resource states stands on its practical track record more than on a settled causal explanation. Similarly, self-generated celebration is Fogg's practitioner insight about sufficient reinforcement, not an established finding on whether self-celebration alone matches externally delivered reinforcement.

Practice this with IX Coach

Practice this with IX Coach

Frequently asked questions

How does BJ Fogg’s behavior model explain habits?

The Fogg Behavior Model is B = MAP: a behavior happens only when Motivation, Ability, and a Prompt arrive at the same moment. If a behavior is not happening, at least one of the three is missing — and which one tells you what to change, because high motivation cannot compensate for a behavior that is too hard or a prompt that never fires. Stanford behavior scientist BJ Fogg developed it as a practitioner framework: its parts rest on established cue and reinforcement research, but the MAP formulation itself has not been tested as a whole in controlled trials.

Diagnose which element: how do you motivation, ability, or prompt — is the bottleneck?

The model represents behavior as B = MAP: Behavior occurs when Motivation, Ability, and Prompt are all above threshold at the same moment. If any single element is missing, the behavior doesn’t fire, no matter how strong the other two are. This diagnostic logic prevents the most common failure in behavior change: treating low motivation as the problem when the real issue is excessive difficulty or a missing prompt.

How do you install a reliable prompt at the right moment?

Prompts function as contextual cues that bring a behavior to attention at the moment when the person is positioned to act. Without a prompt, even highly motivated and capable people simply forget or allow other behaviors to fill the slot. The Fogg model distinguishes person-internal prompts (hunger, fatigue), contextual prompts (environmental cues), and external prompts (notifications, reminders), each with different reliability profiles.

How do you calibrate the behavior to current ability, not future aspirations?

Ability in the Fogg model is not fixed — it varies with time of day, stress, physical state, and competing demands. A behavior that is easy in the morning may be impossible at 10 PM. Designing for average-resource moments rather than peak ones ensures the behavior can be executed even on hard days, which is where consistency is actually built or broken.

How do you surf motivation waves rather than engineering baseline motivation?

Motivation fluctuates in waves driven by biological rhythms, emotional states, and external events. Trying to maintain high motivation as a baseline is exhausting and ultimately fails. The Fogg model prescribes a different use of motivation spikes: use them to set up prompts and reduce the difficulty of behaviors so you need less motivation to execute them reliably.

How do you celebrate immediately after each behavior with a felt sense of success?

Fogg identifies "Shine" — a genuine felt sense of positive emotion immediately after a behavior — as the signal that wires the behavior into long-term habit. The emotion doesn’t have to be large; it must be immediate and genuine. This aligns with reinforcement learning mechanisms: behaviors followed immediately by positive affect become encoded in procedural memory more quickly and durably than behaviors without affective reinforcement.

How do you understand the action line — the threshold where behavior fires?

The Fogg model positions behaviors on a curve: high motivation can compensate for lower ability, and vice versa. The "action line" is the threshold that must be crossed for a behavior to occur given a prompt. The key design insight is that lowering difficulty moves the action line down — making it easier to cross even when motivation is low — which is far more controllable than raising motivation.

How do you design the tiny version of any behavior first?

Tiny behaviors lower the ability requirement so radically that the action line is almost always below the available motivation, even on bad days. This produces consistent execution, which — through repetition and celebration — builds the automaticity and self-efficacy that eventually support the full behavior. The tiny version is not a consolation prize; it is the mechanism through which the full habit is eventually achieved.

Is this the same thing as the action line, or something different?

They describe the same threshold from two angles. Behavior diagnosis (behavior-diagnosis) is the practical checklist you run when a behavior isn't happening — is it motivation, ability, or the prompt that's missing. The action line (action-line) is the underlying curve that diagnosis is checking against: the point where motivation times ability crosses high enough, given a prompt, for the behavior to occur. Diagnosis is the troubleshooting step; the action line is the model of what you're troubleshooting.

Why does lowering difficulty work better than trying to get more motivated?

Because motivation and ability trade off on the same action line, but they aren't equally controllable. Ability calibration (ability-calibration) argues you can directly reduce how much a behavior demands by matching it to your worst days rather than your best ones, which moves the action line down in a way you can engineer on purpose. Motivation, by contrast, arrives in waves you don't control (motivation-wave) — you can time around it, but you can't manufacture it at will. Tiny behavior design (tiny-behavior-design) takes this to its logical endpoint: shrink the behavior until the ability requirement is so low the action line sits below almost any motivation state, including bad days.

What should I actually do when I feel really motivated?

Don't just use the motivation to push through a hard version of the behavior once — use it to change the system so future attempts need less motivation. The motivation-wave practice specifically prescribes spending a motivation spike on redesigning the prompt and lowering the ability requirement, not on a single heroic performance. Ability calibration and tiny behavior design are what that redesign looks like in practice: a high-motivation moment is when you set the easier version up, so that on an average or bad day the behavior can still fire without needing that same motivation to return.

Do I need a reminder or notification for this to work?

You need a prompt, but a phone notification is one of the least durable ways to provide it. Prompt design (prompt-design) distinguishes person-internal prompts like hunger or fatigue, contextual prompts tied to a stable environment, and external prompts like notifications — and notifications specifically decay in salience within days as they become background noise. Tiny behavior design gets around this partly by anchoring the tiny version to an existing routine as its trigger, which functions as a more durable contextual prompt than an app reminder.

Why do I keep failing at the same habit even though I care about it?

Caring about it is motivation, and motivation is usually not the actual bottleneck — which is exactly the mistake behavior diagnosis warns against: treating low motivation as the problem when the real issue is that the behavior is calibrated to a best-case day, or that no reliable prompt exists at the moment you're capable of acting. Ability calibration explains why a habit that worked Monday can fail Friday with no change in commitment: ability varies with stress, time, and competing demands, so a fixed-difficulty habit is inconsistent by design, not because willpower dropped.

Does celebrating after a habit actually make a difference, or is that just motivational fluff?

It's doing mechanistic work, not just morale-boosting: shine-celebration identifies immediate positive emotion right after a behavior as the signal that wires it into long-term habit, which lines up with how reinforcement learning encodes behaviors followed closely by positive affect. The catch is timing — celebrating at the end of a week rather than right after each instance is dramatically less effective, because the reinforcement has to be immediate to attach to that specific repetition. This is also why tiny behavior design pairs naturally with celebration: a behavior small enough to complete in seconds leaves room to celebrate immediately, every time, rather than only after a rare big win.

Do you have to follow these steps in order, or can you start anywhere?

There's a natural entry point, but it's diagnostic rather than sequential. Behavior diagnosis is where you start any time a behavior isn't happening, because it tells you which of the other practices actually applies — if the prompt is missing, prompt design is the fix; if the behavior is too hard on a bad day, ability calibration or tiny behavior design is the fix; if motivation is the honest bottleneck, motivation-wave is about timing your effort rather than forcing it. The action line is the shared reference point all of this maps onto, and shine-celebration is what you do after the behavior fires, regardless of which element you had to fix to get there.

Research

  • Wood & Neal (2007), "A new look at habits and the habit-goal interface", Psychological Review About this work
  • Skinner (1938), The Behavior of Organisms (foundational operant conditioning; immediate reinforcement vs delayed) About this work
  • Bandura (1977), "Self-efficacy: Toward a unifying theory of behavioral change", Psychological Review (mastery experiences) About this work

Related concepts

Articles that cover this

How this pairs with other practices