BJ Fogg Behavior Model Explained: B=MAP and the 6 Factors of Ability (Octalysis Extended)

The BJ Fogg Behavior Model states that any behavior — from tapping a notification to quitting smoking — only happens when three ingredients converge at the same instant: Motivation (how much the person wants to do it), Ability (how easy it is to do), and a Prompt (a trigger telling them to do it now). Written as B = MAP, it is one of the most quietly powerful formulas in behavioral design, and it is also one of the most frequently misunderstood.

B=MAP is one entry in a much bigger toolkit. I catalog Fogg’s model alongside every other framework I use in client work inside my Behavioral Framework Library, including the theories that pick up where the prompt leaves off. If you want to see how they all fit together, start there.

Most designers treat the Fogg Behavior Model as a to-do list: crank up motivation, reduce friction, fire a notification. Ship. Done. But in twenty years of designing behavior-change systems for LEGO, Microsoft, Porsche, Coca-Cola, Salesforce, and MrBeast, I have watched teams spend months trying to boost motivation when the real problem was that their Prompt was landing at the wrong emotional moment — or that their feature was more complicated than their users admitted.

Fogg’s model is the correct starting point. It is not the correct ending point. The Three Elements tell you what has to be true for a behavior to fire, but they do not tell you why motivation rises or falls, which factor of ability is broken, or which kind of prompt your user actually needs right now. That is where the model stops and the real work begins.

This guide unpacks the Fogg Behavior Model at expert depth — the three elements, the six factors of ability most people never read about, the three types of prompts, where the model breaks in practice, how it compares to the Hook Model and COM-B, the neuroscience underneath it, and how I use it day-to-day inside the Octalysis Framework to decide which of the eight Core Drives to pull.

Author Credibility: Yu-kai Chou

Yu-kai Chou created the Octalysis Framework after studying gamification since 2003 — years before the term entered mainstream vocabulary. As a Human-Systems Architect & Behavioral Designer, his framework has been applied by LEGO, Microsoft, Porsche, Coca-Cola, Salesforce, and MrBeast, impacting over 1.5 Billion Users.

Chou has taught the Octalysis methodology at Harvard, Stanford, Yale, Tesla, Google, BCG, and IDEO.

His work has been cited by Harvard, Stanford, MIT, Forbes, Wall Street Journal, Wired, US Department of Energy, NIST, NSF, NCBI, US Department of Education, ClinicalTrials.gov, and Google Scholar — with 3,700+ more academic publications. Explore his books here.

TEDxLausanne · Gamification to Improve Our World17 min

What Is the BJ Fogg Behavior Model?

The BJ Fogg Behavior Model is a behavioral design framework developed by Stanford researcher Dr. B.J. Fogg, founder of the Stanford Behavior Design Lab, stating that three elements must converge at the same moment for any behavior to occur: Motivation, Ability, and a Prompt. Fogg originally formalized this as B = MAT in the early 2000s, where the “T” stood for Trigger, and later renamed it to B = MAP to reflect that real prompts are richer than mechanical triggers.

Fogg is often introduced as “the father of behavior design,” and the model is taught in nearly every product-management program on earth. His book Tiny Habits popularized the idea that behaviors compound from small, anchored actions, and the model itself has shaped products at Facebook, Instagram, Intuit, and thousands of habit-focused consumer apps. A generation of Silicon Valley designers came out of his Stanford course and built an industry on it.

The model is best understood as a diagnostic formula. If a behavior is not happening, B = MAP gives you three suspects to interrogate: is motivation too low, is the behavior too hard, or did the prompt never land? Most teams jump to motivation and spend months writing better copy. In practice, ability and prompt design are where the easy wins hide.

The formula is also multiplicative, not additive. Motivation × Ability × Prompt means that if any single factor hits zero, the behavior cannot fire, no matter how strong the other two are. A user who is wildly motivated to meditate but cannot find the app icon on a cluttered home screen will not meditate. A user who has perfect ability to tap a subscribe button but whose motivation is zero will not subscribe. And a user who has both motivation and ability but who never sees a prompt at the right moment will simply forget. The model’s elegance is that it forces you to diagnose all three before blaming any one of them.

The Three Elements: B = MAP

The three elements are deceptively simple on the surface and reward very close reading. Fogg deliberately chose the shortest possible names — Motivation, Ability, Prompt — because he wanted the formula to be memorable, not because he thought each word covered everything. Each element is a whole sub-model.

Motivation: How Much the User Wants to Act

Motivation in Fogg’s model is treated as a single axis on the Behavior Graph — high to low — but Fogg identified three core motivators underneath it: sensation (pleasure/pain), anticipation (hope/fear), and belonging (social acceptance/rejection). Each motivator has a positive and a negative pole, so you can push behavior with pleasure or with pain, with hope or with fear, with belonging or with the threat of social rejection.

