Fogg Behavior Model: Why Users Act (or Don't)
The Fogg Behavior Model states a behavior only happens when Motivation, Ability, and a Prompt converge (B=MAP). Use it to diagnose why a feature fails or to design new ones. The footgun is blaming low motivation when the real issue is low ability.
Why it exists
To provide a simple, universal framework for understanding why human behaviors happen or fail. Instead of vaguely guessing about user intent, this model gives product builders a concrete diagnostic tool to pinpoint why an action isn't occurring and which lever to pull to fix it.
The mental model
Behavior happens when Motivation, Ability, and a Prompt come together at the same moment. The formula is B=MAP. Think of it as a three-legged stool: if any one of Motivation, Ability, or a Prompt is missing, the behavior collapses. No amount of motivation can overcome a complete lack of ability or a missing prompt.
How it works
The model has three components that must converge:
Motivation
The user's desire to perform the action. This can range from high (a user is desperate to solve a problem) to low (a user is just browsing).
Ability
How easy it is for the user to perform the action. This isn't just about skill; it includes factors like time, money, cognitive load, and physical effort. Making a task simpler is often the most effective way to increase behavior.
Prompt
The trigger that calls the user to action. This can be external (a push notification, an email, a button) or internal (a feeling of boredom, a memory). Without a prompt, the behavior won't happen now, even if motivation and ability are high.
The key insight is the tradeoff between Motivation and Ability. If motivation is very high, users will figure out how to do difficult things. Conversely, if a task is incredibly simple, it requires very little motivation to get done.
When to use it
Use this model as a lens for diagnosing product problems or designing new features. It's invaluable for analyzing user funnels, improving onboarding flows, and increasing feature adoption. When a user drops off, ask: Was their motivation too low? Was the task too hard (low ability)? Or were they never prompted to take the next step?
When not to use it
The model is for analyzing a single, discrete action. It's less suited for understanding complex, multi-step user journeys as a whole or for explaining deep-seated, long-term psychological states. It's a tactical tool for behavior design, not a comprehensive strategic framework.
One canonical example
Imagine you want a user to enable push notifications. If they don't, B=MAP gives you three places to investigate.
Motivation
Does the user understand the benefit? Maybe they don't see the value in getting alerts.
Ability
How hard is it? If enabling requires navigating through three screens of system settings, that's low ability. A single-tap opt-in is high ability.
Prompt
When and how are you asking? A jarring, immediate request on first app open is a poorly timed prompt. A prompt after the user has a positive experience is much more effective.
Interview question
A product team observes low engagement with a new feature, despite initial user feedback indicating high interest. Based on the Fogg Behavior Model, which intervention is often the most effective first step to increase usage?
- a.Redesign the feature to reduce the number of steps required for completion.Correct
- b.Implement a new onboarding flow to educate users on the feature's benefits.
- c.Offer incentives or rewards for users who successfully use the feature.
- d.Increase the frequency and prominence of in-app prompts for the feature.
Why? this is the answer
The card emphasizes that 'making a task simpler is often the most effective way to increase behavior' and warns against blaming low motivation when low ability is the actual issue. Reducing steps directly addresses ability, making the behavior easier to perform. While increasing motivation or prompts can help, improving ability is frequently the most impactful initial lever.
Just read this? Test yourself on what you have been reading.
Read the original → behaviormodel.org
- #growth
- #product
- #psychology
- #experimentation
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on growth — each one lists the topics its interview covers.
See open roles