Description
A team writes the press release for a product as if it had already launched successfully, to define users, goals and timelines before building.
In a working backwards workshop the team writes a press release dated on a future launch day, describing a product or feature that has succeeded and is loved by users and critics. It includes stakeholder quotes and imagined user reviews, and states what problem it solved for users and how it contributed to their success. Writing the release forces early decisions: who the target users are, what goals the product meets for them, which business objectives it serves, and when it ships. Stakeholders can course-correct strategy while it is still cheap, and a dull release is itself a signal that objectives should be rethought. Amazon's fuller PR/FAQ adds a set of frequently asked questions that probe feasibility and risks. The release is built entirely on assumptions, which then need testing with users.
Attributes
- Discipline
- Design & Product Practice
- Loss type
- Active
- Goal
- Support a decision, Prioritise
- Stage
- Strategy
- Data
- Analytical / expert
- Effort
- Hours
Steps
- Gather the team and key stakeholders in a workshop and pick a plausible future launch date.
- Write a headline and a first paragraph naming the target user and the benefit.
- Describe the problem, the solution and how it changes users' success, in customer language.
- Add a stakeholder quote and imagined user reviews from blogs or app stores.
- Optionally add customer and internal FAQs probing feasibility, pricing and risks.
- Review the draft for timelines, target users, user goals and business objectives, and course-correct strategy.
- If the release is not exciting, rethink the objectives; otherwise list its assumptions for research.
Sources
- UX Decoded (Kanungo, 2022)
- An Elegant Puzzle (Larson, 2019)
Also known as
- Amazon working backwards
- Future press release
- PR/FAQ
Categories
- Design
- Design & Product Practice