divergent-working-backwards
Divergent Working Backwards (3 PR/FAQs)
Overview
An enhancement of Amazon's "Working Backwards" process. Instead of writing one Press Release, the team writes three distinct, divergent PRs to explore different strategic directions before converging.
Core principle: Power of Three—always explore three radically different solutions.
The Process
┌─────────────────────────────────────────────────────────────────┐
│ 1. DEFINE THE CUSTOMER PROBLEM │
│ What are we solving? │
├─────────────────────────────────────────────────────────────────┤
│ 2. IDEATE 3 DIVERGENT SOLUTIONS │
│ NOT variations—strategic alternatives │
│ Example: Tiered vs. Points-based vs. Segment-focused │
├─────────────────────────────────────────────────────────────────┤
│ 3. DRAFT 3 DISTINCT PR/FAQs │
│ Full press release for each future │
│ Include compliance, legal, ops details │
├─────────────────────────────────────────────────────────────────┤
│ 4. STAKEHOLDER REVIEW & DEBATE │
│ Compare the 3 futures │
│ Force real trade-off discussions │
├─────────────────────────────────────────────────────────────────┤
│ 5. SELECT ONE PATH & COMMIT │
│ Disagree and commit once chosen │
└─────────────────────────────────────────────────────────────────┘
Key Principles
| Principle | Description |
|---|---|
| Divergence first | Prevents falling in love with first idea |
| Show don't tell | Write full PR/FAQ, not just bullet points |
| Leadership choice | Give real options, not yes/no on single plan |
| Commit after debate | Once chosen, full commitment |
Common Mistakes
- Writing three variations that are only slightly different
- Not pushing to truly divergent strategic alternatives
- Skipping the full PR/FAQ detail for each option
Source: Anuj Rathi (Jupiter Money, Swiggy) via Lenny's Podcast
More from coowoolf/insighthunt-skills
gardening-mindset
Use when dealing with ecosystems, network effects, or high-uncertainty environments where the right answer cannot be known in advance, when rigid planning consumes more value than it creates
45gamification-triad
Use when designing retention mechanisms, habit loops, or auditing why users drop off despite engaging with core features, to structure gamification beyond superficial badges
44three-layer-agent-stack
Use when building AI-powered products or agents, when raw model intelligence isn't enough to solve user problems, or when designing the architecture for agentic workflows
15minimum lovable product (mlp)
In an era where AI lowers the cost of building software, viability is obsolete. The differentiator is joy and emotional connection. Prioritize "Wow" over "Aha"—brand is product interaction.
14curiosity-loops
Use when facing a significant decision (career pivot, product direction, technical choice) and feeling stuck or indecisive, when seeking contextual advice rather than generic recommendations
13pre-mortem-kill-criteria
Use before launching products or signing contracts, when needing to combat sunk cost fallacy, or when standard pre-mortems fail to change behavior
13