Feature request intake brief
Turn a feature request into evidence about the underlying need and the next decision.
Product features · 45 min · Standard · 20 questions
Request evidence
Who made the request?
What situation were they in?
What happened immediately before the request?
What outcome is the requester trying to achieve without referring to the proposed feature?
How is the requester handling this today?
How often does the underlying situation occur?
How many customers face it?
What is the consequence when it occurs?
Where else might this need appear?
Alternative explanations
Which direct observation supports the request?
Which part of the request is still an assumption?
Could an existing capability address the need?
Is a current policy creating the need?
Is a product defect creating the need?
Would clearer guidance address the need?
Decision and response
Who owns the next investigation or response?
When will the requester hear back?
What should happen to this request next?
Why is that disposition appropriate?
What evidence should we gather next?
How to use this brief
Use this brief as a bank of questions for the conversation. Choose what is relevant, mark covered questions as you go, and skip anything that has already been answered.
Use this brief when...
Use when you need to turn a feature request into evidence about the underlying need and the next decision.
Best used as: Live call · Async intake
- Category
- Product features
- Discussion time
- 45 minutes
- Depth
- Standard
- Last updated
- Jul 21, 2026
- Scope
- Design briefs
- Best used as
- Live callAsync intake
- Design roles
- Product designer
- Audience
- Product managersProduct designersFreelancers and consultantsDesign agencies
- Platforms
- Cross-platform
- Company type
- StartupB2BB2CEnterprise
- Product stage
- Early-stageGrowthMature product
- Tags
- product-featuresfeature-request-intakeresearch-and-evaluationcustomer-requestinternal-requestbacklog-intake