Where the earlier lessons in this track explain why behavior happens, this one is about concrete strategies for a product actually meant to help someone build, change, or break a behavior — a fitness app, a budgeting tool, a habit tracker.
When a user already wants to do something, the design job is mostly getting out of the way — fewer steps, fewer fields, fewer decisions. This is Fogg's "ability" lever from two lessons back, applied specifically to a wanted behavior rather than a business-desired one.
A new habit is far more likely to stick if it starts small enough to require almost no willpower — a habit-tracking app that opens on "log one glass of water" rather than "plan your full daily nutrition" is applying this directly. Once the small version becomes routine, it naturally has room to grow.
A progress bar, a streak counter, or a checklist that fills in does two things: it shows the user they're making real progress (which sustains motivation on its own), and it makes the eventual completion feel earned rather than sudden. A completion state should also be unmistakably, visibly different from an in-progress one — vague or subtle "done" states waste this entirely.
| Design lever | What it does | Example |
|---|---|---|
| Reduce friction on a wanted action | Removes the ability barrier | One-tap logging instead of a multi-field form |
| Start small | Requires less motivation to begin | A 2-minute starter habit instead of the full routine |
| Make progress visible | Sustains motivation mid-way through | A progress bar, a streak, a percentage-complete indicator |
| Make completion clear | Delivers the psychological reward | A distinct "done" state, a checkmark animation, a completion message |
The line is intent, not the technique
These same levers work for good and for exploitative design equally well — a streak counter that quietly guilt-trips a user for missing one day (rather than simply letting them resume) has crossed from behavior support into the dark-pattern territory from two lessons back.