retention-design

Retention Design

The Law

A FEATURE LAUNCHED WITHOUT A DESIGNED RETENTION LOOP IS A FEATURE DESIGNED TO CHURN.
"Users will come back if they like it" has no activation moment, no habit trigger, and no reactivation path — which describes every churned product, because users who liked it also forgot about it.
Activation moment + habit loop + reactivation path defined before launch IS retention design.

When to Use

Trigger before:

• Launching any new product or significant new feature
• Redesigning an existing flow where D7 or D30 retention is below target
• Adding a feature whose primary value is realised over repeated sessions (not first use)
• Building any AI assistant, tool, or agent that requires habit formation

When NOT to Use

• One-time-use features where the user's goal is fully completed in a single session (e.g., a one-time document export — retention is not the right metric)
• Features for internal tools where users are required to return (no voluntary retention decision being made)

The Three Retention Elements

1 — Activation Moment

The specific action a user takes that predicts they will return.

Activation is not the first session. It is the moment in the first session when the user understands what the product can do for them — the "aha moment."

How to find it:

• Compare the behaviour of retained users (D30+) vs. churned users
• Find the action that is significantly overrepresented in retained users in the first session
• Verify causality vs. correlation: does encouraging new users to reach this action earlier improve D30?

What it looks like:

Slack: send your first message
Dropbox: put a file in a folder and access it from another device
GitHub Copilot: accept the first autocomplete suggestion

Required in the design:

• Name the activation action
• Measure how many new users reach it in the first session (baseline)
• Design the first-session flow to lead users to this action

2 — Habit Loop

The cue → routine → reward cycle that brings users back.