Review the problem and response behind a feature request
Choose a build, defer, decline, or research response tied to the existing evidence and product boundary.
- Preparation
- A short evidence and product-boundary review.
- Steps
- 3
- Difficulty
- Moderate
- Task
- Decide how to answer a feature request
Requires: Bring the original request, its source and commercial context, existing research, current product boundary, and decision owner. Separate any contractual commitment from the evidence that the core product should change.
Uses: Jira Product Discovery
Back to the Task: Decide how to answer a feature requestBefore you start
Prepare
- Bring the original request, its source and commercial context, existing research, current product boundary, and decision owner.
- Separate any contractual commitment from the evidence that the core product should change.
Steps
Work through the method
Use the listed inputs and tools. Check the evidence when you need to verify a step.
Record the request without promoting it
Create or update the product idea. Preserve the requester’s proposed implementation, source, date, context, and any existing workflow evidence as separate fields.
Step details and sources
Why it matters: The team needs the original request and its interpretation to remain distinguishable.
- Input
- The request, source context, and existing evidence.
- Output
- A product idea with a source-linked request and separate interpretation.
Tools in this stepJira Product DiscoveryEvidence for this step
The cited accounts distinguish a requested implementation from the workflow problem and describe reducing one request to a smaller response.
Hacker News: Comments by codegeek and Jugurtha, 16–17 September 2020Separate anonymous accounts support problem clarification. They do not set a sufficient evidence threshold.Jira Product Discovery can attach an insight description, source link, optional impact, and labels to an idea.
Atlassian Support: StepsThe tool stores an interpretation. It does not verify the source, representativeness, or conclusion.
Clarify the evidenced workflow problem
Review existing evidence for the failed workflow, affected user, consequence, frequency, and current workaround. Mark missing evidence for Customer Research rather than filling the gap with assumptions.
Step details and sources
Why it matters: A product response should address an evidenced problem rather than inherit the requested implementation.
- Input
- The linked request and approved research evidence.
- Output
- A problem statement with evidence, gaps, and product relevance.
Tools in this stepJira Product DiscoveryEvidence for this step
The cited accounts distinguish a requested implementation from the workflow problem and describe reducing one request to a smaller response.
Hacker News: Comments by codegeek and Jugurtha, 16–17 September 2020Separate anonymous accounts support problem clarification. They do not set a sufficient evidence threshold.
Choose the product response
Compare the requested implementation with a smaller response, existing capability, operational response, defer, decline, or research path. Record the decision, trade-off, requester impact, and owner.
Step details and sources
Why it matters: The decision must show why the product will change or stay as it is.
- Input
- The problem statement, product boundary, commercial context, and response options.
- Output
- A build, defer, decline, or research decision with consequences.
Tools in this stepJira Product DiscoveryEvidence for this step
The cited accounts distinguish a requested implementation from the workflow problem and describe reducing one request to a smaller response.
Hacker News: Comments by codegeek and Jugurtha, 16–17 September 2020Separate anonymous accounts support problem clarification. They do not set a sufficient evidence threshold.Jira Product Discovery can attach an insight description, source link, optional impact, and labels to an idea.
Atlassian Support: StepsThe tool stores an interpretation. It does not verify the source, representativeness, or conclusion.
Success checks
Check the result
- The request and workflow evidence are separate.
- The response fits the current product boundary or reopens it explicitly.
- Missing evidence becomes a research action rather than an invented conclusion.
Failure modes
What could go wrong
- Escalate contractual promises to the accountable commercial owner.
- Do not treat one request as representative demand.
- Send fresh interviews and observation to Customer Research.
Tools
Choose tools
Jira Product Discovery
A product workspace for attaching existing evidence to ideas and making selected comparison fields visible.
Check fit, limits and pricingSources
Check the sources
Check what each source supports and where the advice has limits.
- Hacker News: Ask HN: Co-founder is addicted to new featuresFirst-hand founder and practitioner discussion · Published 16 September 2020
- Basecamp: Set BoundariesPractitioner method documentation · Publication date unavailable
- Atlassian Support: Create insights in your ideaOfficial product documentation · Publication date unavailable