A client needs to improve how new users or customers reach their first moment of value. Covers onboarding flow mapping, friction identification, aha-moment definition, activation metric design, and experiment planning for first-session conversion.
How it works
- You provide the product, current onboarding flow, activation data (if available), and retention curve
- The skill maps the onboarding flow, audits for friction, identifies the aha moment, defines activation metrics, and builds an experiment roadmap for improving first-session conversion
- It returns an activation strategy with prioritized experiments and benchmark targets Kate can use for product and growth conversations
Prompt
You are building an activation optimization strategy for a Kate Makrigiannis consulting engagement. Kate uses this to help clients stop losing new users before they ever experience the product's value. Activation is the hinge between acquisition and retention: get it right and the entire growth model improves; get it wrong and no amount of acquisition spending compensates. Before writing, read knowledge/voice-tone-guide.md -- use the client-facing voice.
Inputs I will provide:
- Product: {{PRODUCT}} (what the product is, business model, user type, current stage)
- Current onboarding flow: {{ONBOARDING}} (step-by-step description of what happens from signup through first value -- e.g., "signup form > welcome email > dashboard > no guidance after that," or "3-step wizard > template selection > first project creation")
- Activation data (if available): {{DATA}} (any metrics on onboarding completion, feature adoption, time-to-first-action -- e.g., "40% complete onboarding, 15% create a project in first session," or "we do not track this yet")
- Retention curve: {{RETENTION}} (how well users retain after activation -- e.g., "users who create a project in week 1 retain at 60% vs. 15% for those who do not," or "we see ~30% month-1 retention overall, not segmented by activation")
- Context (optional): {{CONTEXT}} (known friction points, team capacity, upcoming changes, competitive onboarding comparisons, user feedback)
Step 1: Onboarding flow map and friction audit
Map every step of the current onboarding experience and evaluate friction at each point:
Current Onboarding Flow
| Step # | Step | Action Required | Time to Complete | Friction Level | Drop-off Estimate |
|---|---|---|---|---|---|
| 0 | [Signup/Registration] | [e.g., Email + password + company name] | [X seconds/minutes] | [Low / Medium / High] | [X% estimated or actual] |
| 1 | [e.g., Email verification] | [Click link in email] | [Depends on email delivery] | [Friction level] | [Drop-off] |
| 2 | [e.g., Welcome screen / Onboarding wizard] | [Select role, use case] | [X time] | [Level] | [Drop-off] |
| 3 | [e.g., First core action] | [Create first X, invite team, connect integration] | [X time] | [Level] | [Drop-off] |
| 4 | [e.g., Value moment] | [See result, get insight, complete workflow] | [X time] | [Level] | [Drop-off] |
Friction Audit
For each step rated Medium or High friction:
| Step | Friction Type | Specific Issue | Severity | Fix Complexity |
|---|---|---|---|---|
| [Step #] | [Cognitive / Effort / Anxiety / Technical] | [What exactly causes friction] | [High / Medium / Low] | [Quick fix / Medium effort / Major redesign] |
| [Step #] | [Friction type] | [Issue] | [Severity] | [Complexity] |
Friction type definitions:
- Cognitive: User does not understand what to do or why
- Effort: User knows what to do but it requires too many steps or too much time
- Anxiety: User hesitates because of uncertainty, risk, or trust concerns (e.g., entering payment info, granting permissions)
- Technical: Bugs, slow loading, compatibility issues, broken flows
Unnecessary steps to eliminate
| Step | Why It Exists | Why It Should Go | Impact |
|---|---|---|---|
| [Step] | [Historical reason or assumption] | [It adds friction without adding value to the user] | [Removing it reduces time-to-value by X minutes / eliminates X% drop-off] |
Step 2: Aha-moment identification
The aha moment is the action or experience where the user first understands the product's value. It is the moment that predicts retention.
Aha-Moment Candidates
| Candidate Action | Hypothesis | Supporting Evidence | Retention Correlation |
|---|---|---|---|
| [e.g., "Created first project"] | [Users who create a project understand the core value] | [If data available: "Users who create a project in Day 1 retain at X% vs. Y%"] | [Strong / Moderate / Weak / Unknown] |
| [e.g., "Invited a team member"] | [Collaboration unlocks the real value] | [Evidence or hypothesis] | [Correlation] |
| [e.g., "Saw first result/insight"] | [Seeing output demonstrates ROI] | [Evidence] | [Correlation] |
| [e.g., "Completed first workflow end-to-end"] | [Full cycle shows the product works] | [Evidence] | [Correlation] |
How to validate the aha moment
If the client has data:
- Segment retained users (90-day retention) vs. churned users
- Look backward: what actions did retained users take in their first session/week that churned users did not?
- Find the action with the strongest correlation to retention
- Validate with a larger sample and control for confounders (e.g., power users do everything more, so the action may be a symptom, not a cause)
If the client lacks data:
- Interview 5-10 retained users: "When did you realize this product was worth using?"
- Interview 5-10 churned users: "What were you hoping to accomplish? Where did you get stuck?"
- Map responses to specific product actions
- Start tracking the candidate actions and revisit in 4-6 weeks
Recommended aha moment: [Action] because [strongest evidence or reasoning].
Step 3: Time-to-value analysis
Time-to-Value Measurement
| Metric | Current | Target | Benchmark |
|---|---|---|---|
| Time from signup to aha moment | [X minutes/hours/days] | [X -- target reduction] | [Industry benchmark if available] |
| Steps from signup to aha moment | [X steps] | [X steps] | [Benchmark] |
| Sessions to aha moment | [X sessions] | [X sessions -- ideally 1] | [Benchmark] |
| % reaching aha moment in first session | [X%] | [X%] | [Benchmark] |
| % reaching aha moment in first week | [X%] | [X%] | [Benchmark] |
Time-to-value reduction opportunities
| Opportunity | Current Time | Potential Time | How | Priority |
|---|---|---|---|---|
| [e.g., Pre-populate with sample data] | [10 min to first insight] | [30 seconds] | [Show value immediately with demo data while user sets up their own] | [P1] |
| [e.g., Reduce signup fields] | [2 min signup] | [30 sec signup] | [Remove company name, defer to onboarding] | [P1] |
| [e.g., Guided first action] | [User figures it out alone] | [Wizard walks through it] | [Interactive onboarding flow pointing to first action] | [P2] |
| [e.g., Skip email verification upfront] | [Wait for email, often minutes] | [Instant access] | [Verify email later, let them start immediately] | [P1] |
Step 4: Activation metric definition
Primary Activation Metric
| Component | Definition |
|---|---|
| Metric name | [e.g., "Activated user"] |
| Definition | [Precise definition -- e.g., "User who creates at least one project AND invites at least one team member within 7 days of signup"] |
| Why this definition | [Ties to aha moment, predicts retention, actionable by the team] |
| Measurement | [How to compute -- data source, query logic, tool] |
| Current rate | [X% of signups reach this milestone] |
| Target rate | [X% -- with rationale for the target] |
Leading Indicators
These predict whether a user will activate and allow earlier intervention:
| Indicator | Threshold | Predictive Value | Action if Below Threshold |
|---|---|---|---|
| [e.g., Completed onboarding wizard] | [Yes/No within 24 hours] | [Users who complete: X% activate. Who skip: Y%] | [Trigger onboarding reminder email] |
| [e.g., First core action attempted] | [Within first session] | [Predictive value] | [Action] |
| [e.g., Returned for second session] | [Within 48 hours] | [Predictive value] | [Action] |
| [e.g., Connected an integration] | [Within 7 days] | [Predictive value] | [Action] |
Activation metric guardrails
Metrics that must not degrade while optimizing activation:
| Guardrail | Threshold | Why |
|---|---|---|
| [e.g., Support ticket rate] | [Should not increase by more than X%] | [Faster activation should not come at the cost of confused users flooding support] |
| [e.g., 30-day retention of activated users] | [Should stay above X%] | [If activation rate rises but retention drops, the activation metric is wrong] |
| [e.g., Revenue per user] | [Should not decrease] | [Lowering barriers should not attract non-paying users exclusively] |
Step 5: Experiment roadmap
Activation Experiments
| Priority | Experiment | Hypothesis | Metric | Expected Impact | Effort | Duration |
|---|---|---|---|---|---|---|
| P1 | [e.g., Reduce signup to email-only] | [Fewer fields = more signups reaching onboarding] | [Signup-to-onboarding conversion] | [+X% conversion] | [Small] | [1-2 weeks] |
| P1 | [e.g., Add interactive onboarding wizard] | [Guided flow increases aha-moment completion] | [% reaching aha moment in session 1] | [+X%] | [Medium] | [2-4 weeks] |
| P2 | [e.g., Pre-populated demo workspace] | [Showing value before setup reduces time-to-value] | [Time to first value moment] | [-X minutes] | [Medium] | [2-3 weeks] |
| P2 | [e.g., Day-1 email with quick-start video] | [Async education drives second-session return] | [Day-2 return rate] | [+X%] | [Small] | [1 week] |
| P3 | [e.g., Personalized onboarding by use case] | [Relevant path increases completion] | [Onboarding completion rate] | [+X%] | [Large] | [4-6 weeks] |
| P3 | [e.g., Social proof during onboarding] | [Seeing others succeed reduces anxiety] | [Onboarding completion] | [+X%] | [Small] | [1 week] |
Experiment sequencing
- Weeks 1-4: Run P1 experiments (quick wins, high impact)
- Weeks 5-8: Run P2 experiments (moderate effort, clear hypotheses)
- Weeks 9-12: Run P3 experiments (larger bets, dependent on earlier learnings)
Minimum sample sizes
For each experiment, estimate the required sample:
| Experiment | Baseline Rate | Minimum Detectable Effect | Required Sample (per variant) | Time to Reach Sample |
|---|---|---|---|---|
| [Experiment 1] | [X%] | [X percentage points] | [N users] | [X days at current signup volume] |
| [Experiment 2] | [X%] | [X points] | [N users] | [X days] |
Show the math: "To detect a 5 percentage-point improvement from a 20% baseline at 95% confidence and 80% power, each variant needs approximately 1,030 users. At 100 signups/day, that is ~21 days per variant."
Step 6: Activation funnel benchmarks
Benchmark Ranges
| Metric | Poor | Below Average | Average | Good | Excellent | Client Current |
|---|---|---|---|---|---|---|
| Signup completion | <50% | 50-65% | 65-80% | 80-90% | >90% | [X%] |
| Onboarding completion | <20% | 20-40% | 40-60% | 60-75% | >75% | [X%] |
| Aha-moment reach (Day 1) | <10% | 10-25% | 25-40% | 40-60% | >60% | [X%] |
| Aha-moment reach (Week 1) | <15% | 15-35% | 35-55% | 55-70% | >70% | [X%] |
| Day-1 return rate | <15% | 15-25% | 25-40% | 40-55% | >55% | [X%] |
| Week-1 retention | <10% | 10-20% | 20-35% | 35-50% | >50% | [X%] |
Kate's Talking Points
- "Right now [X%] of your signups reach the aha moment. That means [100-X%] of your acquisition spend is wasted on users who never experience the product's value."
- "The biggest friction point is [step] where you lose an estimated [X%] of users. Fixing that alone could increase activation by [X%], which compounds into [X] additional retained users per month."
- "Your activation metric should be [definition]. Users who hit this milestone retain at [X%] vs. [Y%] for those who do not. Every improvement to this number multiplies the value of your acquisition spend."
Related skills: Uses
/plg-readiness-checkfor evaluating whether the product supports self-serve activation. Feeds into/funnel-analysisfor detailed conversion analysis at each activation stage. Pairs with/growth-model-builderfor modeling the downstream revenue impact of activation improvements.
Example Output
Input
- Product: Harlo — a B2B SaaS tool for HR teams at mid-market companies (250–2,500 employees) that automates employee onboarding paperwork, e-signature collection, and new-hire task checklists. Monthly subscription, $299–$799/mo depending on employee count. Currently 1,200 paying customers, growing ~18% MoM on signups but seeing high early churn.
- Current onboarding flow: Signup form (name, work email, company name, company size, HR software they currently use) → email verification → 6-question role-configuration survey → empty dashboard with tooltip tour (skippable) → prompted to "Build your first onboarding template" (blank canvas) → invite teammates → connect HRIS integration (BambooHR, Workday, etc.)
- Activation data: 78% complete email verification. 61% complete the role-configuration survey. 34% start the template builder. 18% complete a template. 9% connect an HRIS integration in the first session. We do not track whether users who complete a template retain better than those who do not.
- Retention curve: Overall month-1 retention is 28%. Anecdotally, customers who go live with their first real new-hire (i.e., use Harlo to onboard an actual employee) retain at ~80%+ through month 3. We have not segmented activation cohorts systematically.
- Context: User interviews surfaced that the blank template canvas is the biggest complaint — new HR managers say they "don't know where to start." A competitor (Trainual) offers a large template library on signup. Engineering can ship small–medium features in 2-week sprints. A new template library (15 pre-built templates by industry/company size) is already in development and 3 weeks from release.
Output (abbreviated)
Activation Optimization Strategy
Harlo — HR Onboarding Automation
Prepared for Kate Makrigiannis Consulting
Step 1: Onboarding Flow Map & Friction Audit
Current Onboarding Flow
| Step # | Step | Action Required | Time to Complete | Friction Level | Drop-off Estimate |
|---|---|---|---|---|---|
| 0 | Signup form | Name, work email, company name, company size, current HR software | ~2.5 min | Medium | ~10% |
| 1 | Email verification | Click link in email | 1–5 min (inbox dependent) | High | ~22% |
| 2 | Role-configuration survey | Answer 6 questions about HR workflows and team structure | ~3 min | Medium | ~17% |
| 3 | Tooltip tour | Watch or skip a 7-step dashboard walkthrough | ~2 min (if completed) | Low | ~5% estimated (skip rate ~70%) |
| 4 | Template builder | Build first onboarding template from a blank canvas | ~15–25 min | High | ~47% |
| 5 | Invite teammates | Enter colleague emails | ~1 min | Low | ~10% estimated |
| 6 | HRIS integration | Connect BambooHR, Workday, etc. via OAuth | ~3–5 min | High | ~50%+ of those who reach it |
Cumulative loss: Of 100 signups, approximately 9 reach a connected integration — and only 18 complete even a single template.
Friction Audit
| Step | Friction Type | Specific Issue | Severity | Fix Complexity |
|---|---|---|---|---|
| 1 — Email verification | Effort + Technical | Interrupts momentum immediately after signup; email delivery delays cause 20%+ abandonment before the user sees the product | High | Quick fix |
| 2 — Role-configuration survey | Cognitive | 6 questions is too many before the user has seen any value; purpose of the survey is unclear to users | Medium | Quick fix |
| 4 — Template builder | Cognitive + Effort | Blank canvas with no scaffolding forces users to invent their own onboarding process from scratch; HR managers are practitioners, not content designers | High | Medium effort (but library is already in dev) |
| 6 — HRIS integration | Anxiety + Effort | Asking for system-level OAuth access before the user trusts the product triggers hesitation; IT involvement often required, killing same-session completion | High | Medium effort |
Unnecessary Steps to Eliminate
| Step | Why It Exists | Why It Should Go | Impact |
|---|---|---|---|
| Email verification (upfront) | Reduce spam signups | Adds a hard stop before users see any value; can be moved to when they first invite a new hire or teammate | Removing it closes the 22% drop-off at Step 1; gate it downstream instead |
| Questions 4–6 of role survey | Personalization data for sales team | Users don't benefit from answering them; sales can collect this data in the first success call | Reduces survey time by ~50%, increasing completion from 61% to an estimated 75–80% |
Step 2: Aha-Moment Identification
Aha-Moment Candidates
| Candidate Action | Hypothesis | Supporting Evidence | Retention Correlation |
|---|---|---|---|
| Completed a template | User sees the full structure of an onboarding program they could use tomorrow | 18% of signups reach this; month-1 retention not yet segmented by this action | Unknown — must instrument immediately |
| Sent first real new-hire onboarding packet | User sees Harlo working in production; new hire receives and signs documents | Anecdotal: ~80%+ month-3 retention for users who reach this milestone | Strong (anecdotal) |
| Previewed a completed template (new) | User sees what a finished product looks like before committing effort | Hypothesis only; not currently possible with blank canvas | Unknown |
| Invited a teammate | Collaboration increases stickiness | No data; likely a leading indicator rather than the aha moment itself | Weak/Unknown |
Recommended aha moment: "Sent first real new-hire onboarding packet" — meaning an HR user creates a template AND sends it to an actual employee who opens it. This is the moment Harlo stops being software and becomes a workflow. The anecdotal 80% month-3 retention for users who reach this milestone dwarfs the 28% overall retention. Every upstream fix should be measured against whether it moves more users to this event.
Secondary aha moment (faster to reach): "Previewed a completed, pre-built template" — the new template library creates an opportunity to show value in under 60 seconds. This becomes the in-session proof point while the user works toward the primary aha moment.
How to Validate
Since cohort data isn't yet segmented by activation actions:
- Instrument immediately: Tag
template_completed,packet_sent,new_hire_opened_packetevents in your analytics tool (Mixpanel or equivalent) - Retroactive cohort pull: Query existing customers — separate the ~80% month-3 retainers and confirm what actions they took in week 1
- Interview 8 churned users from months 1–2: "What were you trying to get done the day you signed up? Where did you get stuck?"
- Revisit correlation data in 6 weeks once tagging is live
Step 3: Time-to-Value Analysis
Time-to-Value Measurement
| Metric | Current | Target | Benchmark |
|---|---|---|---|
| Time from signup to completed template | ~3–5 days (most don't return same session) | Same session, under 20 min | 10–15 min for comparable workflow tools |
| Steps from signup to completed template | 6 steps | 3 steps | 3–4 steps |
| Sessions to aha moment | 2–4 sessions estimated | 1 session | 1 session |
| % reaching completed template in first session | ~18% | 45% | 35–50% for strong B2B onboarding |
| % sending first packet within 7 days | Unknown (not tracked) | 25% | N/A — establish baseline first |
Time-to-Value Reduction Opportunities
| Opportunity | Current Time | Potential Time | How | Priority |
|---|---|---|---|---|
| Pre-built template library (in dev) | 15–25 min to build blank | 2–3 min to customize a template | User selects industry + company size → pre-populated template ready to edit | P0 — ship and instrument |