The prompt
Score 10 of 10, Excellent
Use it when You want to test a product idea by writing its launch announcement and its hardest questions before anyone builds it.
- {{audience}}
- {{idea}}
- {{customer_problem}}
- {{evidence}}
- {{constraints}}
Full prompt and why it works
Prompt
# Role You help a product team test an idea by writing its launch press release and FAQ before anything is built, in the working-backwards style. # Goal Write an internal draft press release and FAQ for the idea below, for {{audience}} to read before deciding whether to invest. The point is to find out whether the customer benefit is clear and real, so a weak spot the draft exposes is a useful result. # Success criteria - A customer could read the first paragraph and say what problem this solves for them. - Every claim about customers, numbers or results comes from the context below. - The FAQ asks what a skeptical executive and a skeptical customer would ask, including the uncomfortable questions about cost, risk and why now. # Constraints - Write the release as of launch day, in plain language with no hype words such as revolutionary or seamless. - Do not invent quotes from real people, statistics, prices, dates or partners. Where the release needs one, write a bracketed placeholder that says what evidence is needed, for example [customer quote: how a buyer in segment X would describe the time saved]. - Do not answer an FAQ question with a promise the context does not support; write "Unknown: [what we need to find out]" instead. # Output Use a Markdown heading for each of the four parts below. 1. Press release, under 400 words: headline, one-sentence subheading, the problem, the solution, a spokesperson quote (placeholder), how it works for the customer, a customer quote (placeholder), how to get started. 2. External FAQ: 5 questions customers would ask, with answers. 3. Internal FAQ: 8 questions the team and leadership would ask, covering cost, effort, risks, what we will not do, how we measure success, and why now. 4. Weak spots: up to 5 places where the draft had to rely on a placeholder or "Unknown", ranked by how much they put the idea at risk. # Stop rules If the context does not say who the customer is or what problem they have, ask for that before writing, because the release cannot be written without it. # Context Product idea: {{idea}} Target customer and their problem: {{customer_problem}} Evidence we have (research, data, requests): """ {{evidence}} """ Constraints we know about (budget, timing, technology): {{constraints}}
Variables
- {{audience}}
- Who decides, for example "the leadership team at the quarterly planning review".
- {{idea}}
- The product or feature idea, in one to three sentences.
- {{customer_problem}}
- Who the customer is and the problem they have today.
- {{evidence}}
- What you know so far: interview notes, data, requests, sales feedback. Write "none yet" if you have nothing.
- {{constraints}}
- Known limits on budget, timing or technology. Write "none known" if there are none.
Why it works
- If unsure. Missing evidence becomes a placeholder that names what is needed, so the gaps in the idea are visible instead of papered over with invented quotes.
- What good looks like. The first paragraph has to make the customer's problem clear on its own, which is the test the working-backwards method exists to apply.
- Layout. Markdown sections in the order OpenAI recommends (role, goal, success criteria, constraints, output, stop rules) with the pasted context last.