Fogg Behavior Model: What It Is and Why It Matters at Work

Behavior happens when three elements converge at the same moment: motivation, ability, and a prompt. Remove any one of them and the behavior doesn’t occur. That’s the Fogg Behavior Model in a single sentence — and it’s deceptively powerful once you stop treating it as a diagram on a slide deck and start using it to diagnose why your team isn’t doing the things you’ve asked them to do.

The Origin

BJ Fogg, a behavioral scientist at Stanford’s Persuasive Technology Lab, introduced the model (originally called the Fogg Behavior Model, or FBM) in 2009. His core insight was that most organizations over-invest in motivation — inspirational town halls, engagement surveys, values posters — while ignoring the other two levers. Motivation is volatile. Ability and prompts are designable.

How It Works in Practice

The model is expressed as B = MAP: Behavior happens when Motivation, Ability, and a Prompt converge simultaneously.

Scenario 1: The manager who won’t give feedback. Most companies assume this is a motivation problem. They run workshops on “the importance of feedback culture.” But often the manager doesn’t know how to give feedback without it turning adversarial (an ability gap), or there’s simply no moment in their week where feedback is prompted. Fix either of those and the behavior starts happening — no motivational speech required.

Scenario 2: The safety checklist nobody fills out. A manufacturing firm noticed compliance with end-of-shift safety checklists was around 40%. Leadership’s instinct was to add consequences — a motivation play. Instead, they moved the checklist from a clipboard in the break room to a tablet mounted at the exit door (ability: made it easier; prompt: placed it in the path of an existing behavior). Compliance hit 90% within a month.

Scenario 3: Peer recognition that doesn’t stick. You’ve launched a recognition platform. Usage spikes in week one, then flatlines. The prompt disappeared — nobody’s reminded to recognize a colleague at the moment they witness good work. A well-timed nudge after a project milestone closes the gap more than another all-hands reminder about “using the platform.”

What Most People Get Wrong

The biggest misconception is treating motivation as the default fix. When someone isn’t doing a desired behavior, the instinct is to assume they don’t want to. Fogg’s model reframes the question: Is this a motivation problem, an ability problem, or a prompt problem? In most workplace scenarios, it’s ability or prompts — the boring, structural stuff that doesn’t make for exciting leadership narratives but actually changes what people do.

Another common mistake: treating the three elements as independent sliders. They interact. When motivation is sky-high (a crisis, a deadline), people can push through low ability. But you can’t sustain crisis-level motivation. Designing for high ability and reliable prompts creates behavior that persists after the urgency fades.

Related Terms

• Nudge Theory — designing prompts and environmental cues to influence decisions
• Choice Architecture — structuring the environment to make desired behaviors easier
• Implementation Intentions — a specific type of self-prompt using if-then planning
• Deliberate Practice — building ability through structured repetition

FAQ

How is the Fogg Behavior Model different from nudge theory? Nudge theory focuses primarily on environmental design and defaults — one subset of what Fogg would call “ability” and “prompts.” The Fogg model is broader, incorporating motivation as a third variable and providing a diagnostic framework rather than a design technique.

Can you use the Fogg model for team-level behavior, not just individuals? Yes, though the analysis gets more complex. Each person on a team may have different ability levels and respond to different prompts. The model works best when you identify the specific behavior you want (not a vague outcome like “collaboration”) and diagnose the MAP bottleneck for the people who aren’t doing it.

What’s the fastest lever to pull? Almost always prompts. They’re cheap, fast to implement, and surprisingly underused. If the behavior isn’t happening and people have the skills, the most likely culprit is that nothing in their environment is triggering the action at the right moment.