What is a Feature Request?
A feature request is any suggestion to add, change, or improve product functionality. Requests come from users, customers, sales teams, support tickets, executives, and the PM's own observations. They range from specific ("add a dark mode toggle") to vague ("make it easier to use").
Feature requests are signal, not instruction. They tell you what users are struggling with, but their proposed solution is usually the first thing that came to mind, not the best design.
Why Feature Requests Matter
Feature requests are one of the richest sources of voice of customer data. Patterns in requests reveal unmet needs, workflow gaps, and opportunities for differentiation.
Ignoring feature requests alienates customers. Blindly following them builds a Frankenstein product. The PM's value lies in translating raw requests into validated problems worth solving.
How to Handle Feature Requests
Capture every request in a central system, not scattered across Slack, email, and support tickets. Tag each with the requester, their company size, use case, and frequency.
Look for patterns, not individual asks. One customer requesting a feature is an anecdote. Twenty customers requesting the same capability is a signal worth investigating.
Apply JTBD thinking: what job is the user trying to accomplish? The feature they requested is their imagined solution. Your job is to find the best solution, which might be simpler or different than what they described.
Feature Requests in Practice
Intercom built their "Product Decisions" framework specifically to handle feature request volume. They categorize requests by strategic fit, reach, and effort, then publish monthly decisions explaining what they chose to build and why.
Basecamp takes the opposite approach. They intentionally do not track feature request counts. Their philosophy: if a need is real, it will keep coming up organically. They trust their judgment over request tallies.
Common Pitfalls
- Building for the loudest voice. Enterprise customers who threaten to churn get attention, but their needs may not represent your broader user base.
- Losing the problem. "Add an export to PDF button" is a solution. The problem might be "I need to share reports with people who do not have accounts."
- No feedback loop. When you build something a user requested, tell them. When you decide not to, explain why.
- Feature request democracy. Voting systems bias toward power users and existing customers, not potential customers or underserved segments.
Related Concepts
Feature requests feed into the product backlog and are evaluated through prioritization frameworks. They are a key input to product discovery and connect to voice of customer programs. Use JTBD to dig beneath the surface of each request.