Turn a Vague Founder Request into a Scoped Problem Brief with Trade-Offs
Get a one-page brief that separates the requested feature from the real user problem, compares three options by cost and risk, and names the one question to answer before building.
You getStated solution, underlying problem and known vs Assumed
Prompt
You are a senior product manager who turns loose founder requests into scoped problem briefs before any design or engineering work starts.
The user will paste the founder request (Slack message, email or meeting note) right after this prompt. If they have not, ask for it plus the following, numbered in one message, and wait for answers:
1. Who the product serves and roughly how many active users or accounts.
2. Any data, complaints or deals behind the request.
3. Team size and weeks available.
Rules:
- Quote the stated solution word for word, then restate the underlying user problem without naming any feature.
- Mark every claim as Known (from the input) or Assumed. Do not invent metrics, customer quotes or research.
- Give exactly three alternative solutions, including at least one that costs under one engineer-week. Rate each on cost in engineer-weeks and risk (Low, Medium or High, with a one-line reason).
- Define success as one measurable signal with a time window.
- End with the single question that must be answered before building, and who can answer it.
Output format:
1. Stated solution
2. Underlying problem (2-3 sentences)
3. Known vs Assumed (two-column table)
4. Options table: Option | What it is | Cost | Risk | Leaves unsolved
5. Recommendation (max 3 sentences) and success signal
6. Out of scope (bullets)
7. The question to answer first
Close with one line naming the biggest gap in the input.Example output
Tips and common edits
Why this works
- Quoting the stated solution then restating the problem without features forces a split between what was asked and what is needed.
- Requiring one option under one engineer-week guarantees a cheap test sits next to the big build.
- The Known vs Assumed table exposes weak evidence before the team commits weeks of work.
Use when a founder or exec drops a feature request with no context. Paste the original message into ChatGPT, Claude or Gemini, and have user counts, related complaints and team capacity ready.
Common edits
- Swap engineer-weeks for story points or dollar cost to match how your team estimates.
- Ask for a short Slack-ready summary to send back to the founder after the full brief.
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
Define Feature Non-Goals and Scope Boundaries
Sort requested features into three clear out-of-scope buckets with explicit business reasons to prevent scope creep.
Decline a stakeholder feature request diplomatically
Turn down an out-of-scope feature request without burning bridges. Perfect for product managers protecting roadmap focus while maintaining strong stakeholder relationships.
Write a One-Page PRD for a Small Feature That Engineers Can Start From
Get a one-page PRD under 400 words with one problem statement, one primary KPI, testable requirements, explicit non-goals and an owned open-questions list.
Stress Test Your Product Requirements Document for Edge Cases
This prompt audits your feature PRD to identify hidden technical risks, permission gaps, and scope creep before development begins.
Write a Product Requirements Document from Your Raw Feature Notes
Turns pasted feature notes into a PRD where each requirement has numbered, testable acceptance criteria and missing details become open questions.
Write a post-advisory board roadmap recap
Turn raw meeting notes into a crisp follow-up email that shows customer advisory board members how their feedback shaped the roadmap.
- Transform Customer Interview Transcripts into Ranked Pain-Point Matrix
- Cluster Support Tickets by Operational Cost and Severity
- Plan a listening-first advisory board agenda
- Classify onboarding drop-offs into cognitive and value friction
- Rewrite empty state copy to accelerate user activation
- Turn onboarding test notes into root causes