Product Feedback

Feedback

Collect user feedback on specific product features to inform your roadmap.

7 input fields · Traditional mode

When to use this template

Product feedback collection is broken at most companies. The signal arrives as scattered Slack messages, support tickets that mention features, sales calls where prospects ask for things, and the occasional NPS comment — none of which aggregate cleanly into roadmap decisions. This template fixes the aggregation problem by making the feedback structured: which feature, how often you use it, how important it is to your workflow, and what you would change. Once the data is structured, sorting by feature and grading importance against rating gives PMs a real opportunity-vs-impact map. The hidden gem is the importance-scale field — it lets you separate "people complain about this but never use it" from "people use this every day and it is broken", which is the difference between a low-priority polish task and a P0.

Who it's for

PM teams running quarterly roadmap planning with structured user input
Founders deciding what to build next with limited engineering bandwidth
UX researchers complementing qualitative interviews with quantitative votes
CS teams routing feature requests into a structured pipeline instead of email chains

What you get

Feature dropdown for routing feedback to the right product area
1-5 rating scale to track satisfaction with the specific feature
Usage frequency multiple choice (Daily / Weekly / Monthly / Rarely / First Time) for context
Two open-ended fields ("What works?" and "What would you change?") for qualitative themes
Importance opinion-scale (1-5) — the key field for prioritization
Optional email so you can follow up with high-quality contributors

Fields in this template

Product FeedbackHeading

Help us build a better product. Share your experience below.Paragraph

Email AddressEmail

Which feature are you providing feedback on?DropdownRequired

How would you rate this feature?RatingRequired

How often do you use this feature?Multiple ChoiceRequired

What do you like about it?Long Text

What would you improve?Long Text

How important is this feature to your workflow?Opinion ScaleRequired

Customization tips

Replace the generic Dashboard / Reporting / Integrations / Settings options with your real product surface area — granularity here determines roadmap usefulness
Embed the form in-product, contextually triggered after a user takes a feature action — captures feedback while the experience is fresh
Pipe submissions to a Notion or Linear database so PMs can triage in their existing tools
Track responses over time per feature — the trend matters more than the snapshot
For high-importance + low-rating combinations, auto-flag the response in a Slack channel for fast triage

Frequently asked questions

How is this different from a feature request board?

A feature request board (Canny, Productboard) collects requests as items that other users vote on. This template collects structured feedback on features that already exist. Use the feature board for "what should we build?". Use this for "what is broken or missing in what we already built?".

Should I make every field required?

No. Required fields lower response rate disproportionately. Make feature, rating, frequency, and importance required — those are the four data points you need for prioritization. Make the open-ended fields optional. Many users will skip them, and that is fine; the ones who write something usually have something worth writing.

How do I act on the data?

Plot importance (x-axis) against rating (y-axis) in a scatter chart per feature. The bottom-right quadrant — high importance, low rating — is where to focus engineering effort. The top-right is what is working. The bottom-left is unimportant features users are unhappy with — usually candidates for deprecation. Top-left is hidden gems people love but rarely use.

Related templates