Two of these motivators are worth staring at. Fogg singled out hope as, in his words, “the most ethical and empowering of the three core motivators.” He also singled out fear — the negative pole of anticipation — as the single most effective lever for driving short-term behavior, and the one most likely to damage the relationship with the user if used repeatedly. A designer who cannot tell the difference between hope-motivated engagement and fear-motivated engagement is a designer who cannot tell the difference between a retention curve that is healthy and one that is quietly burning down.

In my own language, Fogg’s three motivators map onto what I call White Hat and Black Hat motivation in Octalysis. Hope, pleasure, and positive belonging sit on the White Hat side — they make users feel empowered. Fear, pain, and the threat of rejection sit on the Black Hat side — they drive urgent action but leave residue. Both are real, both work. The question is which one your product is quietly running on.

Ability: How Easy It Is to Do

Ability is the axis that product teams consistently under-invest in, because it looks like engineering work instead of design work. Fogg’s core insight here is that ability is not one thing — it is six sub-factors, and the one that is scarcest for your user is the one that matters. If a user has plenty of time but is overloaded with decisions, extra time doesn’t help; Brain Cycles is their real constraint. If a user has unlimited decisions-available but no money, making something cheaper matters more than making it simpler.

Fogg’s rule for ability is “simplicity is a function of your scarcest resource at that moment.” You don’t increase ability by reducing effort in the abstract — you increase it by identifying which of the six factors is in shortest supply for your user right now and removing friction from that one specifically. We will walk through all six in detail below.

Prompt: The Trigger That Tells the User to Act

A prompt is anything that says “do it now.” Push notifications, email subject lines, a friend’s nudge, the sight of a running shoe by the door, a scheduled calendar event — they are all prompts. Fogg originally called this element “Trigger” and later renamed it “Prompt” because “trigger” evoked the idea of a fixed mechanical cue, whereas real prompts are contextual, emotional, and often self-generated.

The non-obvious claim hiding inside the formula is that no behavior happens without a prompt. Even behaviors that seem spontaneous are prompted — by an internal thought, a physical sensation, a change in time-of-day, a piece of environmental design. Nir Eyal’s Hook Model extends Fogg’s prompt idea by distinguishing external triggers from internal triggers, and arguing that habit-forming products are the ones that successfully graft themselves onto a user’s pre-existing emotional triggers. A notification is an external prompt; loneliness leading someone to open Instagram is an internal prompt.

Because prompts have three types — Spark, Facilitator, and Signal — we need to talk about which one to send when, and that requires understanding where the user sits on the motivation-ability graph. I’ll walk through the three types further down.

The Six Factors of Ability

This is the part of Fogg’s work that most product teams have never read carefully, and it is where I spend most of my diagnostic time when a client’s behavior is not firing. Ability, per Fogg, is a function of the scarcest of six resources at the moment of decision. They are:

1. Time

If a behavior takes more time than the user has available, ability is low, regardless of how simple the action is in the abstract. A five-minute meditation is “easy” at 9pm on a quiet Sunday and “impossible” at 8:47am on a Tuesday with a toddler screaming. This is why meditation apps that work win not by cutting motion complexity but by offering a 60-second version — they compress the action into the time the user actually has.

When Time is the scarce factor, product fixes look like: shorter sessions, background processing so the user doesn’t wait, scheduling-aware prompts (“we noticed you usually have 4 minutes free at 7:30am”), and ruthless removal of anything the user has to read before acting.

2. Money

If an action costs money and the user does not have it, ability is zero. Obvious. The non-obvious part is that Money-scarcity is not only financial — a free action that requires an accompanying paid action (a “free app” that gates the real feature behind a subscription, a “free trial” that requires a credit card) is also gated by money. Users who cannot produce money at the moment of decision will not complete the behavior, even if they want to.

Money-scarce products need free tiers that are genuinely useful, not crippled-trial tiers that break at the moment of value.

3. Physical Effort

If the behavior requires physical exertion the user cannot or will not expend, ability drops. This is the sub-factor product teams over-index on — cutting clicks, shortening forms, removing steps — because it is the most measurable. Physical effort matters, but it is rarely the real constraint for a digital behavior.

For physical behaviors (exercise, cooking, leaving the house), Physical Effort is obviously load-bearing. The behavioral design trick is anchoring: attaching a new physical behavior to a movement the user is already making, so the marginal physical effort is nearly zero. Doing two push-ups after brushing your teeth is the archetypal Fogg-style “tiny habit” — zero friction because it rides on an existing motion.

4. Brain Cycles

Brain Cycles is the factor almost every product team ignores, and it is almost always the real constraint for a new-user onboarding flow. If a behavior requires the user to think, choose, weigh, or decide, and their cognitive bandwidth is already full, they will not complete the behavior even if it takes no time and no money and one click.

