The Fogg Behavior ModelWhy This Matters to YouImagine you've spent weeks designing a feature. You launch it — and crickets. Nobody uses it.Sound familiar?The problem might not be bad design. It might be that your users simply weren't set up to take the action you wanted.This brings us to the Fogg Behavior Model.Created by Dr. BJ Fogg at Stanford University, this framework has been cited in over 1,900 academic papers and adopted by product teams worldwide. It's also one of the simplest frameworks in design. Five minutes to explain. Lifetime to master.By the end of this article, you'll be able to:Predict when users will perform a behaviorDiagnose why a feature isn't being adoptedApply practical fixes to your designs immediatelyThis is the first installment of UX Unpacked — a series where I break down essential UX concepts, one framework at a time. Each piece stands alone while building toward deeper fluency. No jargon dumps. No gatekeeping. Just clarity.Let's begin.The Core Formula: B = MAPHere's the entire model in one line:Behavior = Motivation × Ability × PromptOr, translated into plain English:A behavior happens only when Motivation, Ability, and a Prompt all align at the same moment.If any one of these three pieces is missing, nothing happens.No complexity. No hidden variables. This is the ceiling and the floor.The Three Ingredients1. Motivation — Do I want to do this?Motivation is your user's desire to perform an action. The catch: motivation fluctuates wildly. A user who's highly motivated today might be unmotivated tomorrow.Three sources of motivation:TypeWhat It MeansExamplePersonInternal desireI love cooking, so I download recipe appsAdvantageExternal reward or consequenceI complete tasks to earn a bonusContextEnvironmental influenceEveryone in my team uses Slack, so I do tooDesign Tip: Don't try to manufacture motivation from scratch. Instead, connect your feature to motivations that already exist in your users' lives.2. Ability — Can I do this easily?Ability is about simplicity. Even highly motivated users won't act if something is too hard.Five factors that make things harder:Time — Does it take too long?Money — Is it expensive?Physical effort — Does it require clicking 20 times?Mental energy — Is it confusing?Routine fit — Does it disrupt their workflow?Design Tip: The easiest fix is almost always to reduce friction. Remove steps, pre-fill fields, default to sensible choices.3. Prompt — Am I reminded to do this?The prompt is your trigger. Without it, no matter how motivated or able your user is, nothing happens.Three types of prompts:TypeWhen to UseExampleFacilitatorHigh motivation, low abilityA step-by-step wizard guides setupSignalHigh motivation, high abilityA subtle icon reminds them to clickSparkLow motivation, high abilityA limited-time offer nudges them to actDesign Tip: Prompts should be timely and noticeable — but not annoying. A well-placed button beats an ignored notification.The Action Line: Where Behavior HappensNow for the visual that makes it stick.Imagine a graph showing motivation on the vertical axis and ability on the horizontal axis, with a curved line separating where behavior happens from where it doesn't.Key insights:If a behavior is very easy, you need less motivationIf a behavior is hard, you need lots of motivationEither side of the equation can compensate for the otherWhat's below the line? Nothing happens. Fix one variable, and you cross the threshold.How to Debug Missing Behavior (The Right Order!)When a feature isn't getting adoption, designers often blame motivation. "Users just don't care!"But that's usually wrong.Follow this checklist instead:Step 1: Is there a prompt?Can users find the button?Do they know when to act?Is it clear what happens next?Fix: Make the prompt visible and well-timed.Step 2: Is it easy enough?How many clicks/taps?Are there unnecessary forms?Does it fit into their current flow?Fix: Remove friction. Make it stupidly simple.Step 3: Only then — do they want to?What's in it for them?Does it connect to an existing desire?Have you removed barriers that kill motivation?Fix: Tie your feature to real user goals, not business goals.Remember: Fixing motivation is the last resort. If your prompt is invisible or your flow takes 20 minutes, no amount of excitement will help.Real-World Example: BeRealBeReal exploded in popularity by nailing all three ingredients.IngredientHow BeReal Delivered ItPromptDaily notification at a random time — surprising and impossible to ignoreAbilityOne photo, under 2 minutes, no editing. Stupidly simpleMotivationAuthenticity + social connection + FOMO among Gen ZResult? Apple's 2022 iPhone App of the Year. All because all three converged.Apply This to Your Design TodayPick a behavior you're trying to encourage. Now ask:QuestionYour AnswerIs there a clear, timely prompt?Yes / NoIs the action as easy as possible?Yes / NoDoes the user genuinely want to do this?Yes / NoAny box unchecked? That's your fix.A Word on EthicsWith great power comes responsibility.Dr. Fogg himself emphasizes two rules:Help people do what they already want to do.Help people feel successful.Avoid dark patterns: fake countdowns, hidden costs, manipulative notifications. Design for user success, not just business metrics. Long-term trust beats short-term wins.Wrapping UpThe Fogg Behavior Model doesn't promise magic. But it does give you:A diagnostic framework for stuck featuresA prioritized checklist for improvementA common language for your teamRemember: B = MAP. When a behavior isn't happening, one piece is missing. Find it, fix it, move on.What's Coming Next in This SeriesUpcoming articles will cover:Mental models for interaction designHick's Law and decision fatigueJakob's Law and user expectationsPeak-End Rule for memory retentionFitts's Law and target sizingEach piece builds on the last while standing alone for new readers. My goal is to make these concepts accessible to anyone starting in UX — no jargon dumps, no gatekeeping.