Reframe a feature request into a core user problem
Break down prescriptive feature requests into underlying user motivations, workflow bottlenecks, and testable problem statements.
You getSurface Request, core User Problem and underlying Jobs to Be Done
Prompt
You are a product discovery specialist. Help me analyze a prescriptive solution request from a stakeholder or customer and extract the root user problem.
Rules:
- Deconstruct the requested feature into the underlying user goal, trigger, and friction point.
- Focus on workflow outcomes rather than user interface components.
- Propose two alternate approaches that solve the real problem without building the exact requested widget.
- State clearly what customer assumptions need validation.
Output format:
1. Surface Request: One-sentence summary of what was asked for.
2. Core User Problem: A standard problem statement (When [trigger], users struggle to [goal] because [blocker]).
3. Underlying Jobs to Be Done: 2 concise job statements.
4. Alternative Exploration Paths: 2 lightweight product or workflow alternatives.
5. Discovery Questions: 3 questions to ask users to validate the problem.
Here is the feature request:Example output
Paste feature requests from customers, executives, or sales teams directly into ChatGPT, Claude, or Gemini. For deeper discovery, ask the model to generate an interview script targeting the discovery questions.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Draft a Zero-to-One Product Discovery Experiment Card
Generates a structured, one-page test card with a falsifiable hypothesis, cheap validation test, and numeric kill threshold for new features.
Write a Customer Interview Script That Validates a Problem with Past-Behavior Questions
Get a 30-minute problem-discovery interview script with past-behavior questions, two follow-up probes each, banned-question rewrites and evidence signals.
Analyze customer feedback using Jobs to Be Done
Extract functional, emotional, and social customer drivers from raw user feedback. Use this to separate true user motivations from reactionary feature requests.
Draft Multi-Tier SaaS Product Packaging and Feature Matrix
Generate a clear, competitive feature matrix for your SaaS product that aligns tiered capabilities with specific user upgrade triggers.
Synthesize User Interview Notes into Counted Themes and Insights
Turns raw interview notes into a ranked theme table showing how many participants raised each theme, with observations kept separate from interpretation.
Draft a working-backwards press release and FAQ
Write an Amazon-style press release and hard FAQ to clarify customer value and address tough technical questions before writing code.
- Transform Customer Interview Transcripts into Ranked Pain-Point Matrix
- Classify onboarding drop-offs into cognitive and value friction
- Schedule phased customer communications for feature sunsetting
- Break a product epic into vertical MVP slices
- Decline a stakeholder feature request diplomatically
- Turn a Vague Founder Request into a Scoped Problem Brief with Trade-Offs