working-backwards

To write a PR/FAQ for product validation, draft a fictional press release stating the customer benefit in plain language, then pair it with an external FAQ addressing customer doubts and an internal FAQ covering business feasibility, unit economics, and success metrics.

The working backwards method is a product strategy approach where you document the end-state customer experience through a press release and FAQ before any engineering starts, ensuring stakeholder alignment on what success looks like and preventing wasted build cycles.

To run a pre-mortem for a go/no-go decision, assume the product already failed, generate specific failure scenarios, score each by likelihood and impact, and then assign mitigation plans with owners and tripwires to monitor risks throughout development.

You need narrative decision-making and a PR/FAQ during feature discovery when proposing new products, drafting launch narratives, preparing executive memos, or conducting go/no-go risk stress tests to force clear customer value and hard questions before committing engineering resources.

Yes, you can use the working backwards approach for internal executive memos and stakeholder alignment because the structured PR/FAQ output serves as a decision-ready document that captures customer benefits, business case assumptions, and measurable success metrics for confident review.

The PR/FAQ and pre-mortem approach requires structured customer-benefit writing and rigorous business case assumptions, which can be time-consuming and may not fully capture rapidly shifting market dynamics or technical execution risks that emerge after the initial go/no-go decision.