“Free” decisions are expensive. Every dropdown, every branching question, every “which plan is right for you?” interrupt forces the user to spin cycles they don’t have. The cure is not always fewer options; it is defaults that are correct 80% of the time and visible edit-later escape hatches. The user’s brain gets to say “yes, proceed” instead of “now I must analyze seventeen variables.”

5. Social Deviance

If the behavior violates the user’s social norms — what their peer group, family, or community expects — ability is reduced, regardless of how easy the action is mechanically. Asking a devout Muslim to set up a meditation practice that uses Christian imagery. Asking an American teenager to post publicly on a platform their friends don’t use. Asking a corporate VP to publicly endorse an experimental productivity tool. The mechanics are trivial. The social cost is high.

Product designs solve Social Deviance with private modes, anonymous defaults, peer-group confirmation (“12 of your colleagues are already using this”), and features that let users signal adoption after trying — never before.

6. Non-Routine

If the behavior falls outside the user’s existing routines, ability drops. A task that is objectively simple (“open an app you’ve opened a thousand times”) is trivially easy. The same task, when it requires the user to break an established pattern (“open a new app at a new time”), is several orders of magnitude harder. Routine is a cognitive and emotional groove, and carving a new one takes disproportionate effort.

This is why habit-stacking works and why most behavior-change products under-design for it. You cannot drop a new behavior into a user’s life as a free-floating event; you have to anchor it to an existing behavior the user already does every day. BJ Fogg’s Tiny Habits method is essentially an operationalization of this single insight: find the user’s existing routine, graft the new behavior onto it, shrink the new behavior until it is comically small, and let routine do the rest of the work.

The Three Types of Prompts

Fogg’s most under-taught insight is that prompts are not interchangeable. There are three types, and which one works depends on where the user already sits on the Motivation-Ability graph at the moment the prompt fires. Most product teams send one type of prompt — usually a Signal — and then wonder why conversion is flat. The prompt doesn’t fail; the type of prompt fails.

Spark: Add Motivation When Ability Is High

A Spark is a prompt that adds motivation. It is the right prompt for a user who has high ability but low motivation. They can act, but they don’t want to yet. A Spark’s job is to give them a reason.

“Your friend just beat your high score” is a Spark. “Only 3 left in stock” is a Spark. “You’ll lose your 47-day streak if you don’t log in today” is a Spark — a fear-based one. Every Spark activates one of Fogg’s three core motivators (sensation, anticipation, belonging) and pushes the user up the motivation axis just high enough to clear the action line. Well-designed Sparks fire rarely, at high-value moments, and use the gentlest motivator that will work.

Facilitator: Remove Friction When Motivation Is High

A Facilitator is a prompt that removes ability friction. It is the right prompt for a user who has high motivation but low ability. They want to act, but something is in the way.

“Tap here and we’ll pre-fill your info” is a Facilitator. “One-click checkout with Apple Pay” is a Facilitator. “We noticed you started drafting this post 3 days ago — resume where you left off?” is a Facilitator. The user is already motivated; the prompt’s job is to collapse the remaining ability cost to near-zero. Facilitators almost always beat Sparks in mature products, because mature products have already sold the user on motivation and the residual drop-off is pure friction.

Signal: Fire When Motivation and Ability Are Both Above the Action Line

A Signal is a prompt that simply says “now is the time.” It assumes motivation and ability are both already high enough to act — the user just needs to be reminded. A calendar alert, a red badge on an app icon, a “reminder” email sent at the scheduled time. Signals are the cheapest prompt to design and the one most products over-use.

The failure mode is obvious: if motivation or ability is below the action line, a Signal does nothing except teach the user to ignore your prompts. This is how notification fatigue happens. Teams diagnose the problem as “users ignore our notifications” and respond by sending more Signals, when what they actually needed was to send fewer Signals and more Sparks or Facilitators at moments where those would have helped.

Where the Fogg Model Falls Apart

The Fogg Behavior Model is a brilliant formula, and it is also incomplete. The places where it falls apart in the real world are predictable and worth knowing before you bet a product on it.

Motivation Is Treated as a Single Bucket

The most important critique of the Fogg model is that it treats motivation as one slider from “low” to “high” — but motivation has a shape. A user can be highly motivated by social comparison (Core Drive 5) and completely unmoved by epic meaning (Core Drive 1). Another user in the same exact situation is the reverse. Fogg’s model will tell you both users need “more motivation,” and it will tell you nothing about which lever to pull. This is why Octalysis exists — to decompose the motivation bucket into eight distinct drives that you can design for individually.

A product that adds “social proof” copy to the checkout and sees no lift may have been targeting the wrong Core Drive all along. Fogg says motivation was too low; Octalysis tells you which kind of motivation was missing.

The Action Line Is a Moving Target

Fogg’s Behavior Graph shows a fixed curve above which behaviors fire and below which they don’t. In practice, that curve is different for every user, different for every time of day, different after a stressful meeting, different after a good night’s sleep. The model gives you no mechanics for state change — a user’s action line can shift by 50% between 3pm and 9pm on the same day, and the same prompt that failed at 3pm succeeds at 9pm without the prompt changing at all.

