Future press release
Write the newspaper article about your finished product, to align the team on the outcome before anyone scopes anything.

- Time
- 50 min session, 15 min writing
- People
- 4–8 people
Overview
The board sets the scene: you are in a cafe with coffee and cake, reading the paper. Your product is in customers’ hands, the press release went out, and the paper picked it up. What does the article say?
Because a press release has to name who benefits and why they care, it forces out disagreements about the goal that a feature list lets you avoid. Nothing gets published — the artifact is the discussion you have while writing it.
When to use it.
Once framing has enough context to imagine a finished state, and before detailed scoping begins. It takes the top four to five voted How Might We statements from Assumption mapping as its input, so run that first.
Who to involve.
Four to eight, including the sponsor if they will engage with it. Writing in pairs works better than alone, because the differences between versions are the output.
Effort.
Low prep High engagement Only a small part of the session is writing — the rest is reading aloud and discussing the differences, which is the valuable part.
Outcomes.
An agreed articulation of what success looks like in customer terms, plus an explicit list of what the group did not agree on — carried into scoping as open questions rather than silences.
Recommendations.
Imagine an ideal world while writing, with abundant resources and no technical or financial constraints; they come back soon enough. Include a measured improvement, as the board asks — “30% increase in operational safety” beats “significantly safer” — and give it a rough date, so everyone knows how far into the future you are imagining. Ban internal language: no module names, no roadmap terms. If it cannot be said to a customer it does not belong in the release.
How to run it
Give everyone fifteen minutes to write all seven parts below, in the board’s own order, alone or in pairs.
Newspaper headline
Attention-grabbing, names the product you are about to build, and picks an imaginary launch day in the future.
Subheading
One sentence explaining the key benefit and its audience. The board’s pattern: [Company] launches [service] for [user type] that [solves problem / delivers benefit].
Introduction
A summary of what the product is and does, articulating the ambitious goals — what this means for users and for the business.
Problem
What problem exists in the world that you are trying to solve? Give examples of the struggles users endure without it, and illustrate the hurdles your team overcame.
Solution
How the service excels at solving the problem for the primary users. If secondary users exist, explain how it resolved their problems too.
Company quote
From the spokesperson or CEO, on why you created this and what it means for users and the business.
Customer quote
From a customer, on how the service has improved their life. The hardest and most useful part — if the quote is “it has more features”, the team does not yet agree on the value.
Read aloud and collate
Read every version aloud and capture where they disagree — that discussion is the valuable part. Then use Claude to collate and synthesise the group’s sentiments into three final articles, each written in the style of a different outlet — Medium, a daily newspaper and Bloomberg are good samples to prompt from. Keep all three as team artifacts.


