Activation

Get users to the first proof of value—the action that predicts they will return.

Prerequisite: Customer Discovery — know who this is for and what state they arrive in. Related concepts: Feeling North Star, Tools, Techniques, and Practices.

What it is

Activation is the moment a new user experiences the product’s core value for the first time—not the moment they finish onboarding, and not the moment they sign up. It is defined by a specific action (or short sequence of actions) that reliably predicts a person will come back, chosen because it correlates with retention in your product, not because it is easy to instrument. “Created an account” is rarely an activation event; “sent the first message that got a reply,” “saw the first chart with real data,” or “shipped the first automated task” usually are.

This distinction—activation as an evidence-backed milestone rather than a funnel-completion checkbox—is what separates real activation work from onboarding decoration. Onboarding is the path; activation is the destination the path should be measured against. A team can have a beautiful, fast onboarding flow that still fails to activate anyone, because the flow was optimised for completion rather than for producing the specific “aha” that makes someone believe the product is worth their continued attention.

Why it works

Activation works because it forces a team to be honest about what “the product working” actually means for a real person, instead of assuming that finishing setup is the same thing as experiencing value. Defining the activation event—and validating it against Day 7 or Day 30 retention—turns a vague goal (“get people engaged”) into a falsifiable one (“does completing this action predict return, and if not, what does?”). Teams that skip this step tend to optimise vanity milestones: tutorial completion, profile fullness, or signup conversion, none of which tell you whether anyone actually benefited.

The underlying mechanism is the same one Jobs-to-be-Done describes: a person hired the product to make a specific piece of progress, and activation is the first evidence that the hire was a good decision. Get there fast and the person’s feeling north star shifts from doubt to competence; take too long, or bury the payoff under setup, and the emotional residue is the opposite—effort spent for nothing, which is a stronger predictor of churn than almost any UI flaw.

Core Tools, Techniques, and Practices (TTPs)

• Time to Value: Help people reach their first meaningful outcome with the least unnecessary effort
• Success Moments: Mark meaningful progress with feedback that feels earned, then let users decide what comes next
• Setup Defaults: Give users a credible starting point they can understand, change, or skip
• Empty States: Turn “nothing here” into a clear, useful next step
• Discovery: Guide users to value before they know where to look
• Personalisation: Make the product fit the user’s stated needs—without making assumptions they cannot inspect or change
• Micro Interactions: Small responses that make an action feel acknowledged, understandable, and complete
• Momentum Bias: Give people a genuine head start without taking the decision away from them

Supporting Tools, Techniques, and Practices (TTPs)

• Progressive Disclosure: Reveal the next useful layer of complexity when the user needs it, while keeping deeper capability easy to find
• JTBD Copywriting: Jobs-to-be-Done (JTBD) copy: write from the progress the user is trying to make, not the feature your product wants to describe
• Loading Feedback: Make unavoidable waits legible, calm, and proportionate
• Sandbox Experience: Let people experience a truthful slice of product value before asking them to commit
• Contact Bridge: Connect users to people they already know—without turning their address book into a growth hack

Insights & Metrics

Measure whether people reach real value—not whether they finished a tour.

1. Activation Rate
   • Formula: (Users who complete the defined activation action ÷ New users in cohort) × 100
   • What it measures: Share of new users who hit the milestone most tied to later retention
   • Why it matters: Signup and checklist completion are vanity; activation is the first signal the product worked
2. Time to Value (TTV)
   • Formula: Median time from first open (or signup) to first activation action
   • What it measures: How quickly users experience product benefit
   • Why it matters: Longer paths usually mean more drop-off; median beats mean when a few slow setups skew the average
3. Feature Adoption Rate (post-activation)
   • Formula: (Activated users who used feature X ÷ Activated users) × 100
   • What it measures: Whether first value deepens into the capabilities that sustain use
   • Why it matters: Activation without follow-on adoption often means a shallow “aha,” not a habit start
4. Activated vs Not — Early Retention
   • Formula: Compare Day 1 / 7 / 30 retention for activated vs non-activated users in the same signup cohort
   • What it measures: Whether your activation definition actually predicts return
   • Why it matters: If “activated” users do not retain better, redefine the action before polishing the funnel

Behind the Data

What’s blocking first value—and whether the milestone you track is the right one.

Define & validate activation

• Which candidate actions best predict Day 7 / 30 retention—and which are busywork?
• Do different jobs-to-be-done need different activation events?
• How does guided vs self-directed exploration change activation rate and TTV?

Friction before first value

• Where do users stall before the activation action (empty state, setup, permission, account wall)?
• Which defaults, empty states, or Sandbox paths produce the fastest TTV?
• Does asking for account or contacts before value correlate with lower activation?

After the aha

• What do users do in the same session after the first Success Moment—explore, leave, or hit a wall?
• Which features adopted within 24–72 hours best predict retention among activated users?
• Where does Discovery help—and where does it distract from the core job?

Further reading

• Getting Started: Driving Product Engagement by Obsessing Over Activation (Amplitude) — Define an aha/activation action and validate it against retention.
• What is Activation Rate for SaaS Companies? (Amplitude) — Clear framing of activation rate as a product-specific, retention-linked metric.
• Hook trial users from their first use (Intercom) — JTBD-led first-use design aimed at a real aha with minimal ask.
• Designing Empty States in Complex Applications (Nielsen Norman Group) — Empty states as status, learnability, and a direct path into key tasks.
• Progressive Disclosure (NN/g) — Reveal complexity when needed so first value is not buried under setup.

Agent skill

• Primary command / sequence: /productfeeling sequence — jobs → map → friction → states → delight → brief
• Core TTPs to load: Time to Value, Success Moments, Setup Defaults, Empty States, Discovery, Personalisation, Micro Interactions, Momentum Bias
• Supporting TTPs: Progressive Disclosure, JTBD Copywriting, Loading Feedback, Sandbox Experience, Contact Bridge
• When the agent should use this strategy: “activation rate”, “aha moment”, “time to value”, “signed up but inactive”, “first value”, “define activation event”
• Companion handoff: Impeccable — empty states, defaults, sandbox paths, and first-value feedback on named surfaces; DocSlime — when the activation definition or retention-linked milestone belongs in docs/strategy/ or docs/experience/; RedTeam — before committing to a vanity activation metric or contact-import gate (/redteam review on the proposed activation event)
• Feeling north star this strategy serves: clarity that the product works, with early competence
• Anti-goals: fake social proof, contact-book spam, sunk-cost traps, forcing tours before value, counting vanity events as “activated”
• Reference path: skill/reference/sequence.md