a builder's codex
codex · operators · Anuj Rathi · ins_three-divergent-pr-faqs

Bring three divergent PR-FAQs to a strategy decision, not one

By Anuj Rathi · VP Product (former Swiggy, Jupiter); product leader, India marketplaces · 2026-04-28 · podcast · Anuj Rathi on Full-Stack PM, Working Backwards, India Marketplace Dynamics — Lenny's Podcast

Tier A · TL;DR
Bring three divergent PR-FAQs to a strategy decision, not one

Claim

For ambiguous strategy decisions, prepare three press-release-and-FAQ documents — three different solutions to the same problem, each fully reasoned with named tradeoffs. Showing one path makes stakeholders feel railroaded. Showing three lets them choose, but their choice is constrained by the analysis you did.

Mechanism

A single recommendation forces stakeholders into binary "yes/no" — and "no" usually wins by default in large companies because risk is asymmetric. Three options force the decision into "which?" rather than "whether," which is a much easier conversation. The work of writing three options also shakes out lazy thinking: an option you can't make a credible PR-FAQ for probably wasn't a real option anyway.

Conditions

Holds when:

Fails when:

Evidence

"I really truly believe in the power of three... three press releases, alternative and divergent. When you show one roadmap, stakeholders feel unheard. When you show three well-thought divergent paths, they see their input incorporated but trade-off-analyzed."

— Anuj Rathi on Lenny's Podcast, 2026-04-28

The Amazon-derived working-backwards method centers a single PR-FAQ; Anuj's modification adds the divergence to handle politically loaded decisions in marketplace and growth contexts.

Signals

Counter-evidence

Bret Taylor and Brian Chesky both argue for clear founder/CEO conviction over committee-style choice menus. In smaller orgs with strong founders, three-options can devolve into "the leader picks the one they wanted anyway." Use this in orgs where the decision needs cross-functional buy-in, not in tight founder-led teams.

Cross-references

Open the interactive view → View original source → Markdown source →