Great — let's run a structured brainstorm on improving day-2 retention. ## Step 1: Problem Focusing Let me reframe this as a How Might We statement: **HMW**: "How might we make new users find enough value on Day 1 so that they return on Day 2?" Before I diverge, a few quick clarifying questions: 1. Who are your new users? (Casual browsers, power users, mobile-first?) 2. What's the current onboarding flow? (Guided tour? Self-serve?) 3. Any known drop-off points? (After signup? After first action?) If you don't have specifics, I'll proceed with general product logic and flag where real data would sharpen the ideas. ## Step 2: SCAMPER Divergence (7 ideas) | # | Perspective | Idea | |---|------------|------| | 1 | **Substitute** | Replace email-based onboarding with in-app interactive walkthrough — no "read this guide", instead "do this now" | | 2 | **Combine** | Merge the "aha moment" with the signup flow — show a personalized result before asking for full profile | | 3 | **Adapt** | Borrow Duolingo's streak mechanic — give users a Day 1 streak badge and make Day 2 feel like "don't break the chain" | | 4 | **Modify (10× smaller)** | What if Day 1 had only ONE action? Strip everything except the single highest-value feature | | 5 | **Put to other uses** | Turn the empty state into a social proof wall — "847 users did this today" | | 6 | **Eliminate** | Remove the 5-step signup. One field (email or phone), everything else is progressive profiling | | 7 | **Reverse** | Let users experience the product BEFORE signup — guest mode with save-on-exit prompt | ## Step 3: 5 Why Root Cause Dive **Pain point**: 82% of users don't return on Day 2 - **Why 1**: They didn't accomplish their goal on Day 1 - **Why 2**: The core action takes too many steps - **Why 3 (root cause)**: Onboarding is designed around product features, not user tasks - **Solution**: Rebuild onboarding around the #1 user task, not the feature menu ## Step 4: Constraint Innovation | Constraint | Idea | |-----------|------| | **Zero dev cost** | Send a personalized Day 1 evening email: "Here's what you started — pick up where you left off" with a deep link | | **1 line of code** | Add a progress bar to the onboarding — "You're 60% done" — completion bias drives returns | ## Step 5: Reverse Brainstorm | Make it WORSE | Flip to IMPROVE | |--------------|----------------| | Send no follow-up after signup | Send a timed push at the user's typical active hour on Day 1 evening | | Make users re-discover the core feature every time | Pin the core action to a persistent bottom nav bar | | Show a blank dashboard on return | Show a "Welcome back — here's what's new since you left" summary | ## Step 6: Impact/Effort Screening | Quadrant | Ideas | |----------|-------| | **Quick Wins** (High Impact, Low Effort) | Day 1 evening email with deep link · Progress bar on onboarding · Guest mode with save-on-exit | | **Big Bets** (High Impact, High Effort) | Rebuild onboarding around user tasks · In-app interactive walkthrough · Streak mechanic | | **Fill-ins** (Low Impact, Low Effort) | Social proof wall · "Welcome back" summary | | **Money Pits** (Low Impact, High Effort) | Full feature menu restructure on Day 1 | ## Top 3 Recommendations 1. **Day 1 Evening Email** — Quick Win, zero dev cost, expected +5–8% day-2 retention. Test with a 10% cohort first. 2. **Guest Mode with Save-on-Exit** — Quick Win, moderate effort but high leverage. Lets users feel value before committing. 3. **Task-Based Onboarding Rebuild** — Big Bet, requires UX research + redesign, but addresses the root cause. Expected +10–15% retention if done right. Want me to go deeper on any of these, or shall we move to a PRD for the top pick?