Teams that don’t account for this end up with reports that say “our campaign converted 2.3% of sends,” when the real insight is “we converted 7% of users we reached after 9pm and 0.8% of users we reached during lunch.” The average hides the real story.

The Model Ignores What Happens After

B = MAP is purely about whether a behavior fires. It says nothing about whether the behavior produces satisfaction, builds a habit, generates regret, or gets abandoned the next day. The full arc of a user’s relationship with a behavior requires a reinforcement loop — something like Skinner’s operant conditioning, or the variable-reward loop in the Hook Model — that Fogg’s formula does not describe.

A prompt can succeed in the moment and fail the user over time. “You’ll lose your streak” fires the behavior, but a user who is grinding through a meditation app because of streak-loss fear is not building a meditation practice — they are building a meditation-app-tolerance. The model does not warn you about this, because the model ends at the moment the behavior fires.

What’s Really Happening Inside the Brain

Underneath Fogg’s three-element formula is a set of neural mechanisms that translate “motivation, ability, and prompt” into actual neurons firing. Understanding the underlying biology turns the model from a checklist into a diagnostic tool.

Motivation lives in the mesolimbic dopamine system. When the prefrontal cortex anticipates a reward — a point, a like, a streak saved, a snack consumed — the ventral tegmental area releases dopamine into the nucleus accumbens. This is what “high motivation” feels like from the inside: a rising prediction of reward. Dopamine is not, as the popular framing has it, the pleasure chemical; it is the wanting chemical. It tells the brain “this is worth doing right now.” A well-designed Spark does not create motivation out of nothing; it recruits the user’s pre-existing dopaminergic prediction by reminding them that a reward is close.

Ability lives in the basal ganglia and the prefrontal cortex. The brain has two parallel systems for acting: a slow, deliberate, effortful system in the prefrontal cortex, and a fast, automatic, cheap system in the basal ganglia. A behavior is “high ability” when it runs on the basal ganglia — when it is a routine, a habit, a compiled skill. A behavior is “low ability” when every execution requires the prefrontal cortex to think it through from scratch. This is why BJ Fogg’s Tiny Habits method — anchor a new behavior to an existing routine, shrink it until it costs almost nothing — works at the neural level: it recruits the basal ganglia as scaffolding for the new habit.

Prompts work by capturing attention through the salience network. The insula and anterior cingulate cortex constantly scan the environment for stimuli that are novel, urgent, or emotionally loaded, and they pull conscious attention toward whichever of those wins. A Signal that does not trigger the salience network — a notification that looks like every other notification — gets filtered out below the level of consciousness. A Spark that exploits fear, scarcity, or social comparison wins the salience contest because those are the stimuli the brain is evolutionarily wired to prioritize. This is why fear-based prompts are so effective and so corrosive: they work, and they teach the salience network to treat your product as a source of threat.

The three-element formula, translated into neuroscience, becomes: dopaminergic prediction × basal-ganglia automaticity × salience capture. When all three fire at the same instant, behavior happens. When any one drops out, it doesn’t. The biology recapitulates the model.

Fogg vs Other Behavior Theories

The Fogg Behavior Model is one of several major behavioral-design frameworks. It is most useful when you understand what it explains better than its rivals, and what its rivals explain better than it does.

Fogg vs Skinner (Operant Conditioning)

B.F. Skinner’s operant conditioning explains behavior as a product of consequences — reinforcement increases the frequency of a behavior, punishment decreases it. Fogg’s model explains behavior as a product of pre-conditions — motivation, ability, and prompt must converge for the behavior to happen at all. The two frameworks answer different questions. Skinner asks: “once a behavior happens, why does it stick?” Fogg asks: “why does the behavior happen in the first place?”

A complete behavioral-design system needs both. Fogg gets the behavior to fire once; Skinner explains what turns a one-time fire into a pattern. This is why products that only design for the first action — the signup, the first session — and ignore the reinforcement schedule that follows end up with high acquisition and high churn. The Fogg-model checklist worked; the Skinner reinforcement loop was missing.

Fogg vs the Hook Model (Nir Eyal)

Nir Eyal’s Hook Model — Trigger, Action, Variable Reward, Investment — is essentially Fogg’s model with a feedback loop welded onto the end. The Trigger and Action stages are a direct simplification of B = MAP. The Variable Reward stage imports Skinner’s variable-ratio reinforcement schedule. The Investment stage adds a commitment-consistency loop that increases future prompt-responsiveness.

The Hook Model is more useful than Fogg’s model for designing habit-forming products, because it explicitly addresses the multi-cycle dynamics that Fogg ignores. Fogg’s model is more useful than the Hook Model for diagnosing why a single specific behavior is not happening right now, because Fogg’s decomposition of ability into six sub-factors is more actionable than the Hook Model’s treatment of ability as a single step.

