Where Should We Store Feedback
A guide for deciding where product feedback should live so teams can search it, score it, and act on it.
Product walkthrough
Watch how Feedbackly brings product feedback into a shared board for review and prioritization.
Watch the product walkthroughSee the Feedbackly product walkthrough
Practical context for Where Should We Store Feedback
Store product feedback somewhere your team can retrieve the original customer evidence, compare recurring problems, and record decisions. Choose the system around the work you need to do: private research, support resolution, shared requests, or delivery planning.
Match the evidence to its home
Support tickets belong with the account context needed to resolve them. Interview recordings and sensitive research notes need a suitable private repository. A shared feedback board works for non-sensitive requests that benefit from comments, voting, and visible status.
You do not need to move every raw artifact into one tool. A useful approach keeps original evidence in the appropriate system and links a clear problem summary to the product review queue.
- +Support system: incidents and account-specific resolution.
- +Research repository: participant context and detailed observations.
- +Feedback board: public-safe requests and product discussion.
Create a minimum searchable record
Capture a problem title, the task, source link, affected audience, and review owner. Add a theme only when it helps someone retrieve or compare the evidence. Avoid a taxonomy so elaborate that people stop recording feedback.
For example, 'Cannot share a weekly report with an external client' is easier to find and assess than 'reporting request'. Keep the original customer's wording in the source while using a consistent summary for planning.
- +Use stable references when titles change.
- +Record distinct customer reports without overwriting them.
- +Separate observed problems from suggested solutions.
Move beyond a spreadsheet when coordination breaks
A spreadsheet can work when one owner maintains a small queue. Reconsider it when updates conflict, requests lose their source, or customers need a visible status. Define which system owns the decision so a copied row does not become a second backlog.
Migrate a small, reviewed set first. Check that titles, descriptions, and source references survive the move, then agree how new feedback enters the system. Keep private evidence private during the migration.
- +Decide which system is authoritative for each field.
- +Preserve evidence before removing duplicates.
- +Document who maintains links and statuses.
Keep exploring this topic
These next reads help you move from the concept on this page to a framework, tool, template, or deeper comparison you can apply right away.
Questions teams usually ask
Can Notion be our feedback repository?
It can hold internal planning notes and evidence. If customers need submission, voting, and public status, connect that planning process to an appropriate customer-facing board.
Should everything be publicly searchable?
No. Customer account details, confidential research, and sensitive incident reports need a private path. Share only suitable summaries on a public board.
Put customer feedback into practice
Use Feedbackly to collect requests, discuss customer problems, and make product status visible. Bring that evidence into your team's review process.