Convert vague feedback into testable problem statements
Translate fuzzy stakeholder complaints into precise, observable root problems with clear metrics and validation tests.
You getExtracted Core Symptoms, unverified Assumptions and testable Problem Statement
Prompt
Act as a senior product discovery and systems analyst. Transform the vague stakeholder complaints provided below into structured, testable problem statements.
- Separate observable symptoms from emotional venting, assumed solutions, and hearsay.
- Identify the affected user group and the specific step in their workflow that breaks.
- Formulate a falsifiable problem statement stating who, what barrier occurs, and the measurable business impact.
- Define one rapid test to prove or disprove the problem before committing engineering or operational resources.
Output format:
- Extracted Core Symptoms (bullet points)
- Unverified Assumptions (bullet points)
- Testable Problem Statement (single structured paragraph)
- Validation Experiment (hypothesis, metric, pass/fail threshold)
My stakeholder notes are below:Example output
Paste raw survey responses, meeting transcripts, or stakeholder emails at the bottom of the prompt in Claude, ChatGPT, or Gemini. Ask the model to suggest three discovery interview questions to run with users as a follow-up.
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
Frame stakeholder trade-offs using an if-then constraint matrix
Turn impossible project demands into clear trade-off choices across scope, speed, and budget so leadership makes realistic commitments.
Check project forecasts against realistic base rates
Stress-test internal projections against historical industry base rates to neutralize planning fallacy and timeline optimism.
Create a weighted multi-criteria decision matrix
Compare complex options objectively by generating clear evaluation criteria, weights, and a scoring rubric.
Draft a calm devil's advocate brief
Create structured, non-defensive questions to stress-test popular proposals. Use this to surface blind spots in upcoming team discussions without sounding confrontational.
Identify perverse incentives in a proposed policy
Expose unintended consequences, metric gaming, and perverse incentives hidden inside proposed rules. Perfect for managers drafting new KPIs or policies.
Map branching root causes for multi-factor incidents
Analyze systemic breakdowns across parallel technical, operational, and communication branches instead of relying on a single 5 Whys chain.
- Red-team a strategic proposal to expose fatal flaws
- Separate actionable leading indicators from vanity metrics
- Separate negotiating positions from underlying stakeholder interests
- Separate verified facts from guesswork in incident reports
- Check an argument for cherry-picked statistics
- Design a cheap low-risk test before committing