The Fogg Behavior Model (B=MAP): A Product Research Guide

The Fogg Behavior Model, in One Sentence

A behavior happens only when three things converge at the same instant: Motivation (the person wants to do it), Ability (it's easy enough to do), and a Prompt (something tells them to do it now). Written as a formula: B = MAP. It is a product — not a sum — so if any one element drops to zero, the behavior does not happen, no matter how strong the other two are.

The model was created by Stanford researcher Dr. BJ Fogg, founder of the Behavior Design Lab and author of Tiny Habits. For product teams, B=MAP is the most practical diagnostic in behavioral design: when a user doesn't do something — doesn't activate, doesn't upgrade, doesn't return — the model tells you exactly which of the three ingredients was missing.

"For a behavior to occur, three elements must converge at the same moment: Motivation, Ability, and a Prompt. When a behavior does not occur, at least one of those three elements is missing." — Dr. BJ Fogg, founder of the Stanford Behavior Design Lab

Key Takeaways

• Behavior = Motivation x Ability x Prompt. It's a product, so if any one element is zero, the behavior does not happen.
• Motivation is the volatile lever. Raising ability — removing friction — is usually faster and more durable than trying to make people want it more.
• Match the prompt to the gap: Spark when motivation is low, Facilitator when ability is low, Signal when both are present.
• The action line turns "low engagement" into a specific diagnosis of which ingredient is missing.
• Users rarely volunteer which element failed — adaptive interviews separate motivation, ability, and prompt so you fix the right thing.

---

Why B=MAP Beats "Just Motivate Users More"

Most teams try to fix weak engagement by pumping up motivation — bigger value props, louder marketing, more persuasive copy. Fogg's research shows this is usually the wrong lever, because motivation is unreliable and fluctuates over time. The durable move is to increase ability — to make the target behavior so easy it happens even when motivation is low.

The stakes are concrete. The typical mobile app loses 70–80% of its users within 30 days of install (enable3), and a huge share of that loss is a B=MAP failure: users who wanted the outcome (motivation) but hit too much friction (low ability) or never got prompted at the right moment (no prompt). Day 1 retention, in particular, "shows whether onboarding and the first experience clicked" — which is a direct test of whether your activation behavior cleared the action line.

"People change best by feeling good, not by feeling bad." — Dr. BJ Fogg, Tiny Habits

---

The Three Elements

1. Motivation

How much the person wants to perform the behavior. Fogg describes three core motivators: sensation (pleasure/pain), anticipation (hope/fear), and belonging (acceptance/rejection). Motivation is powerful but volatile — you cannot rely on it being high at the moment you need the behavior.

2. Ability

How easy the behavior is to do. Fogg breaks ability into factors of simplicity: time, money, physical effort, mental effort (brain cycles), social deviance, and routine. The fastest way to raise ability is to remove steps. Making a behavior easier is almost always more effective than trying to make people want it more.

3. Prompt

The cue that says "do it now." Fogg defines three prompt types based on where the user sits relative to the action line:

• Spark — pairs the prompt with a motivator, for users with high ability but low motivation.
• Facilitator — pairs the prompt with something that makes the behavior easier, for users with high motivation but low ability.
• Signal — a simple reminder, for users who already have both motivation and ability and just need a nudge.

The right prompt depends entirely on which ingredient is short. Sending a "signal" reminder to a user who lacks ability just annoys them.

---

The Action Line: A Diagnostic Tool

Fogg plots Motivation (vertical) against Ability (horizontal). A curved action line separates behaviors that happen from behaviors that don't. Above the line, a prompt succeeds; below it, the same prompt fails. This gives product teams a precise diagnosis:

• Behavior failing and user has high motivation, low ability → simplify the task (Facilitator).
• Behavior failing and user has high ability, low motivation → connect it to a motivator (Spark).
• Behavior failing and user has both → fix the prompt: timing, channel, or clarity (Signal).

The model's power is that "low engagement" stops being a vague problem and becomes a specific, testable one.

---

How to Research Motivation, Ability, and Prompts

B=MAP is a diagnosis, but you can only diagnose if you know which element was missing — and that requires asking users. For each element there is a question only a customer can answer:

• Motivation: "How much did you actually want to do this? What were you hoping would happen?"
• Ability: "What made it hard? Where did you hesitate or give up?"
• Prompt: "Did anything tell you to do this? Was it the right moment?"

The critical insight is that users rarely volunteer which ingredient failed — they say "I just didn't get around to it." Getting to the real cause takes follow-up probing, which is why static surveys consistently miss it.

---

The Modern Approach: Diagnosing B=MAP with AI Interviews

Koji is purpose-built for this kind of behavioral diagnosis. Its AI-moderated interviews — over voice or text — adaptively separate motivation from ability from prompt in a single conversation. When a user says "I didn't finish setup," Koji's AI automatically probes the real cause: "What stopped you — were you not sure it was worth it, or was it too much effort, or did you just forget?" That one follow-up maps directly onto M, A, and P. You can configure a custom AI consultant to run every interview as a behavior-design diagnostic.

Where a traditional survey tool like SurveyMonkey gives you a flat "why didn't you complete onboarding?" with a fixed answer list, Koji discovers the true blocker from the conversation and confirms it with a follow-up. Running hundreds of these in parallel with automatic thematic analysis reveals whether your activation problem is systematically a motivation gap, an ability gap, or a prompt gap — the difference between three completely different fixes. Real-time reporting delivers that in minutes, and teams using AI-assisted research report dramatically faster time-to-insight — no behavioral-science PhD required.

Koji's six structured question types quantify each element:

• scale to measure motivation intensity and perceived difficulty
• single_choice to isolate the dominant blocker (motivation, ability, or prompt)
• open_ended to capture the story behind the friction
• multiple_choice to tag which ability factors (time, effort, cost) applied
• ranking to order which simplicity factors matter most
• yes_no to confirm whether a prompt was received at the right moment

See the structured questions guide for combining these in one study.

---

Real-World Examples of B=MAP

• Amazon 1-Click. A pure ability play. Motivation to buy already exists; Amazon collapsed checkout to a single tap, removing the friction (time, mental effort) that pushed the purchase behavior below the action line.
• Duolingo streak reminders. A prompt play with precise timing. Users have motivation and ability; the model's job is a well-timed Signal prompt that fires at the moment they're most likely to act.
• Onboarding step reduction. Cutting a 9-field signup to 3 fields raises ability — the classic fix when users clearly want the product (high motivation) but drop off (low ability).
• Couch to 5K. A motivation-and-ability design: it lowers the bar so far ("just run for 60 seconds") that the behavior clears the action line even on low-motivation days, exactly as Fogg's Tiny Habits prescribes.

Each example fixes a different ingredient. The discipline B=MAP enforces is identifying which one is missing before you build the fix — because shipping a motivation campaign when the real problem is friction wastes the cycle.

Fogg vs. the Hooked Model

The two frameworks are complementary, not competing. The Hooked Model describes the loop that builds a habit over many repetitions (Trigger → Action → Variable Reward → Investment). B=MAP describes what has to be true for each single instance of the behavior to happen at all. In practice: use B=MAP to get the individual action across the action line, then use the Hook Model to turn that repeated action into an automatic habit.

---

Common Mistakes

• Defaulting to motivation. It's the volatile lever. Increasing ability (removing friction) is usually faster and more durable.
• Prompting at the wrong moment. A perfect prompt sent when ability is low just creates frustration.
• Treating "low engagement" as one problem. It's three different problems with three different fixes; you have to diagnose which.
• Guessing the blocker. Whether the missing ingredient was M, A, or P is an empirical question — ask users, don't assume.

---

Related Resources

• The Hooked Model: Building Habit-Forming Products — turn a single behavior into a habit loop
• User Onboarding Research — diagnose activation as a B=MAP problem
• The Aha Moment: Researching First Value — get users across the action line to first value
• Customer Retention Research — find which ingredient is missing for churned users
• Customer Effort Score Guide — measure the ability/effort dimension
• Structured Questions Guide — quantify motivation, ability, and prompts