improve-retention

Map the failing behavior to B=MAP: check whether a prompt exists, then audit ability across six factors (time, money, physical effort, mental effort, social deviance, non-routine), and only then examine motivation. Day-1 drop-off usually indicates a prompt failure, while day-7 drop-off signals the behavior is too hard for receding motivation.

B=MAP states that behavior occurs when Motivation, Ability, and a Prompt converge at the same moment. Behaviors above the Action Line succeed when prompted; below it, no prompt works. The reliable design strategy is increasing ability (making behaviors easier) rather than boosting motivation.

Rate each of the six Ability Chain factors from 1-5 for the target behavior: time, money, physical effort, mental effort, social deviance, and non-routine. The lowest-rated factor is the bottleneck blocking the behavior. Fix that weakest link first, typically with smart defaults, templates, or progressive disclosure.

Use B=MAP for diagnosis when a specific behavior is failing and you need to identify whether motivation, ability, or prompts are the cause. Use the Hook Model for designing self-reinforcing engagement loops with triggers, variable rewards, and investment. The two frameworks complement each other.

Notifications fail when sent to users below the Action Line — lacking motivation or ability, the prompt becomes spam. Schedule-based messages like "We miss you!" underperform event-based prompts tied to real activity, such as "Your report is ready." Prompt fatigue also degrades the value of all future notifications.

Motivation comes in waves that spike at signup and crash by day 14-30, so products depending on it fail at the trough. Motivation tactics don't compound and are context-dependent. Ability-first design — shrinking behaviors to starter steps that survive low motivation — produces more durable retention.