init.Habits app store
blog — august 7, 2026

← all posts

Tiny Habits by BJ Fogg: the model, the recipe, and the celebration nobody does

Tiny Habits by BJ Fogg: the model, the recipe, and the celebration nobody does — init.Habits blog

Three books get passed around whenever someone decides to change something: Atomic Habits, The Power of Habit, and Tiny Habits by BJ Fogg. The first two are the ones people quote. Fogg's is the one people can act on the same afternoon, because it reads less like a theory of behaviour and more like assembly instructions. Tiny habits by BJ Fogg reduces to three moving parts: a model that tells you why a behaviour didn't happen, a one-sentence recipe for installing a new one, and a celebration step that almost everyone reads, finds embarrassing, and quietly skips.

Fogg ran a behaviour design lab at Stanford for about two decades before the book existed, and the method that came out of it is mechanical in a way the other two aren't. You don't have to feel motivated. You need something that already happens reliably, a version of the new behaviour small enough to be nearly free, and a way of marking the moment as a win.

This post is about Fogg's method specifically. For the cue-routine-reward loop that Duhigg popularised, habit loop examples walks through it with real behaviours; if you're setting up your first habit at all, a habit tracker for beginners is the more practical starting point.

B=MAP, and what it's actually for

The model is one line. B = MAP: Behaviour happens when Motivation, Ability and a Prompt converge at the same moment. Remove any one and nothing happens, whatever you promised yourself on Sunday.

Written forwards it sounds like a slogan. Run it backwards and it turns into a diagnostic, which is the part worth keeping.

what actually happenedthe part that failedthe fix Fogg would reach for
you never thought about it all daypromptattach it to something that already happens without fail
you thought about it and didn't feel like itabilityshrink it until "didn't feel like it" is no longer a valid excuse
you did it eleven days, then stopped for a weekmotivation carried it, then leftrebuild the same habit at a tenth of the size
you did it, but only on days you'd slept wellability, on your worst dayset the floor at the tired-Tuesday version, not the good one

Fogg's ordering matters more than the equation. When a behaviour doesn't happen, he'd have you fix ability first, prompt second, and touch motivation last — because motivation is the one variable you can't schedule. It shows up in January and leaves in February, and any design that depends on it inherits that swing.

The recipe: after I ___, I will ___

The whole method compresses into a sentence with three slots.

Anchor. An existing behaviour that already happens on its own — brushing your teeth, sitting down at your desk, closing the laptop, putting the kettle on. Not a time of day. "At 7am" isn't an anchor because nothing physically happens at 7am; "after my feet touch the floor" does.

Tiny behaviour. The new thing, cut down until it's almost insulting. Floss one tooth. Read one paragraph. Open the running app. Two pushups. Fogg's rule is that it should take under thirty seconds and require no decision.

Celebration. Immediately after, do something that makes you feel successful. That's the third slot, and it's the one that goes missing.

Written out: After I flip the kettle switch, I will do two pushups, and then I'll say "nice" out loud. The anchor half of that recipe is what the internet later repackaged and sold separately as habit stacking. It's a real technique and it works, but it's one slot of three — stacking tells you where a behaviour goes and says nothing about its size or what happens after it.

The celebration, and why it feels ridiculous

Fogg's claim here is the most disputed thing in the book: emotions create habits, repetition doesn't. Feel good immediately after a behaviour and the brain wires it faster than any number of grim repetitions will.

Most readers find this unbearable. Saying "yes!" to yourself in an empty kitchen after flossing one tooth feels like something you'd hide from your flatmate, so people skim past it and keep the anchor and the shrinking, which are the comfortable two-thirds. That's the single most common way the method gets watered down.

One caveat worth stating plainly: the strong version of "repetition doesn't matter" doesn't quite survive contact with the evidence. The UCL habit-formation study that produced the well-travelled 66-day figure found automaticity building through plain repetition, across a range from 18 to 254 days depending on the person and the behaviour. Repetition clearly does something. What the celebration seems to add is a reason for the repetition to keep happening while it's still fragile, in the first three weeks when nothing about the habit feels rewarding on its own.