Fogg vs COM-B (Michie, West & Atkins)

COM-B — Capability, Opportunity, Motivation → Behavior — is the behavior-change framework of choice in public health and clinical psychology. It decomposes behavior into three similar-looking elements, but the decomposition is deeper than Fogg’s: Capability splits into physical and psychological capability; Opportunity splits into physical and social opportunity; Motivation splits into reflective and automatic motivation. That six-way split often catches behavioral determinants that B = MAP misses.

COM-B is better than Fogg for designing population-level health interventions, because it forces the designer to think about social and physical environment separately from individual ability. Fogg is better than COM-B for designing individual product features, because its treatment of the prompt as a distinct third element (COM-B folds “cue” inside “opportunity”) gives clearer guidance to product teams.

Fogg vs Self-Determination Theory

Self-Determination Theory (Ryan and Deci) tells you why motivation exists in a sustained way — the satisfaction of the three basic psychological needs for autonomy, competence, and relatedness. Fogg tells you that motivation either is or is not high enough right now. SDT is upstream of Fogg in the causal chain: SDT explains how a durable motivational baseline is produced; Fogg explains how, at the moment of decision, that baseline either does or does not clear the action line.

A product that runs on SDT without Fogg tends to be conceptually beautiful and operationally inert — users feel good about the product but never actually use it. A product that runs on Fogg without SDT tends to be operationally effective and motivationally hollow — users complete the actions but never internalize them. Both frameworks are necessary.

The Fogg Model in the Real World

The model is most useful when you see it applied to real products and behaviors. Four domains show what “good Fogg-model design” actually looks like in practice.

Product and UX Design

Instagram Stories’ “new story” ring around profile pictures is a Fogg-perfect piece of design. The ring is a Signal (visual novelty in the salience network). The “tap to view” gesture collapses ability to a single touch (Physical Effort = 0, Brain Cycles = 0, Time = 2 seconds). Motivation is pre-supplied by social relatedness — you see people you care about. The ring works because it respects all three elements of B = MAP at once: the prompt is visually unmissable, the ability cost is trivial, and motivation is imported from the social graph.

The same model explains why “generic push notification at 7pm” has a sub-2% engagement rate in most apps. The motivation is not pre-supplied, the ability cost includes switching contexts and orienting to a new surface, and the prompt is visually indistinguishable from every other notification. One element is just barely above the action line, which is enough for two of them to drop the whole behavior below it.

Health and Habit Change

Fogg’s Tiny Habits method is the canonical health-behavior application of the model. Recipe: identify an existing routine the user already performs daily (brushing teeth, sitting down with morning coffee, walking into the office), anchor a new behavior to that routine, and shrink the new behavior to something comically small (one push-up, one page, one deep breath). Ability rides on the pre-existing routine (Non-Routine cost ≈ 0, Physical Effort = trivial, Brain Cycles = 0). The prompt is the anchor-behavior itself. Motivation only needs to exceed the action line for the tiny behavior, which it almost always does.

Clinical behavior-change programs that cite Fogg’s model tend to focus on one sub-factor at a time — a diabetes self-management program might attack Brain Cycles first (automatic reminders, pre-filled logs) and Social Deviance second (peer support groups that make the behavior socially normal). Stepwise Ability fixes tend to outperform motivational campaigns in this domain.

Workplace Behavior

Inside organizations, Fogg’s model explains why “change management” keeps failing. Leaders give rousing speeches (Spark on motivation) and then wonder why the new CRM still isn’t being used. The motivation was pushed above the action line for about three days; then ability friction (Brain Cycles to learn the new tool, Non-Routine cost to break the old habit, Social Deviance cost of being the only person on the new workflow) pulled behavior back below the line. No amount of additional exhortation closes the gap.

Effective workplace behavior change inverts the emphasis. Leaders spend about 20% of effort on motivation-side Sparks — clear “why” framing, visible executive adoption — and about 80% on Ability-side Facilitators: one-click migration tools, pre-populated workflows, peer mentors who absorb Brain Cycles for the team, explicit permission to drop the old workflow so Non-Routine cost disappears. Behavior moves.

Marketing and Conversion

At the top of the conversion funnel, Fogg’s model explains why “we’ll show you an ad and hope they click” rarely works. The ad is a Signal; motivation is low because the user hasn’t been sold yet; ability cost includes context-switching from the page they were on. One element above the action line is not enough. The Fogg-faithful version of the same funnel pre-heats motivation (an article, a case study, social proof) before firing the Signal, and collapses ability (one-click sign-in, pre-filled forms, Apple Pay checkout) to the floor. Conversion multiplies.

The counter-pattern I see in client work is teams adding Sparks on top of Sparks — “hurry, only 3 left!” on top of “last chance!” on top of “500 other people bought this!” — and watching conversion rate flatten. Motivation has a diminishing return; ability friction does not. The conversion mathematics almost always favor a Facilitator over an additional Spark once a baseline motivation is in place.

