Post-win review loop
Prompt users to review, learn, or share immediately after a positive outcome instead of assuming the best learning moment is after failure.
Why this can grow a startup
Albert Cheng shared that Chess.com discovered 80% of game reviews happened after wins, even though the team expected players to learn after losses. Reframing the experience around positive reinforcement increased review usage, subscriptions, and retention. The broader growth lesson is to place prompts where users feel capable, proud, or curious, not where the team thinks education should happen.
Source-backed example
Chess.com changed game review moments to surface brilliant moves and encouraging coaching after losses, then spread the positive-moment insight across adjacent product surfaces.
Source-reported evidence
Source: Lenny's Podcast transcript dataset · Browse Lenny's Podcast transcript dataset tactics
review or share actions after positive outcomes
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 21, 2026
When to use it
Use this when Referrals, Email, Communities is relevant to activation, retention, monetization and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Referrals and Email, using evidence from Lenny's Podcast transcript dataset as context—not as a promised result.
- Record a baseline for: Share of target users completing the product's first-value action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Connect activation, customer value, retention, and referral into one measurable loop.