working-backwards
Working Backwards (PR/FAQ)
A product development method pioneered at Amazon: start from the customer experience and work backwards to the technology. The centerpiece is the PR/FAQ document — a fictional press release and FAQ written before a single line of code, forcing clarity of thought about who benefits, why they care, and what could go wrong. Includes a built-in pre-mortem step based on Gary Klein's prospective hindsight technique.
Core Principle
If you can't write a compelling press release, you don't understand the product yet. Writing forces thinking. A PR/FAQ written at the start — not the end — of a project exposes fuzzy thinking, missing logic, and unjustified assumptions before any resources are committed. If the press release is boring, the product will be boring.
The Working Backwards process inverts the typical development flow:
Traditional: Idea → Build → Launch → Explain to customers
Amazon: Customer need → PR/FAQ → Debate → Build only if compelling
Scoring
Goal: 10/10. When reviewing a PR/FAQ or product proposal, rate it 0-10:
More from tomaszstaniak/pm-ai-skills
continuous-discovery-habits
Product discovery framework based on Teresa Torres'' "Continuous Discovery Habits". Use when you need to: (1) build an opportunity solution tree from desired outcomes, (2) identify and prioritize customer opportunities, (3) design assumption tests for product ideas, (4) structure customer interview snapshots, (5) map assumptions to experiments, (6) move from output-driven to outcome-driven product development, (7) map current-state customer experiences, (8) build a weekly discovery habit.
13good-strategy
Strategy evaluation and design framework based on Richard Rumelt''s "Good Strategy Bad Strategy" and Michael Porter''s "What Is Strategy?". Use when you need to: (1) evaluate whether a strategy is good or bad, (2) diagnose the core challenge before proposing solutions, (3) build a coherent strategy kernel (diagnosis + guiding policy + coherent actions), (4) stress-test strategic plans with pre-mortem analysis, (5) distinguish strategy from goals, ambitions, or wish lists.
10positioning-and-pitch
Framework based on April Dunford''s "Obviously Awesome" and "Sales Pitch". Use when you need to: (1) define or evaluate product positioning using the five-component framework, (2) translate positioning into a compelling pitch for stakeholders or buyers, (3) choose a market category strategy that shapes what you build and how you compete, (4) develop differentiated value claims that connect product decisions to market reality, (5) structure a pitch for exec reviews, board updates, or partner conversations, (6) diagnose why your product story isn''t landing with customers or internal stakeholders, (7) align cross-functional teams around a shared positioning narrative, (8) connect positioning decisions to roadmap priorities and feature trade-offs
6first-90-days
Leadership transition framework based on Michael D. Watkins'' "The First 90 Days". Use when you need to: (1) plan onboarding for a new leadership or management role, (2) build a 30-60-90 day plan, (3) diagnose the business situation you''re entering (STARS model), (4) plan critical early conversations with your new boss, peers, and team, (5) identify and avoid common transition traps, (6) accelerate time to value in a new role.
5escaping-build-trap
Product management framework based on Melissa Perri''s "Escaping the Build Trap". Use when you need to: (1) diagnose whether a team is stuck in the build trap (shipping features without outcomes), (2) shift from output-driven to outcome-driven product development, (3) evaluate product manager archetypes and team maturity, (4) design a product strategy that connects company vision to team-level decisions, (5) run a pre-mortem on a product roadmap to detect build-trap patterns.
5para-method
Personal knowledge management framework based on Tiago Forte''s "The PARA Method" and "Building a Second Brain". Use when you need to: (1) organize digital information into Projects, Areas, Resources, and Archives, (2) build a Second Brain for capturing and retrieving knowledge, (3) apply CODE methodology (Capture, Organize, Distill, Express), (4) design progressive summarization layers, (5) create actionable knowledge management systems, (6) connect knowledge to current projects, (7) reduce information overload through systematic organization.
2