How to Apply the Fogg Behavior Model with the Octalysis Framework

Fogg tells you that motivation, ability, and prompt must all be present. It does not tell you which motivation to activate, which ability factor is broken, or which prompt will land. That is where Octalysis sits underneath Fogg as the causal engine.

Mapping Fogg’s Motivators to the Eight Core Drives

Fogg’s three motivators (sensation, anticipation, belonging) decompose cleanly across the Octalysis Core Drives. Sensation — pleasure and pain — maps onto Core Drive 7 (Unpredictability & Curiosity) on the pleasure side and Core Drive 8 (Loss & Avoidance) on the pain side. Anticipation — hope and fear — maps onto Core Drive 2 (Development & Accomplishment) on the hope side and again onto Core Drive 8 on the fear side. Belonging — social acceptance and rejection — maps onto Core Drive 5 (Social Influence & Relatedness).

What Octalysis adds that Fogg does not name: three motivational drives that sit outside his three-motivator triad. Core Drive 1 (Epic Meaning & Calling) — the drive to participate in something greater than yourself — is not reducible to sensation, anticipation, or belonging. Core Drive 3 (Empowerment of Creativity & Feedback) — the drive toward generative self-expression — is also not captured by Fogg’s triad. Core Drive 4 (Ownership & Possession) — the drive to accumulate, customize, and protect what you own — is a motivational force in its own right that Fogg subsumes under nothing. Designers who rely only on Fogg will systematically under-design for meaning, creativity, and ownership, because the upstream model tells them those forces don’t exist.

Mapping Ability’s Six Factors to Anti-Core Drives

Octalysis has a parallel structure for what I call Anti-Core Drives — the negative forces that sap motivation from each of the eight Core Drives. Fogg’s six Ability factors map directly onto specific Anti-Core Drives, which is where the two frameworks stop being rivals and start being a single diagnostic stack.

• Time-scarcity and Non-Routine feed the Anti-Core-Drive against Core Drive 4 (Ownership). A user who doesn’t have time or whose existing routine rejects the new behavior cannot build ownership of the feature, so Ownership motivation never accumulates.
• Brain Cycles feeds the Anti-Core-Drive against Core Drive 3 (Empowerment & Creativity). When cognitive load is high, users cannot be creative; they default to the path of least cognitive resistance, which kills expressive engagement.
• Physical Effort and Money feed the Anti-Core-Drive against Core Drive 2 (Development & Accomplishment). Obstacles that feel arbitrary (rather than challenging) make progress feel like drudgery, which is the inverse of accomplishment.
• Social Deviance feeds the Anti-Core-Drive against Core Drive 5 (Social Influence & Relatedness). When acting means being socially punished, the drive toward relatedness becomes a drive away from the behavior.

This map is where the two frameworks combine into a diagnostic. If your product’s behavior is not firing, ask: (1) which of the eight Core Drives is supposed to be supplying motivation, and is it actually active for this user right now? (2) Which of the six Ability factors is scarcest for this user in this moment, and which Anti-Core-Drive is that factor feeding? (3) Which of the three Prompt types — Spark, Facilitator, Signal — is actually appropriate for where this user sits on the motivation-ability graph? Three questions. Every time.

White Hat vs Black Hat Prompts

A final integration. Fogg’s three prompt types — Spark, Facilitator, Signal — have a White Hat and a Black Hat version, and the distinction matters for long-term retention. A White Hat Spark activates Core Drives 1–3 (Epic Meaning, Accomplishment, Empowerment) — “you’re 3 lessons from becoming fluent.” A Black Hat Spark activates Core Drives 6–8 (Scarcity, Unpredictability, Loss) — “you’ll lose your streak if you don’t log in right now.” Both work; the first produces sustainable engagement, the second produces compulsive engagement that decays into resentment.

Most products I’ve seen fail on this axis run almost entirely on Black Hat Sparks, because Black Hat Sparks have higher short-term click rates. The retention cost shows up 60–90 days later in the form of a dropoff curve no one understands. Fogg’s model does not warn you about this, because the model stops at the moment the behavior fires. The Octalysis overlay — specifically, the White Hat / Black Hat distinction — is what keeps your prompt design from quietly eating your user base.

Practical Steps for Applying the Fogg Behavior Model

If you want to actually use B = MAP in a product, a classroom, a clinic, or a workplace, here is the sequence I use with clients. It produces more reliable behavior change than “add a push notification” by a large margin.

