Feedback Triage and Product Routing
Feedback triage turns raw comments, requests, and reports into evidence that the right team can assess. Product routing sends each item to support, research, product discovery, delivery, or another defined destination without treating every comment as a feature request.
itTechnical communication and collaboration | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Feedback Triage and Product Routing
Feedback triage is the controlled process that turns an incoming observation into a classified, traceable decision. Product routing is the part of that process that sends the observation, or a finding derived from it, to the team and system able to act. Together they prevent a support ticket, interview quote, survey response, sales note, and public idea from becoming one undifferentiated backlog.
The process sits between feedback channels and decision systems:
source → intake record → safety and scope check → normalize → relate → route → decide → close loop
The intake record preserves what was received, where it came from, and enough context to interpret it. Triage adds operational metadata. Routing then links or moves the right representation into a destination such as a support queue, incident process, research repository, discovery idea, or delivery tracker.
Keep three record types distinct
Raw feedback is what a person said or what an observed behavior revealed. Preserve its wording and source context. Rewriting it too early can turn a problem into somebody's preferred solution.
A finding is an evidence-based interpretation of one or more observations. GOV.UK's research guidance separates observations from findings and recommends grouping similar observations before deciding what they mean. A finding can connect repeated feedback without erasing the original records.
A work item is a commitment to investigate, design, repair, or deliver something. It belongs in a delivery system only after a responsible team accepts it. Feedback can support a work item, but receipt does not create a promise.
many observations → one finding or idea → zero, one, or several work items
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://www.gov.uk/service-manual/user-research/analyse-a-research-session
Supports
- Separation of raw observations from interpretation
- Grouping observations into themes, determining findings, and deciding actions
- Intro, practice, quiz, reference-path, and infographic claims about evidence synthesis
- https://www.gov.uk/service-manual/user-research/start-by-learning-user-needs
Supports
- Evidence-based user needs focused on problems rather than proposed solutions
- Link and quiz rationales about neutral problem framing
- https://www.gov.uk/service-manual/user-research/sharing-user-research-findings
Supports
- Findings used for design decisions, prioritization, stories, and roadmaps
- Regular sharing cadence and concise finding structure
- Queue-review and communication guidance
- https://www.gov.uk/service-manual/agile-delivery/deciding-on-priorities
Supports
- Regular prioritization based on performance analysis, user research, and stakeholder input
- Use of a clear method with delivery-team and stakeholder involvement
- Separation of prioritization from intake and quiz answers
- https://www.atlassian.com/software/jira/product-discovery/guides/insights/overview
Supports
- Insights as data that support, validate, and shape ideas
- Insight descriptions, source links, impact ratings, and labels
- Evidence-to-idea relationships in intro, slides, cheatsheet, quiz, and infographic
- https://www.atlassian.com/software/jira/product-discovery/guides/ideas/overview
Supports
- Ideas representing problems, opportunities, solutions, or requests
- Idea links to comments, insights, fields, history, and delivery tickets
- Record-layer and reference-path claims
- https://www.atlassian.com/software/jira/product-discovery/guides/fields/overview
Supports
- Fields used to compare, categorize, sort, and prioritize ideas
- Triage fields, formulas, effort, impact, goals, and confidence examples
- Controlled vocabulary, scoring, quiz, and reference-path claims
- https://www.atlassian.com/software/jira/product-discovery/guides/integrations/overview
Supports
- Discovery as uncommitted work and Jira delivery as committed work
- Connections from feedback sources through ideas into delivery
- Destination and routing claims in intro, quiz, and reference path
- https://www.atlassian.com/software/jira/product-discovery
Supports
- Jira Product Discovery capture, prioritization, roadmapping, and delivery connection
- Landscape role and product destination
- https://www.atlassian.com/software/jira/product-discovery/pricing
Supports
- Jira Product Discovery proprietary cloud delivery and free plus paid plans
- Landscape licensing and pricing classification
- https://docs.github.com/en/issues/tracking-your-work-with-issues/administering-issues/triaging-an-issue-with-ai
Supports
- Automated issue intake suggestions for actionability and missing information
- Human review of automated suggestions
- Automation controls in intro, slides, cheatsheet, practice, quiz, and reference path
- https://www.productboard.com/product/insights/
Supports
- Central capture, curation, routing, filtering, and segmentation of feedback
- Productboard Landscape placement
- https://www.productboard.com/pricing/
Supports
- Productboard free and paid plans
- Landscape pricing classification
- https://canny.io/features
Supports
- Feedback boards, user association, internal comments, segmentation, tags, categories, prioritization, roadmaps, and status updates
- Closed-loop behavior and Canny Landscape placement
- https://help.canny.io/en/collections/325099-canny-features
Supports
- Post states, owners, merging, tags, categories, automation, segmentation, and integrations
- Canny workflow details used in intro and Landscape
- https://canny.io/pricing
Supports
- Canny free and paid plans
- Landscape pricing classification
- https://www.aha.io/ideas/overview
Supports
- Portals, consolidation, review, themes, prioritization, and segmentation
- Aha Ideas Landscape placement
- https://support.aha.io/aha-ideas/support-articles/ideas-management/ideas-introduction~7444662523467143698
Supports
- Structured idea management, regular feedback review, and continued communication
- Aha Ideas destination-contract rationale
- https://www.aha.io/ideas/pricing
Supports
- Aha Ideas paid plans and trial
- Landscape pricing classification
- https://dovetail.com/
Supports
- Centralization of research and customer signals with source-linked insights
- Dovetail Landscape placement on the evidence side of routing
- https://dovetail.com/pricing/
Supports
- Dovetail free and paid plans
- Landscape pricing classification
- https://github.com/sindresorhus/awesome
Supports
- Starting index used to discover an applicable awesome list
- https://awesome-selfhosted.net/tags/ticketing.html
Supports
- Discovery of Frappe Helpdesk, FreeScout, MantisBT, Request Tracker, and Zammad
- Ticketing use cases and the listed project destinations
- https://frappe.io/helpdesk
Supports
- Open-source helpdesk positioning and Awesome Links rationale
- https://freescout.net/
Supports
- Email-based help desk and shared mailbox positioning
- Awesome Links rationale
- https://www.mantisbt.org/
Supports
- Software bug-tracking positioning and Awesome Links rationale
- https://www.bestpractical.com/rt/
Supports
- Issue and request tracking with owned workflow states
- Awesome Links rationale
- https://zammad.org/
Supports
- Open-source multi-channel support and ticketing positioning
- Awesome Links rationale
