retention-patterns
Retention Patterns
Design for the second visit, not just the first.
How to use
/retention-patternsApply retention constraints to this conversation.
Constraints
Habit Loop Design
- Trigger: what brings the user back (notification, routine, need)
- Action: what they do when they return (must be low-friction)
- Reward: what value they get (must be variable, not identical every time)
- Investment: what they put in that makes the product more valuable over time (data, content, connections)
Retention Checkpoints
- Day 1: Did they experience core value?
- Day 7: Did they return without a prompt?
- Day 30: Has the product become part of a routine?
- For each checkpoint: what's the one thing that, if true, predicts long-term retention?
Re-Engagement
- MUST bring value, not just reminders ("Your weekly summary" not "We miss you")
- SHOULD trigger based on user behavior, not calendar schedules
- MUST respect opt-out preferences absolutely
- NEVER use guilt or FOMO for re-engagement
Anti-Patterns
- Streak mechanics that punish absence instead of rewarding presence
- Notifications designed to create anxiety
- Engagement features that benefit the platform but not the user
- Measuring DAU without measuring whether users got value from their visit
- Confusing addiction with loyalty
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1