1. Name the target behavior in one precise sentence. “Users should log a mood entry” is vague. “Users should tap the mood-log icon on the home screen within 60 seconds of opening the app” is precise. Fogg-style diagnosis is only as sharp as the behavior definition, because the three elements must be evaluated at the exact moment the behavior is supposed to fire.
2. Diagnose motivation by Core Drive, not by “high/low”. Ask which of the eight Core Drives is supposed to produce the motivation for this behavior, and whether that drive is actually active for this user. If you don’t know which Core Drive you’re activating, you don’t have a motivation design — you have a motivation wish.
3. Diagnose ability by identifying the single scarcest of the six factors. Do not try to reduce all six at once. Do not reduce the wrong one. Watch real users attempt the behavior. Notice which of Time, Money, Physical Effort, Brain Cycles, Social Deviance, or Non-Routine is the one they hit first. Attack that one.
4. Match the prompt type to the user’s position on the graph. If motivation is high and ability is low, send a Facilitator. If motivation is low and ability is high, send a Spark — and pick a White Hat Spark if you want the relationship to survive long-term. If both are already above the action line, send a Signal. Never send a Signal when motivation or ability is below the line; that is how you train users to ignore you.
5. Shrink the behavior until motivation only needs to barely clear the action line. This is the Tiny Habits move. If you need 40 units of motivation to fire the current behavior, redesign the behavior until it only needs 5. The action line is a threshold — you don’t need to overshoot it, you just need to clear it reliably.
6. Anchor the new behavior to an existing routine to drop Non-Routine cost. “After my morning coffee, I will…” is the canonical form. The new behavior rides on an existing neural pathway instead of cutting its own.
7. Instrument every dimension and pick one to improve each sprint. Measure motivation (engagement, session intensity), ability (time-to-complete, error rate, abandonment point), and prompt performance (open-rate by type, by hour, by segment). Pick the weakest of the three this sprint. Next sprint, pick the new weakest. Repeat until the behavior fires above your target rate.

The Fogg Behavior Model Was the Beginning, Not the End

B = MAP is a brilliant starting point. It gives you a three-element diagnostic that any product team can hold in working memory, and it forces you to distinguish between three failure modes that are usually conflated. Most product teams would benefit enormously from just applying it correctly, even without any extension.

But the model ends where behavioral design actually starts. It names the elements; it does not decompose them. It describes the threshold; it does not account for state changes. It explains the fire; it does not explain the burn. A designer who treats Fogg’s formula as the full map will repeatedly run into the same frustration — motivated users who don’t act, prompts that get ignored, one-time conversions that never become habits — without the diagnostic vocabulary to see why.

The version of behavioral design I have spent two decades teaching — and that our Octalysis Group team applies with LEGO, Microsoft, Porsche, and MrBeast — uses Fogg as the top-level checklist and Octalysis as the underlying causal engine. Fogg tells you which of three suspects is to blame. Octalysis tells you which of eight levers will fix it. You need both. If you are willing to put in the reps on both frameworks — and the same applied work on Skinner, the Hook Model, SDT, and a handful of other specific theories — you end up with behavioral designs that work the first time, and keep working long after the launch.

That is the work. Fogg’s model is the doorway. Walk through it.

Frequently Asked Questions About the BJ Fogg Behavior Model

What is the BJ Fogg Behavior Model?

The BJ Fogg Behavior Model is a framework developed by Stanford behavioral scientist B.J. Fogg stating that any behavior requires three elements to converge at the same moment: Motivation, Ability, and a Prompt. It is written as B = MAP (originally B = MAT, where “T” stood for Trigger). If any one of the three elements is missing at the moment of decision, the behavior does not fire.

What does B = MAP stand for?

B stands for Behavior. M stands for Motivation (how much the person wants to do it). A stands for Ability (how easy it is to do). P stands for Prompt (the cue that tells them to do it now). The formula is multiplicative — if any factor is zero, Behavior is zero — which is why it is written with an implicit multiplication rather than addition.

What are the 6 factors of Ability in the Fogg Behavior Model?

The six factors are Time, Money, Physical Effort, Brain Cycles, Social Deviance, and Non-Routine. Fogg’s rule is that Ability is determined by whichever factor is scarcest for the user at the moment of decision, not by reducing all six in parallel.

What is the difference between a Spark, a Facilitator, and a Signal?

A Spark is a prompt that adds motivation and is used when ability is high but motivation is low. A Facilitator is a prompt that removes friction and is used when motivation is high but ability is low. A Signal is a reminder used when motivation and ability are already both high. Most product teams over-use Signals and under-use Sparks and Facilitators.

What is the difference between B = MAT and B = MAP?

They are the same model. Fogg originally called the third element “Trigger” (B = MAT) and later renamed it to “Prompt” (B = MAP) because the word “trigger” suggested a mechanical cue, when in practice prompts are contextual, emotional, and sometimes self-generated. The renaming did not change the formula, only the terminology.

How does the Fogg Behavior Model compare to the Hook Model?

Nir Eyal’s Hook Model (Trigger, Action, Variable Reward, Investment) extends Fogg’s model by adding a reinforcement loop at the end. Fogg explains why a behavior fires once; the Hook Model explains why a behavior becomes a habit. The Hook Model is more useful for designing habit-forming products; Fogg is more useful for diagnosing why a single specific behavior is not firing right now.

