Product Task
Decide how to answer a feature request
A proposed implementation is being treated as the requirement before the underlying workflow failure is clear.
“This is costing me product capacity while one requested implementation is treated as the only answer.”
Outcome
The result to aim for
Record a build, defer, decline, or research decision tied to the evidenced workflow problem.
Best practices
- Bring the original request, its source and commercial context, existing research, current product boundary, and decision owner.
- Create or update the product idea; then preserve the requester’s proposed implementation, source, date, context, and any existing workflow evidence as separate fields.
- Compare the requested implementation with a smaller response, existing capability, operational response, defer, decline, or research path; then record the decision, trade-off, requester impact, and owner.
- Confirm that the request and workflow evidence are separate.
- Escalate contractual promises to the accountable commercial owner.
Related sources
Further information
- Documented guidance: Basecamp: Set Boundaries
- Related guidance: Hacker News: Ask HN: Co-founder is addicted to new features