aws-one-way-door
Amazon Working Backwards with one-way-door ceremony — for hard-to-reverse decisions (typically new product lines, public commitments, major investments). Starts with the human-authored Press Release (the founding artifact), stress-tests it with the FAQ, and requires the 6-pager decision narrative before build spend. Optional post-FAQ deepening: MRD (market validation, product scale) or OpportunitySpec (discovery, feature scale) — the door sets the ceremony; the scale picks the tool.
Specs in This Workflow
Synthesis Rules
How downstream specs are generated from upstream ones.
Extract Business Model Canvas blocks from MRD. Focus on customer obsession and working backwards.
Challenge the press release's assumptions ruthlessly. Include customer questions, internal stakeholder questions, and the business case: market, economics, why now, feasibility.
Deepen and validate the FAQ's business-case answers with market evidence: segments, sizing, competition, positioning.
Amazon 6-pager format for the one-way-door decision meeting. Data-driven narrative, no slides.
Populate the 12-box OpportunitySpec canvas from the Press Release and FAQ. Flag boxes the source documents leave unanswered — those are the discovery gaps.
Derive product requirements from the announced customer experience (press) and its stress-tested constraints (FAQ), grounded in whichever optional deepening is present: market validation (MRD, typical at product scale) or the discovery canvas (OpportunitySpec, typical at feature scale).
Human-authored founding artifact — not synthesized. Write the press release first; everything else works backward from it.
Test plan covering all PRD requirements with traceability, including UX acceptance flows.
Methodology Principles
Feeds Execution Via
Included Assets
15 document templates · 13 LLM-as-a-Judge rubrics — embedded in visionspec.