How does the Fogg Behavior Model compare to the Octalysis Framework?

Fogg treats motivation as a single axis; the Octalysis Framework decomposes motivation into eight distinct Core Drives (Epic Meaning, Accomplishment, Empowerment, Ownership, Social Influence, Scarcity, Unpredictability, Loss). Fogg tells you that motivation needs to be high; Octalysis tells you which kind of motivation to design for. Most serious designers use them together — Octalysis as the causal engine, Fogg as the execution checklist.

What is Fogg’s Tiny Habits method and how does it relate to B = MAP?

Tiny Habits is Fogg’s operational recipe for building new behaviors: anchor the new behavior to an existing routine, shrink the new behavior until it requires almost no motivation, and celebrate immediately after. It is a direct application of B = MAP — anchoring reduces the Non-Routine ability cost to near-zero, shrinking reduces the motivation needed to clear the action line, and the celebration creates positive reinforcement for the next iteration.

Why do most prompts in products fail to fire behavior?

Because they are almost always Signals sent to users whose motivation or ability is below the action line. A Signal assumes motivation and ability are already high enough — if either is not, the Signal does nothing except teach the user to ignore future prompts. The fix is not more Signals. The fix is to diagnose whether the user needs a Spark (to add motivation) or a Facilitator (to remove friction) at that moment, and send that instead.

Is the Fogg Behavior Model ethical to use?

The model itself is ethically neutral — it describes how behavior happens, not which behaviors to design for. The ethical concerns come from how it is applied. Products that rely heavily on fear-based Sparks (Black Hat motivation) produce short-term engagement at the cost of long-term trust and well-being. Fogg himself has been increasingly vocal that behavior design ethics require designing for outcomes the user would endorse on reflection, not just outcomes that produce engagement. The Octalysis White Hat / Black Hat distinction is a practical tool for keeping Fogg-model applications on the ethical side of the line.

References

Fogg, B. J. (2009). A behavior model for persuasive design. Proceedings of the 4th International Conference on Persuasive Technology (Persuasive ’09), 40. Association for Computing Machinery. https://doi.org/10.1145/1541948.1541999

Fogg, B. J. (2003). Persuasive Technology: Using Computers to Change What We Think and Do. Morgan Kaufmann.

Fogg, B. J. (2020). Tiny Habits: The Small Changes That Change Everything. Houghton Mifflin Harcourt.

Chou, Y. (2019). Actionable Gamification: Beyond Points, Badges, and Leaderboards. Packt Publishing.

Eyal, N. (2014). Hooked: How to Build Habit-Forming Products. Portfolio/Penguin.

Michie, S., van Stralen, M. M., & West, R. (2011). The behaviour change wheel: A new method for characterising and designing behaviour change interventions. Implementation Science, 6(1), 42. https://doi.org/10.1186/1748-5908-6-42

Skinner, B. F. (1953). Science and Human Behavior. Macmillan.

Ryan, R. M., & Deci, E. L. (2000). Self-determination theory and the facilitation of intrinsic motivation, social development, and well-being. American Psychologist, 55(1), 68–78. https://doi.org/10.1037/0003-066X.55.1.68

Wood, W., & Rünger, D. (2016). Psychology of habit. Annual Review of Psychology, 67, 289–314. https://doi.org/10.1146/annurev-psych-122414-033417

Berridge, K. C., & Robinson, T. E. (1998). What is the role of dopamine in reward: Hedonic impact, reward learning, or incentive salience? Brain Research Reviews, 28(3), 309–369.

Schultz, W. (2016). Dopamine reward prediction-error signalling: A two-component response. Nature Reviews Neuroscience, 17(3), 183–195.

Duhigg, C. (2012). The Power of Habit: Why We Do What We Do in Life and Business. Random House.

Thaler, R. H., & Sunstein, C. R. (2008). Nudge: Improving Decisions About Health, Wealth, and Happiness. Yale University Press.

Stanford Behavior Design Lab. (n.d.). Behavior Model. https://behaviormodel.org/

Related Reading

• BJ Fogg’s 3 Triggers Through the Octalysis Framework (Part 2)
• The Octalysis Framework for Gamification & Behavioral Design
• Self-Determination Theory: Ryan & Deci’s Motivation Framework
• B.F. Skinner’s Operant Conditioning Explained
• Nir Eyal’s Hook Model for Habit-Forming Products
• Flow Theory: Csikszentmihalyi’s Optimal Experience Framework
• Maslow’s Hierarchy of Needs (S-Tier Behavioral Designer’s Guide)
• Cialdini’s 6 Principles of Persuasion (Designer’s Guide)
• Actionable Gamification: Beyond Points, Badges & Leaderboards

WOULD YOU LIKE YU-KAI CHOU TO WORK WITH YOUR ORGANIZATION?