Product Management Glossary
Product strategy and execution — discovery, prioritization frameworks, agile methods, OKRs, and building products users love.
Acceptance Criteria
Specific, testable conditions that a user story must satisfy to be considered complete. Acceptance criteria define the boundaries of a feature by specifying expected behavior, edge cases, and quality requirements in unambiguous terms.
Agile
A set of values and principles for software development that prioritizes individuals and interactions, working software, customer collaboration, and responding to change. Agile emphasizes iterative delivery and continuous feedback over rigid planning.
Assumption Mapping
A technique for identifying and prioritizing the assumptions underlying a product idea based on their importance and the team's confidence in them. High-importance, low-confidence assumptions are tested first to reduce risk early.
Build-Measure-Learn
The core feedback loop of the Lean Startup methodology. Teams build a small experiment, measure how users respond with quantitative and qualitative data, then learn whether to iterate, pivot, or scale the approach.
Continuous Discovery
A practice where product teams conduct regular, ongoing discovery activities rather than treating research as a discrete phase. Teams interview users weekly, run experiments continuously, and constantly refine their understanding of customer needs.
Definition of Done
A shared checklist of activities that must be completed before any work item is considered finished. The Definition of Done ensures consistent quality across the team by making quality standards explicit and non-negotiable.
Design Sprint
A five-day structured process for rapidly prototyping and testing ideas with real users. Developed at Google Ventures, it compresses months of debate into a focused week of mapping, sketching, deciding, prototyping, and testing.
Design Thinking
A human-centered approach to innovation that integrates the needs of people, the possibilities of technology, and the requirements for business success. It follows five stages: empathize, define, ideate, prototype, and test.
Dogfooding
The practice of using your own product internally before releasing it to customers. By experiencing the product as users do, teams discover bugs, usability issues, and missing features that might otherwise go unnoticed.
Dual-Track Agile
An approach that runs product discovery and product delivery as parallel, synchronized tracks. The discovery track validates what to build through research and experiments while the delivery track builds validated solutions in sprints.
Experiment Design
The structured process of creating controlled tests to validate product hypotheses. Good experiment design specifies the hypothesis, metrics, sample size, duration, success criteria, and potential confounds before the experiment begins.
Feature Creep
The gradual, uncontrolled addition of features beyond a product's original scope. Feature creep dilutes focus, increases complexity, delays releases, and often results in a product that does many things poorly instead of a few things well.
Impact Mapping
A strategic planning technique that connects business goals to deliverables through a four-level map: Why (goal), Who (actors), How (behavior changes), and What (deliverables). It ensures every feature traces back to a measurable business impact.
Jobs to Be Done
A framework that defines customer needs as functional, emotional, and social jobs people hire products to accomplish. It shifts focus from demographic segments to the underlying progress customers are trying to make in specific circumstances.
Kanban
A workflow management method that visualizes work, limits work-in-progress, and optimizes flow. Unlike Scrum's fixed sprints, Kanban uses a continuous flow model where items move through stages as capacity becomes available.
Kano Model
A theory of product development that classifies features into categories based on how they affect customer satisfaction: basic needs, performance needs, and delight factors. It reveals that not all features contribute equally to user happiness.
Lean Startup
A methodology for developing businesses and products through validated learning, rapid experimentation, and iterative releases. It emphasizes reducing waste by testing assumptions before building fully-featured solutions.
Minimum Lovable Product
An evolution of the MVP concept that emphasizes delivering enough quality and delight that early users genuinely love the product. It balances speed-to-market with the emotional engagement needed to drive organic word-of-mouth growth.
Minimum Viable Product
The simplest version of a product that can be released to test a core hypothesis with real users. An MVP delivers just enough functionality to gather validated learning while minimizing development time and cost.
MoSCoW Method
A prioritization technique that categorizes requirements into Must-have, Should-have, Could-have, and Won't-have. It creates clear alignment on what is essential for a release versus what can be deferred or dropped entirely.
Now-Next-Later
A roadmapping format that organizes initiatives into three time horizons without committing to specific dates. Now items are in active development, Next items are planned soon, and Later items are being explored or researched.
OKR Framework
Objectives and Key Results is a goal-setting methodology that pairs ambitious qualitative objectives with measurable key results. OKRs align teams around outcomes rather than outputs, creating focus and accountability across the organization.
Opportunity Solution Tree
A visual framework that maps the path from a desired outcome through opportunities discovered in user research to potential solutions and the experiments that validate them. It ensures every initiative connects clearly to a measurable business outcome.
Pivot
A structured course correction that tests a new fundamental hypothesis about a product, strategy, or growth engine. A pivot changes direction while preserving the validated learning accumulated from previous experiments.
Prioritization Matrix
A visual tool that plots potential initiatives on two axes, typically impact versus effort, to facilitate objective comparison and decision-making. It transforms subjective debates into structured conversations by forcing explicit evaluation on defined criteria.
Product Analytics
The practice of collecting, analyzing, and acting on user behavior data to improve product decisions. Product analytics tracks how users interact with features, where they drop off, and what actions correlate with retention and revenue.
Product Debt
The accumulated cost of past product decisions that were expedient at the time but create ongoing friction, confusion, or inefficiency. Product debt manifests as inconsistent UX patterns, unused features, and convoluted user flows.
Product Discovery
The ongoing process of determining what to build by identifying user needs, exploring solutions, and validating assumptions before committing development resources. Discovery reduces the risk of building products nobody wants.
Product Enablement
The practice of equipping customer-facing teams with the knowledge, tools, and resources they need to effectively communicate product value. It bridges the gap between product development and go-to-market execution through training, documentation, and playbooks.
Product Metrics
Quantitative measurements that indicate how well a product is performing against its goals. Core product metrics typically include acquisition, activation, engagement, retention, and revenue, often organized into a framework like pirate metrics or the North Star metric.
Product Operations
A function that supports product teams by streamlining processes, managing tools, synthesizing customer insights, and facilitating data-driven decision-making. Product ops removes operational burden from product managers so they can focus on discovery and strategy.
Product Principles
A set of guiding beliefs that shape how a product team makes decisions. Product principles codify the team's values and trade-off preferences, enabling decentralized decision-making that remains consistent with the overall product direction.
Product Roadmap
A strategic document that communicates the planned direction and priorities for a product over time. Effective roadmaps focus on outcomes and problems to solve rather than committing to specific features or fixed delivery dates.
Product Sense
The intuitive ability to understand what makes a product great, identify user needs, and predict how design decisions will affect user behavior. Product sense combines empathy, analytical thinking, and pattern recognition developed through experience.
Product Strategy
The high-level plan that connects a product vision to executable goals by defining target users, core value proposition, competitive differentiation, and the sequence of moves needed to win in the market over time.
Product Trio
A cross-functional team of three roles, product manager, designer, and tech lead, who collaborate closely on product discovery decisions. The trio ensures business viability, user desirability, and technical feasibility are considered together from the start.
Product Vision
An aspirational description of the future state a product aims to create for its users and the world. A compelling product vision inspires the team, guides strategic decisions, and communicates purpose to stakeholders and customers.
Product-Led Sales
A go-to-market strategy where the product experience generates and qualifies sales leads. Sales teams focus on users who have already experienced product value, resulting in shorter sales cycles, higher conversion rates, and more efficient revenue growth.
Product-Market Fit
The degree to which a product satisfies strong market demand. Achieving product-market fit means customers are actively seeking, using, and recommending your product because it solves a real and pressing problem for them.
Product-Qualified Account
An account identified as a strong sales prospect based on product usage patterns rather than demographic or firmographic data alone. PQAs show behavioral signals indicating readiness to purchase, such as high engagement, team adoption, or feature exploration.
RICE Framework
A prioritization scoring model that evaluates initiatives based on Reach, Impact, Confidence, and Effort. The RICE score is calculated as (Reach times Impact times Confidence) divided by Effort, producing a comparable ranking across diverse projects.
Scope Creep
The uncontrolled expansion of a project's scope after work has begun, typically through new requirements, expanded features, or shifting goals. Unlike feature creep which affects the product broadly, scope creep happens within a specific initiative or sprint.
Scrum
An agile framework that organizes work into fixed-length sprints, typically two weeks, with defined roles, ceremonies, and artifacts. Scrum provides structure through sprint planning, daily standups, sprint reviews, and retrospectives.
Sprint Velocity
A measure of the amount of work a team completes during a single sprint, typically expressed in story points. It serves as a planning tool for forecasting how much work the team can handle in future sprints based on historical performance.
Stakeholder Management
The process of identifying, analyzing, and strategically engaging the people who influence or are affected by product decisions. Effective stakeholder management builds alignment, manages expectations, and ensures the product team can execute with appropriate autonomy.
Story Mapping
A visual exercise that organizes user stories into a two-dimensional map showing the user journey horizontally and priority vertically. It helps teams see the big picture of a product while planning incremental releases.
Technical Spike
A time-boxed investigation designed to answer a specific technical question or reduce uncertainty before committing to a development approach. Spikes produce knowledge and recommendations rather than shippable product increments.
Usability Testing
A method of evaluating a product by testing it with representative users who perform specific tasks while observers note difficulties and confusion. It reveals interface problems that internal teams are too familiar with the product to notice.
User Research
The systematic study of target users to understand their behaviors, needs, motivations, and pain points. Methods include interviews, surveys, observation, diary studies, and analytics analysis to inform product decisions with evidence.
User Story
A short, informal description of a feature written from the user's perspective in the format: As a [type of user], I want [action] so that [benefit]. User stories capture requirements in terms of user value rather than technical specifications.