Product & planning21 categories
Why would nobody come back?
Before building something you assume people will love.
Why would someone try this once and never come back? Give me three reasons, most likely first.
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Discovery and evidence. Checking the idea before you commit: research, feedback, competitors, risky assumptions, success metrics.
Related prompts
Define success metrics for this featureBefore you build, so you're not inventing a metric afterwards to look good.Find the riskiest assumptionBefore committing a quarter to a plan that rests on something untested.Design user interview questionsYou have five research calls booked and one chance to not lead the witness.Synthesise raw feedback into themesA pile of interview notes, survey answers or reviews and no pattern yet.Tear down a competitor's productUnderstanding a rival properly, beyond "they have more features than us".Turn support tickets into product insightSupport volume is telling you something and nobody has read it as a whole.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free