Organize incoming feature requests into themes and priorities so you can make faster, evidence-backed product decisions.
The template
Request Summary
Write a one-line summary of what the user is asking for, in plain language.
Example: "User wants to export reports as a PDF directly from the dashboard without going through settings."
User Segment
Note which type of user submitted this request — their role, plan tier, or use case.
Example: "Enterprise plan — Operations Manager at a 200-person logistics company using the analytics module daily."
Underlying Need
Describe the core problem or job-to-be-done behind the request, not just the feature itself.
Example: "Needs to share formatted data with stakeholders who don't have access to the product — currently screenshots or manual copy-paste."
Priority Signal
Record how often this request appears, which segments are asking, and any revenue or churn risk attached.
Example: "Mentioned by 14 enterprise users this quarter; 2 accounts flagged it in churn interviews; estimated $42k ARR at risk."
How to use it
Collect your requests in one place Pull feature requests from all sources — support tickets, sales calls, NPS responses, and in-app feedback — into a single spreadsheet or doc before you start.
Fill in one row per request For each piece of feedback, complete all four template sections so every request is documented consistently and nothing gets lost in translation.
Group requests into themes Read through your completed rows and tag requests that share the same underlying need, then count how many responses fall under each theme.
Prioritize by impact and frequency Rank your themes by combining request volume, the seniority or value of the requesting segment, and any churn or expansion signals attached to each theme.
What it looks like filled in
PDF & Export Options
"I have to take screenshots every week to share results with my director — a PDF export would save me so much time."
→ Prioritize one-click PDF export in the next sprint; validate spec with top 5 requesting accounts before build.
Role-Based Permissions
"We need to give our clients view-only access without them being able to accidentally change anything — right now it's all or nothing."
→ Add a read-only guest role to the Q3 roadmap; flag for upsell potential on Enterprise tier.
Slack & Notification Integrations
"I'd love a Slack alert when a report hits a certain threshold so I don't have to log in just to check the numbers."
→ Build threshold-based Slack notifications; scope as a lightweight integration to ship before larger API work begins.
Why teams skip the template
Copying feedback by hand takes hours Pulling requests from tickets, calls, and surveys into one spreadsheet is tedious and means analysis only happens once a month at best.
Grouping themes is subjective and inconsistent Different team members tag the same request differently, making it impossible to trust your frequency counts or compare results over time.
Priority signals get buried or missed entirely Churn risk and revenue context are often buried in call notes — manual reviews routinely miss the signals that would change your prioritization.
Analyze your feature requests automatically — no template needed
