Glossary
31 terms every product builder eventually googles — defined in plain English, with the depth and the practical angle that the one-line definitions leave out.
Customer feedback is any information users share about their experience with a product — bug reports, feature requests, reviews, complaints, and praise. It is the rawest available signal about what to fix, build, or leave alone.
Read the full definitionIn-app feedback is input collected inside the product while the user is using it, rather than through external channels like email or surveys sent later. Proximity to the moment of friction makes it more specific and more honest than recalled feedback.
Read the full definitionA feedback widget is a small embeddable component — typically a floating button that opens a short form — that lets visitors submit feedback from any page of a site or app. It is installed once, usually with a script tag, and works everywhere the script loads.
Read the full definitionA feedback portal is a dedicated destination — usually a hosted page — where customers submit ideas, browse existing requests, vote, and follow progress. It is the customer-facing counterpart to whatever internal triage the team runs.
Read the full definitionA feedback board is a public or private space where feedback lives as discussable posts — users submit ideas, comment on others’, and vote. Canny, Nolt, and Fider are board-centric tools.
Read the full definitionA feedback inbox is the private workspace where submissions arrive for the team to review, filter, and act on — feedback’s equivalent of a support queue. Items carry categories, statuses, and context rather than sitting in an undifferentiated pile.
Read the full definitionA bug report is a user’s account of the product behaving incorrectly — something broken, erroring, or not doing what it promised. It is the feedback type with the most direct fix path and the most need for context.
Read the full definitionA feature request is a user asking for a capability the product does not yet have. Individually it is an anecdote; collected and counted, requests become a demand signal that can genuinely steer a roadmap.
Read the full definitionA customer review is an evaluative judgment of the product, usually a rating plus commentary. Unlike a bug report or feature request, its subject is overall sentiment — how the product feels to use and whether the reviewer would recommend it.
Read the full definitionA customer feedback loop is the full cycle from a user sharing input to the user seeing the outcome: collect, organize, decide, act, and communicate back. The “loop” is the crucial part — feedback that vanishes into a void trains users to stop giving it.
Read the full definitionFeedback triage is the recurring practice of reviewing new submissions and deciding what each one is and what happens next — fix now, cluster with duplicates, promote for validation, or decline. It is to feedback what inbox-zero is to email.
Read the full definitionClosing the loop means telling the people who gave feedback what happened to it — the fix shipped, the feature is planned, or the request was declined and why. It is the difference between feedback as extraction and feedback as conversation.
Read the full definitionVoice of the customer is the umbrella practice of systematically capturing what customers say, need, and expect across every channel, then feeding that understanding into product and business decisions.
Read the full definitionProduct discovery is the work of figuring out what is worth building before building it — understanding user problems, testing assumptions, and validating demand so delivery effort lands on real needs.
Read the full definitionIdea management is the process of collecting product ideas from users and stakeholders, deduplicating and organizing them, and moving the best through evaluation toward delivery — keeping the pipeline from suggestion to shipped feature orderly.
Read the full definitionFeature voting lets users signal demand by upvoting the feature requests they want, turning scattered anecdotes into ranked, countable preference data.
Read the full definitionAn upvote is a single user’s one-click endorsement of a feedback item or feature request — the atomic unit of demand measurement in feedback tools.
Read the full definitionA prioritization framework is a structured method for deciding what to build next — RICE, ICE, MoSCoW, impact–effort matrices — that scores or sorts candidates on explicit criteria instead of instinct alone.
Read the full definitionRICE scores features by Reach × Impact × Confidence ÷ Effort — how many users it touches, how much it moves them, how sure you are, and what it costs to build. Higher scores argue for earlier delivery.
Read the full definitionICE scores candidates on Impact, Confidence, and Ease (usually 1–10 each, multiplied) — a faster, looser cousin of RICE that trades the reach estimate for speed of scoring.
Read the full definitionMoSCoW sorts requirements into Must have, Should have, Could have, and Won’t have (this time) — a categorical prioritization used to define scope for a release or project rather than to rank a backlog.
Read the full definitionAn impact–effort matrix plots candidates on two axes — value delivered versus work required — yielding four quadrants: quick wins, big bets, fill-ins, and money pits. It is prioritization as a picture.
Read the full definitionA product roadmap is a communication artifact showing where the product is headed — what is planned, in progress, and shipped — at whatever fidelity its audience needs. It expresses strategy as a sequence, not a promise of dates.
Read the full definitionA public roadmap is a customer-visible board of what a product team is considering, building, and shipping — typically with statuses users can follow and items they can vote or comment on.
Read the full definitionA changelog is a chronological record of what changed in a product — new features, improvements, and fixes — published where users can see it. It is the product’s public memory.
Read the full definitionRelease notes are the announcement attached to a specific version or release, explaining what shipped and why it matters. Where a changelog is the continuous record, release notes are the per-release story.
Read the full definitionNPS measures loyalty with one question — “how likely are you to recommend us?” (0–10) — then subtracts the percentage of detractors (0–6) from promoters (9–10). Scores range from −100 to +100.
Read the full definitionCSAT measures satisfaction with a specific interaction or feature — “how satisfied were you with X?” on a short scale — reported as the percentage of positive responses. It is a transactional metric, asked in the moment.
Read the full definitionCES asks how much effort a task took — “how easy was it to accomplish X?” — on a scale from very difficult to very easy. Its premise: reducing effort predicts loyalty better than delighting.
Read the full definitionChurn rate is the percentage of customers (or revenue) lost over a period — the metric that quietly decides whether a subscription business compounds or leaks. Its inverse is retention.
Read the full definitionProduct-market fit is the state where a product satisfies a real market’s demand strongly enough that growth starts pulling instead of pushing — users stay, refer, and complain when it breaks.
Read the full definition