Product Management Glossary
Key product management, agile, and customer feedback terms defined. A reference for product teams building what users actually want.
Acceptance Criteria
Acceptance criteria are the specific conditions that a user story or feature must satisfy to be considered complete. They define the boundaries of a feature in testable terms, ensuring the development team and product owner agree on what "done" means. Well-written acceptance criteria prevent scope creep and reduce rework by making expectations explicit before development begins.
Read definition →Backlog Grooming
Backlog grooming (also called backlog refinement) is the recurring practice of reviewing, updating, and prioritizing items in a product backlog. During grooming sessions, the team adds detail to upcoming stories, removes obsolete items, re-estimates effort, and reorders based on new information. It keeps the backlog healthy and sprint-ready.
Read definition →Changelog
A changelog is a chronological record of product updates, new features, bug fixes, and improvements shared with users. It serves as both a communication tool and a historical reference for what has changed in a product over time. Well-maintained changelogs keep users informed, demonstrate momentum, and close the feedback loop by showing that user input leads to real product changes.
Read definition →Churn Rate
Churn rate is the percentage of customers who stop using a product or cancel their subscription within a given time period. It is calculated by dividing the number of customers lost during the period by the number at the start. A high churn rate signals product-market fit problems, unmet user needs, or competitive pressure that requires immediate attention.
Read definition →Closed-Loop Feedback
Closed-loop feedback is the practice of following up with customers after they provide feedback to let them know what action was taken. It completes the feedback cycle by connecting input to outcome. Most companies collect feedback. Few close the loop. Teams that do see higher satisfaction, stronger retention, and more willingness from customers to share future input.
Read definition →Continuous Discovery
Continuous discovery is the practice of regularly talking to users and incorporating their feedback into product decisions, rather than doing research only at the start of a project. It involves weekly customer touchpoints, structured opportunity mapping, and rapid assumption testing. The goal is to maintain a constant flow of user insight that informs every sprint.
Read definition →Customer Advisory Board
A customer advisory board (CAB) is a selected group of customers who provide strategic feedback on product direction, market trends, and company decisions. Unlike open feedback channels, a CAB offers curated, in-depth input from your most engaged or representative customers. It builds stronger relationships while giving the product team high-quality directional signals.
Read definition →Customer Effort Score
Customer Effort Score (CES) is a metric that measures how easy it is for customers to accomplish a specific task with your product or support team. It is typically captured through a post-interaction survey asking users to rate their agreement with a statement like "the company made it easy for me to handle my issue." Lower effort correlates strongly with customer loyalty and repeat purchases.
Read definition →Customer Experience
Customer experience (CX) is the total perception a customer forms about a brand based on every interaction across the entire relationship. It spans marketing, sales, onboarding, product usage, and support. CX is shaped by both deliberate design choices and the gaps between them. Companies that treat CX as a system rather than a department consistently outperform on retention and growth.
Read definition →Customer Feedback Loop
A customer feedback loop is the continuous cycle of collecting feedback from users, analyzing it for patterns, acting on the insights by building or improving features, and then communicating those changes back to the users who provided the input. Closing the loop is what separates companies that listen from companies that just collect data. It turns feedback into a relationship-building mechanism.
Read definition →Customer Retention
Customer retention is the ability of a company to keep its existing customers over a given period. It measures how many customers continue using and paying for a product rather than leaving for a competitor or canceling entirely. Retention is driven by product value, customer experience, and the ongoing match between what users need and what you deliver.
Read definition →Customer Satisfaction
Customer satisfaction (CSAT) measures how well a product or service meets customer expectations. It is typically assessed through post-interaction surveys where users rate their experience on a scale. Common satisfaction metrics include CSAT scores, Net Promoter Score, and Customer Effort Score. High satisfaction correlates with retention, expansion revenue, and positive word of mouth.
Read definition →Definition of Done
A definition of done (DoD) is a shared checklist of criteria that a product increment must meet before the team considers it complete. It typically includes code quality standards, testing requirements, documentation, and deployment readiness. For user-requested features, the DoD should also verify that the original user problem is actually solved.
Read definition →Digital Suggestion Box
A digital suggestion box is an online tool that replaces the physical suggestion box with a structured feedback collection system. It allows users, customers, or employees to submit ideas, feature requests, and improvement suggestions through a web interface. Modern digital suggestion boxes include voting, categorization, and status tracking, evolving into full feedback management platforms.
Read definition →Dual-Track Agile
Dual-track agile is a development approach where discovery and delivery run as parallel tracks within the same team. The discovery track focuses on understanding user problems and validating solutions. The delivery track builds and ships validated features. Both tracks operate continuously, with discovery feeding a stream of de-risked ideas into the delivery backlog.
Read definition →Feature Parity
Feature parity means matching the functionality of a competing product or an existing version of your own product. Teams pursue feature parity during platform migrations, product rewrites, or when entering a market with established competitors. It is a strategic choice that balances meeting baseline expectations with the risk of building a copycat product instead of innovating.
Read definition →Feature Prioritization
Feature prioritization is the process of deciding which features to build first based on impact, effort, user demand, and strategic fit. It uses structured frameworks like RICE, ICE, and MoSCoW to replace gut-feel decisions with repeatable scoring methods. Effective prioritization connects customer feedback data directly to development planning so teams build what users actually need.
Read definition →Feature Request
A feature request is a user suggestion for new functionality or an improvement to an existing product. Feature requests represent raw demand signals from the people who use your product daily. Feedback tools organize, deduplicate, and rank these requests so product teams can identify patterns and prioritize what to build next based on real user needs rather than internal assumptions.
Read definition →Feature Voting
Feature voting is a mechanism that lets users upvote feature requests to signal demand. It transforms qualitative feedback into quantitative data by showing exactly how many people want a specific capability. Voting surfaces the features with the broadest user appeal and gives product teams a defensible way to prioritize their roadmap based on actual user demand rather than guesswork.
Read definition →Feedback Board
A feedback board is a public or private forum where users submit, discuss, and vote on product feedback. It acts as a structured channel between a product team and its users, replacing scattered emails and support tickets with a single visible space. Feedback boards organize suggestions by status and popularity, making it easy to see what users want most and what the team is working on.
Read definition →First Response Time
First response time (FRT) is the duration between a customer submitting a support request and receiving the first meaningful reply from a human agent. It is one of the most important support metrics because it directly affects customer satisfaction. Faster first responses signal that a company values its customers, even when the full resolution takes longer.
Read definition →Help Desk
A help desk is a system for managing, tracking, and resolving customer support requests. It provides a centralized inbox where support agents receive tickets, assign them, track status, and measure performance. Modern help desks integrate with product tools so that support conversations inform feature prioritization and bug fixes.
Read definition →ICE Framework
The ICE framework is a lightweight scoring model for prioritizing features and experiments. Each item is rated on three dimensions: Impact (how much it moves a key metric), Confidence (how certain you are in the estimate), and Ease (how simple it is to implement). ICE trades the granularity of RICE for speed, making it ideal for teams that need quick prioritization decisions without extensive data.
Read definition →Idea Management
Idea management is the systematic process of collecting, evaluating, and implementing ideas from users, employees, or stakeholders. It goes beyond simple suggestion collection by adding structure for scoring, prioritizing, and tracking ideas through a pipeline from submission to delivery. Effective idea management connects user creativity to product execution.
Read definition →Impact Mapping
Impact mapping is a strategic planning technique that connects business goals to deliverables through a structured map. It works backward from a goal to identify actors (who can influence the outcome), impacts (how their behavior needs to change), and deliverables (what the team can build to create that change). It prevents teams from building features that do not connect to outcomes.
Read definition →Jobs to Be Done
Jobs to Be Done (JTBD) is a framework for understanding why customers buy or use a product. Instead of focusing on demographics or features, JTBD asks what "job" the customer is trying to accomplish. A job is the progress a person seeks in a specific circumstance. Products succeed when they help customers complete their jobs better than alternatives.
Read definition →Kano Model
The Kano model is a framework for classifying product features based on their relationship to customer satisfaction. It defines five categories: must-be (expected basics), one-dimensional (more is better), attractive (unexpected delighters), indifferent (no impact), and reverse (actively unwanted). The model helps teams balance investments between table-stakes functionality and differentiating features.
Read definition →Knowledge Base
A knowledge base is a self-service library of articles, guides, FAQs, and documentation that helps users solve problems without contacting support. It reduces support ticket volume, speeds up resolution for common issues, and improves the overall customer experience. An effective knowledge base is searchable, well-organized, and continuously updated based on real user questions.
Read definition →MoSCoW Method
The MoSCoW method is a prioritization technique that sorts requirements into four categories: Must have (critical for launch), Should have (important but not essential), Could have (desirable if time permits), and Won't have (explicitly excluded for now). It is widely used in agile and project management to set clear expectations about scope and delivery.
Read definition →Net Promoter Score
Net Promoter Score (NPS) is a customer loyalty metric based on a single question: "How likely are you to recommend this product to a friend or colleague?" Respondents answer on a 0-10 scale. Those scoring 9-10 are promoters, 7-8 are passives, and 0-6 are detractors. NPS is calculated by subtracting the percentage of detractors from the percentage of promoters, yielding a score between -100 and +100.
Read definition →North Star Metric
A north star metric is the single metric that best captures the core value your product delivers to customers. It aligns every team around one measurable outcome that reflects real user value, not just business revenue. The right north star metric correlates with long-term growth because it measures whether users are getting what they came for.
Read definition →Product Backlog
A product backlog is an ordered list of everything a product team believes it needs to build, fix, or improve. It serves as the single source of work for the development team and is continuously refined as user feedback, market conditions, and business goals evolve. The product owner maintains the backlog and decides priority.
Read definition →Product Discovery
Product discovery is the process of deciding what to build before committing engineering resources. It involves understanding user problems, generating solutions, and testing assumptions through prototypes and experiments. The goal is to reduce risk by validating that a solution is valuable, usable, feasible, and viable before full development begins.
Read definition →Product Operations
Product operations (product ops) is a function that supports product managers by streamlining processes, managing tools, and surfacing data. Product ops teams handle the operational work that enables PMs to focus on strategy and discovery. They standardize how feedback is collected, how experiments are tracked, and how insights flow between teams.
Read definition →Product Strategy
Product strategy is the high-level plan that connects your product vision to execution. It defines who your target users are, what problems you solve for them, how you differentiate from competitors, and what outcomes you aim to achieve. A strong product strategy turns user feedback and market insight into a focused roadmap instead of a scattered list of features.
Read definition →Product-Market Fit
Product-market fit is the point where a product satisfies strong market demand. It means you have found a group of users who need what you have built and are willing to pay for it, recommend it, or depend on it. Measuring product-market fit requires combining quantitative signals like retention and NPS with qualitative feedback about why users stay or leave.
Read definition →Public Roadmap
A public roadmap is a product roadmap shared externally with customers, showing planned, in-progress, and completed features. It gives users visibility into what the team is building and why. Public roadmaps build trust by demonstrating that user feedback influences product direction. They also reduce inbound support questions about when specific features will ship.
Read definition →Release Notes
Release notes are documentation that describes the changes, improvements, and fixes included in a software release. They inform users about what is new, what has changed, and what has been fixed. Well-written release notes close the feedback loop by showing users that their requests were heard and acted upon, building trust and encouraging continued engagement.
Read definition →RICE Framework
The RICE framework is a quantitative scoring model for prioritizing features and projects. It evaluates each item on four dimensions: Reach (how many users it affects), Impact (how much it moves a key metric), Confidence (how certain you are in your estimates), and Effort (how much time it takes to build). The formula produces a single score that enables objective comparison across competing ideas.
Read definition →Self-Service
Self-service is the practice of enabling customers to find answers, resolve issues, and complete tasks without human assistance. It includes knowledge bases, FAQ pages, community forums, in-app help widgets, and automated troubleshooting flows. Effective self-service reduces support costs, improves response times, and gives users the autonomy they prefer.
Read definition →SLA (Service Level Agreement)
A service level agreement (SLA) is a commitment that defines the expected level of service a company will provide, including response times, resolution targets, and uptime guarantees. SLAs set measurable standards for support quality and create accountability between the company and its customers. They are common in B2B and enterprise contracts.
Read definition →Sprint Planning
Sprint planning is the agile ceremony where the team decides what work to commit to in the upcoming sprint. The product owner presents prioritized backlog items, the team discusses scope and feasibility, and together they agree on a sprint goal. Effective sprint planning connects user feedback to concrete development commitments within a fixed timebox.
Read definition →User Story
A user story is a short description of a feature written from the end user's perspective, typically following the format "As a [user], I want [goal], so that [benefit]." It captures what a user needs and why, without prescribing how to build it. User stories keep development teams focused on delivering value rather than completing tasks.
Read definition →Value Hypothesis
A value hypothesis is a testable assumption about why customers will use your product. It states the specific value a user will receive and the evidence that would prove or disprove it. Validating the value hypothesis early prevents teams from building products that work technically but fail to solve a real problem users care about.
Read definition →Voice of the Customer
Voice of the Customer (VoC) is a research methodology for capturing customer needs, expectations, and preferences. It involves collecting feedback through surveys, interviews, support interactions, and feedback boards, then analyzing that data to understand what customers truly value. VoC programs turn scattered user input into structured insights that drive product, marketing, and support decisions.
Read definition →