If the verbal version is too much, use a physical one nobody can see. A fist under the desk. Checking the box in a tracker and watching the square fill. The requirement is that something registers as a small win in the two seconds after the behaviour, not that you perform enthusiasm.

How to write a Tiny Habits recipe

  1. Pick the behaviour you want, then write down the smallest version of it that would still count — the one you could do with a fever.
  2. Find an existing behaviour that happens every single day without you managing it. That's your anchor.
  3. Decide whether the new habit goes after the anchor or replaces the dead moment right after it. Immediately after works better than "later that morning".
  4. Choose your celebration and rehearse it three times on purpose, so it's automatic when the real moment arrives.
  5. Run it for a week without raising the size. If you're doing more than the tiny version most days, that's fine — let it grow on its own rather than promoting it in writing.

Tiny Habits by BJ Fogg in practice: three recipes, twenty days

Take someone installing three things at once, which Fogg allows precisely because each one is trivial.

  • After I pour my morning coffee, I will read one paragraph. Twenty days: 20 done. Median actual reading, about eleven minutes. The paragraph was never the point; it was the thing small enough to start.
  • After I close my work laptop, I will do two pushups. Twenty days: 17 done. All three misses were days the laptop closed in a café, where the anchor fired perfectly and doing pushups on the floor was never going to happen.
  • After I put my phone on the charger, I will write one sentence in a journal. Twenty days: 20 done, average four sentences.

The pushup failure is the instructive one. Nothing was wrong with the behaviour or the motivation — the anchor fired in a context where the behaviour was impossible. That's a prompt problem wearing an ability costume, and the repair is a second recipe for café days, not more discipline.

Where the tiny version stops scaling

Shrinking solves the starting problem. It does not solve every problem, and pretending otherwise is how people end up with a 200-day streak of two pushups and no measurable change in anything.

Some behaviours have a genuine minimum size. Seven hours of sleep can't be shrunk to seven minutes. A gym session with a 20-minute commute each way has a floor set by geography, not by willpower. For those, the tiny recipe is best used on the entry to the behaviour — put on the running shoes, pack the bag the night before — and the actual outcome has to be tracked separately, or you'll congratulate yourself for the shoes indefinitely.

The other limit is growth. Fogg says the behaviour will expand naturally, and often it does, but not on a schedule and not for everyone. If a habit has sat at the floor for two months and you wanted more, raise the target deliberately and expect it to wobble — that's a new habit, not a bigger old one. Picking things worth this effort in the first place is a separate exercise, and what habits to track is a decent menu; keeping them alive through the messy weeks is staying consistent, which is where most methods are actually won or lost.

FAQ

What is the Tiny Habits method by BJ Fogg?

It's a behaviour-design method built on one recipe: after an existing behaviour you already do reliably, perform a new behaviour small enough to take under thirty seconds, then immediately celebrate. Fogg's underlying model is B=MAP — behaviour needs motivation, ability and a prompt at the same moment — and the method deliberately manipulates ability and prompt rather than motivation, since motivation is the one you can't rely on.

What does B=MAP stand for?

Behaviour = Motivation, Ability, Prompt. All three have to arrive together for a behaviour to happen. Its practical use is backwards: when something didn't happen, work out which of the three was missing. Forgot entirely means the prompt failed, couldn't face it means the behaviour was too big, and did it only while enthusiastic means it was running on motivation.

Is Tiny Habits the same as habit stacking?

No, though they overlap. Habit stacking is essentially Fogg's anchor step — attaching a new behaviour to an existing one — presented on its own. The Tiny Habits method adds two things stacking doesn't specify: shrinking the behaviour until it's nearly free, and celebrating immediately afterwards to mark it as a success.

Do I really have to celebrate after every tiny habit?

Something has to register as a win in the couple of seconds after the behaviour, but it doesn't have to be a verbal one. A private fist, a quiet "good", or watching a square fill in on a habit tracker all do the job. Skipping the step entirely is the most common way the method gets diluted, because the first weeks of a new habit produce no natural reward of their own.

try init.Habits

init.Habits is a habit tracker that looks like a terminal — streaks with shields so one bad day doesn’t wipe the chain, github-style heatmaps, and 23 editor themes. on iPhone and in any browser.

download on the app store open the web app see the features →