The Fogg Behavior Model, Explained (and Why Your Habit Tracker Should Use It)

Most habit trackers ask you one question: did you do it today, yes or no? That checkmark feels like progress, but it doesn't tell you anything about why you missed a day, or what to fix so tomorrow goes differently. The Fogg Behavior Model is the framework we built TrakBit around specifically because it answers that question.

What the Fogg Behavior Model actually says

BJ Fogg, who runs the Behavior Design Lab at Stanford, spent two decades studying why people do — or don't do — the things they intend to. His model compresses that research into one formula:

B = MAP

Behavior happens when Motivation, Ability, and Prompt all show up at the same moment. Drop any one of the three low enough, and the behavior doesn't happen, no matter how strong the other two are.

• Motivation is how much you want to do it right now. It's real, but it's also the least reliable of the three — it spikes on January 1st and Monday mornings, and it dips on a bad night's sleep. Most advice about habits is really just advice about motivation, which is why most of it doesn't hold up past a few weeks.
• Ability is how easy the behavior is to do in this moment — physically, mentally, and in terms of time. "Go to the gym for an hour" has low ability at 11pm on a work night. "Put on running shoes" has high ability at almost any time.
• Prompt is the trigger that reminds you to act at all. Without one, motivation and ability are irrelevant — you simply never think to do the thing.

Fogg's own summary of the model is blunt: if a behavior isn't happening, the problem is almost never a personal failing. It's that one of these three is too low, and you can diagnose which one.

Why streak counters miss half the picture

A plain streak counter — the grid of filled and empty squares that most habit apps use — only records the output. It can't tell you whether Tuesday's miss happened because you weren't motivated, because the habit was too hard to fit into a packed day, or because nothing reminded you until it was already 11pm. Those are three completely different problems with three completely different fixes, and a checkmark treats them all the same: as failure.

That's the gap the Fogg model closes. It reframes a missed day from "I failed" to "which of the three broke down, and what does that tell me to change" — lower the difficulty, fix the cue, or accept that motivation will fluctuate and design around it instead of relying on it.

How TrakBit builds this in

Inside TrakBit, every habit has a Fogg breakdown, not just a checkmark. You set Motivation, Ability, and Prompt for a habit, and TrakBit shows you a completion probability calculated from all three — the same B = MAP logic, made visible instead of invisible.

When a habit isn't sticking, TrakBit's recent-failures view groups your missed days so you can actually see the pattern: is Ability consistently the weak link on weekdays? Does Prompt disappear on weekends when your routine changes? That's a different, more useful question than "how long is my streak," because it points at what to adjust instead of just how much you've disappointed yourself.

In practice, that turns into concrete changes:

• Low Ability → shrink the habit. "Meditate for 20 minutes" becomes "sit down and take three breaths." Fogg's own research backs this — tiny versions of a habit are dramatically more likely to survive a bad day.
• Low Prompt → anchor the habit to something that already happens reliably, right before or after it, instead of trusting a phone notification you'll eventually swipe away.
• Low Motivation → stop trying to fix it directly. Motivation is the least controllable of the three; lowering Ability or tightening the Prompt usually does more for consistency than any pep talk.

How this compares to other trackers

Apps like Streaks and HabitKit are genuinely good at what they do — Streaks' Apple Health integration and HabitKit's GitHub-style grid both make consistency satisfying to look at. Neither is built around diagnosing why a habit breaks down, because neither is built on a behavior-science model in the first place. If what you want is a clean visual streak, they're a fine choice. If you want the app to help you figure out what's actually blocking a habit — not just remind you that it's blocked — that's the specific gap TrakBit's Fogg-based tracking is built to fill.

Try it

The Fogg Behavior Model is free to read about — Fogg's book Tiny Habits is the definitive source. TrakBit is our attempt to build an app around it instead of around a checkmark. Download TrakBit and set your first habit's Motivation, Ability, and Prompt to see how it changes what "missing a day" actually tells you.

FAQ

What is the Fogg Behavior Model? A framework from Stanford researcher BJ Fogg stating that Behavior = Motivation × Ability × Prompt (B = MAP). A behavior only happens when all three are high enough at the same moment; if it's not happening, at least one of the three is too low.

Is the Fogg Behavior Model backed by research? Yes. BJ Fogg developed and tested the model over roughly two decades at Stanford's Behavior Design Lab, and it's the basis for his book Tiny Habits (2019).

Does TrakBit require using the Fogg model? No — you can track a habit with a simple daily check-in. The Motivation/Ability/Prompt breakdown is there for habits that aren't sticking and you want to understand why, not a mandatory step for every habit.

How is this different from a habit streak counter? A streak counter records whether you completed a habit. TrakBit's Fogg-based tracking additionally estimates why a habit is or isn't sticking, based on which of Motivation, Ability, or Prompt is weakest — so you get a specific thing to change, not just a number that resets.