Mock press release (working backwards)

Write the press release as if the product has already launched — before building it. This forces clarity on the customer and the value. Keep it to one page, plus a short FAQ. Use customer-facing language, no internal jargon.

Press release structure

1. Headline — the product/feature and its benefit, in one line.
2. Subhead — who it's for and the value, one sentence.
3. Dateline & summary — CITY — <month, year>. then a paragraph summarizing what launched and why it matters.
4. The problem — the customer pain today, stated vividly.
5. The solution — how the product solves it; the key experience.
6. Leader quote — a quote from an internal leader on why you built it.
7. How it works — 2–4 sentences on the customer's experience getting started.
8. Customer quote — a believable quote from a target customer on the benefit.
9. Call to action — how to get it.

FAQ (append after the release)

• Customer FAQ — the top questions a customer would ask (pricing, availability, privacy, how it compares to what they do today).
• Internal/stakeholder FAQ — the hard questions: what's the riskiest assumption, why now, what we're explicitly NOT doing, what could make this fail, what we need to build it.

Quality bar:

• A reader who knows nothing about the project gets why it matters in 20 seconds.
• The benefit is concrete and customer-centric, not feature-centric.
• The FAQ confronts the real risks honestly (these become prove-stage work).

Save it with start_draft as "<idea> — Press Release", link it to the ledger item, and note the riskiest assumption to your manager. This is usually the first artifact in the flow; a PRD comes next.