01
Separate facts from assumptions
Start with the request as written. Distinguish confirmed information from interpretations, implied solutions, and missing details.
Made for Engineers
Clarify a Request With a Product Partner
Also useful for: people in Software Engineering
45 min
Advanced
Software Engineering
Engineer
Communicate Better
Career outcome:
Avoid Professional Risk
Run a structured product clarification conversation before technical planning begins.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Expose gaps, assumptions, and conflicting expectations before they turn into rework.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Find the underlying problem
Move behind the requested feature or solution to the user or business problem that needs attention.
03
Identify users and triggers
Clarify who encounters the problem, when it occurs, what happens now, and what outcome matters.
04
Test behavior across scenarios
Cover the normal path plus edge, failure, and recovery cases that could change the requirement.
05
Draw the boundaries
Make tentative scope lines visible so the product partner can confirm what belongs now, later, or not at all.
06
Surface constraints and tradeoffs
Connect deadlines, policies, technical limits, and dependencies to the choices they may force.
07
Rank the unknowns
Decide which gaps deserve meeting time and which should become follow-up investigations.
08
Build the conversation plan
Fit the highest-value topics into the available time and keep the discussion moving toward decisions.
09
Prepare the live script and notes
Use neutral language that invites correction and capture each statement in the right category.
10
Close decisions and assign follow-up
Convert the discussion into a record that supports investigation, planning, or a deliberate pause.
Make Your Play
Clarify a Request With a Product Partner
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Paste or summarize the product request that needs clarification.
0/10000
Describe what you currently believe the request means, including any interpretations that may be wrong.
0/10000
List the people or functions expected in the conversation.
List customer feedback, data, incidents, research, or business context connected to the request.
0/10000
List deadlines, policies, platform limits, dependencies, or commitments that may restrict the work.
0/10000
Select the time available for the clarification conversation.
State what needs to be decided, confirmed, or assigned by the end of the conversation.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Separate facts from assumptions
Start with the request as written. Distinguish confirmed information from interpretations, implied solutions, and missing details.
02
Find the underlying problem
Move behind the requested feature or solution to the user or business problem that needs attention.
03
Identify users and triggers
Clarify who encounters the problem, when it occurs, what happens now, and what outcome matters.
04
Test behavior across scenarios
Cover the normal path plus edge, failure, and recovery cases that could change the requirement.
05
Draw the boundaries
Make tentative scope lines visible so the product partner can confirm what belongs now, later, or not at all.
06
Surface constraints and tradeoffs
Connect deadlines, policies, technical limits, and dependencies to the choices they may force.
07
Rank the unknowns
Decide which gaps deserve meeting time and which should become follow-up investigations.
08
Build the conversation plan
Fit the highest-value topics into the available time and keep the discussion moving toward decisions.
09
Prepare the live script and notes
Use neutral language that invites correction and capture each statement in the right category.
10
Close decisions and assign follow-up
Convert the discussion into a record that supports investigation, planning, or a deliberate pause.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Paste the request as written, then add what you currently think it means. If evidence or constraints are unknown, say “Unknown” instead of guessing. Use the generated questions as a guide, not a script that must be read word for word.
Advanced instructions
Challenge solution-shaped requests by tracing them back to outcomes, evidence, and constraints. During the conversation, label statements as facts, decisions, assumptions, or unknowns. Push unresolved technical questions into named investigations rather than debating them without evidence.
Use this when
A product request is important enough to discuss but still leaves questions about the problem, users, scenarios, boundaries, priorities, or expected behavior.
You'll need
- Request or initiative
- Current understanding
- Participants
- Known evidence
- Known constraints
- Meeting length
- Desired outcome
You'll get
- A problem statement confirmed or corrected
- Primary users and scenarios identified
- In-scope and out-of-scope boundaries recorded
- High-impact assumptions and unknowns labeled
- Priority tradeoffs made explicit
- Decisions, owners, and follow-up dates documented
By the end of this playbook
You will have:
- A problem statement confirmed or corrected
- Primary users and scenarios identified
- In-scope and out-of-scope boundaries recorded
- High-impact assumptions and unknowns labeled
- Priority tradeoffs made explicit
- Decisions, owners, and follow-up dates documented
Examples
Progress 1 of 10