Glossary

Clear, practitioner-oriented definitions of key product management concepts.

A/B Testing

Controlled experiment comparing two product variants to measure the causal effect of a change on user behavior. The gold standard for validating that changes drive desired outcomes.

The percentage of new users who complete their first key action or experience the core value proposition shortly after signing up. Activation is measured as: users who achieve a defined activation milestone divided by total new users in a period. High activation rates indicate the product's value is clear; low rates indicate onboarding or product problems.

API-First Design

The architectural practice of designing APIs before implementation, making the contract between systems explicit and enabling parallel development across teams.

Assumption Mapping

Structured process for identifying and testing the beliefs underlying a product strategy or feature. Separates what you know from what you're guessing about.

Blue Ocean Strategy

A competitive strategy where you create new, uncontested markets (blue oceans) rather than competing in existing markets with known competitors (red oceans). Blue ocean strategy focuses on value innovation—simultaneously pursuing differentiation and low cost—to make competition irrelevant.

Business Model Canvas

A one-page strategic management template that visualizes nine key components of a business model: customer segments, value propositions, channels, customer relationships, revenue streams, key resources, key activities, key partnerships, and cost structure.

Chief Product Officer

The executive responsible for defining product strategy, building product leadership capability within the organization, and driving strategic alignment across all customer-facing functions. The CPO operates at the board level and is accountable for the mechanisms through which the organization creates and captures value.

Churn Rate

The percentage of customers who stop using a product during a given period. Monthly churn rate is calculated as: customers lost in a month divided by total customers at the start of the month. Churn is the inverse of retention—lower churn indicates higher LTV and stronger business fundamentals.

Cohort Analysis

Behavioral analysis technique that groups users by shared characteristics or time periods, then compares outcomes across cohorts. Reveals how user segments respond differently to changes.

Competitive Analysis

A systematic evaluation of competitor products, strategies, and market positioning to identify gaps, threats, and opportunities. It informs product strategy by revealing where your product can differentiate and where it risks commoditization.

Continuous Delivery

The practice of building, testing, and packaging software so that it can be released to production at any time. The decision to release is business-driven, not engineering-blocked.

Continuous Discovery

Continuous discovery is the practice of conducting regular, ongoing customer research — typically weekly — to continuously inform product decisions rather than relying on periodic large-scale research efforts.

Continuous Integration

The practice of merging code changes into a central repository multiple times per day, with automated testing on every commit to catch integration issues early.

Cross-Functional Team

A team bringing together people with different specialties (engineering, design, product, data) working toward a shared goal. The diverse skills reduce handoffs and enable faster iteration.

Customer Acquisition Cost

The average cost to acquire one paying customer. CAC is calculated as: total sales and marketing spend in a period divided by number of new customers acquired in that period. CAC varies significantly by acquisition channel and determines how much you can profitably spend to grow.

Customer Interview

Structured one-on-one conversation with a user or customer designed to explore their context, motivations, problems, and decision-making. Core tool for discovery and validation research.

Customer Journey Map

Visual representation of a user's experience across all touchpoints with a product or service, from initial awareness through ongoing use. Reveals pain points and opportunities.

Customer Lifetime Value

The total revenue a company expects to generate from a customer over the entire relationship. LTV is calculated as: average revenue per user × average customer lifespan. LTV determines how much you can spend on acquisition and what you must achieve on retention to have a viable business.

Definition of Done

The explicit checklist of quality criteria, testing, and documentation requirements that must be met before work is considered complete. It's the contract that makes velocity meaningful.

Design Sprint

Time-boxed (typically 5-day) structured process to prototype, test, and validate product ideas rapidly. Compresses months of design-test cycles into a focused week.

Design Thinking

Problem-solving methodology centered on empathy for users, rapid prototyping, and iterative testing. Emphasizes understanding context before jumping to solutions.

DevOps

The operational model where development and infrastructure teams collaborate to automate deployment, monitoring, and incident response, reducing the time between code and production value.

Disruption Theory

A framework explaining how new entrants with inferior products displace incumbents by serving overlooked customer segments with better performance on dimensions those segments care about. Disruption is distinct from innovation—innovations improve along dimensions that matter to incumbent customers, while disruptions compete on different dimensions.

Dual-Track Agile

A product delivery model where discovery and delivery work in parallel: one track explores and validates ideas (research, prototyping, user testing), the other executes on validated work.

Empathy Map

Visualization of a user segment's mindset, structured around what they think, feel, say, do, hear, and see. Deepens understanding of user motivations and constraints.

Executive Alignment

The state in which senior executives (CEO, CFO, CTO, Chief Product Officer) share a common understanding of product strategy, prioritized outcomes, and the trade-offs being made. Executive alignment is prerequisite for rapid execution—misalignment at the top cascades down and slows decision-making throughout the organization.

Experiment-Driven Development

Product development methodology where most decisions are validated through controlled experiments rather than expert judgment or user research alone. Creates a culture of evidence-based iteration.

Feature Flag

Code-level switch that enables or disables a feature without requiring code deployment. Infrastructure for safe experimentation, gradual rollout, and easy rollback.

Feature Team

A cross-functional team organized around delivering a specific product capability or feature, owning the full stack from design to operations. Team members report to the same leader and share a common goal.

Freemium Model

A business model offering a free version of a product with basic functionality to acquire users at scale, while monetizing through a paid premium version with advanced features. Success requires high free-to-paid conversion, sufficient free value to retain users, and sustainable unit economics.

Funnel Analysis

Measurement of user progression through sequential steps (signup → onboarding → first action → purchase). Identifies where users drop off and reveals conversion bottlenecks.

Go-to-Market Strategy

The plan and execution for bringing a product to market and acquiring customers. It encompasses target customer definition, positioning, channels, sales process, and success strategies. Go-to-market (GTM) is distinct from product strategy—you can have an excellent product with a poor GTM.

Hypothesis-Driven Development

Product development methodology where decisions are framed as testable hypotheses with predicted outcomes. Shifts from opinion-based to evidence-based decision-making.

Impact Mapping

A strategic planning technique that visualizes how product changes cascade from output (features built) through user behavior change (adoption) to desired business outcomes. Impact maps create causal links between activities and outcomes, making assumptions explicit and testable.

Jobs to Be Done

A framework for understanding customer motivation by focusing on the specific outcome a customer seeks to achieve rather than their demographics or explicit requests. JTBD assumes customers 'hire' products to get a job done in a particular circumstance.

Kanban

A pull-based workflow system where work flows through defined states (To-Do, In Progress, Review, Done), with explicit limits on work-in-progress to prevent bottlenecks and reduce context-switching.

KPIs vs. Metrics

KPIs (Key Performance Indicators) are critical health measurements tied to business outcomes, while metrics are individual data points used for analysis. Every KPI is a metric, but not every metric is a KPI—KPIs are the subset you track and act on regularly.

Land and Expand

A growth strategy where you initially establish a foothold in a customer account (land) with a narrow product or use case, then systematically expand to adjacent use cases, departments, or products (expand) to grow customer lifetime value. This is particularly effective in B2B where usage spreads internally.

Lean Canvas

A streamlined version of the Business Model Canvas designed for startups and early-stage companies, replacing 'customer segments' and 'key partnerships' with 'problem' and 'solution' to emphasize problem-solution fit before building a full business model.

Market Segmentation

The division of a broader market into distinct subgroups (segments) with different needs, behaviors, or characteristics. Effective segmentation allows focused product development and targeted go-to-market strategies rather than building one product for everyone.

Microservices

An architectural pattern where a product is composed of loosely-coupled, independently-deployable services communicating through APIs. Each service owns a distinct business capability and its own data store.

Minimum Viable Product

The smallest set of capabilities required to test a critical hypothesis about customer demand and willingness to pay. An MVP is designed to learn, not to satisfy; it trades completeness for speed of validated learning.

Monolith-to-Microservices Migration

The process of decomposing a monolithic application into independent microservices, typically driven by scaling constraints, team growth, or deployment velocity needs.

Net Promoter Score

A metric that measures customer satisfaction and loyalty by asking customers how likely they are (0-10 scale) to recommend the product to a friend or colleague. NPS is calculated as: percentage of promoters (9-10) minus percentage of detractors (0-6). NPS ranges from -100 to +100.

Network Effects

The phenomenon where the value of a product increases as more people use it. Network effects create a self-reinforcing cycle where each new user makes the product more valuable for existing users, enabling exponential growth and building defensible competitive advantages.

North Star Metric

The single primary metric that measures progress toward your product's strategic outcome, serving as the guiding star for all cross-functional decisions. It is the operational definition of the value your product delivers to customers.

OKRs

Objectives and Key Results—a goal-setting framework that defines what an organization wants to achieve (Objectives) and how it will measure success (Key Results). OKRs cascade from company strategy to individual execution, creating alignment across departments.

Opportunity Solution Tree

A strategic planning framework that maps customer opportunities to solutions and experiments, ensuring alignment between discovery and delivery. It moves teams from stating desired outcomes to systematically testing which customer problems are worth solving.

Outcome vs. Output

The critical distinction between what an organization produces (output: features, code, campaigns) and the measurable business result that output creates (outcome: increased revenue, reduced churn, improved retention). Outcome-focused organizations measure success by business results; output-focused organizations measure success by activities completed.

Pirate Metrics

A framework for measuring product-market fit and growth using five key stages: Acquisition (how do users find you?), Activation (do users have a good initial experience?), Retention (do users come back?), Revenue (how do you make money?), and Referral (do users recommend you?). AARRR is a mnemonic for this framework.

Platform Strategy

A business strategy where you build infrastructure that enables multiple parties (developers, sellers, creators, users) to create value for each other. Platforms create network effects, where value grows as more participants join. Examples: app stores, marketplaces, operating systems, and API ecosystems.

Platform Team

A specialized team that builds and maintains infrastructure, tools, and shared services enabling feature teams to work faster. They own databases, CI/CD pipelines, monitoring, and framework libraries.

Pricing Strategy

The approach to setting customer prices for products or services. Pricing strategy balances capturing customer value, sustaining profitability, and remaining competitive. It's distinct from price point (the actual price) and encompasses the value and economic rationale behind pricing decisions.

Product Analytics

The discipline of measuring user behavior, engagement, and outcomes to inform product decisions. Product analytics transforms raw behavioral data into actionable insight about what is working, what is not, and why.

Product Backlog

The prioritized inventory of work items—features, bugs, technical debt, and experiments—representing everything the product needs. It's the single source of truth for what will be built.

Product Channel Fit

The alignment between your product's characteristics and your chosen distribution channel. Good product-channel fit means the product's complexity, price point, customer support needs, and sales cycle naturally fit the channel. Poor fit results in high CAC and low conversion.

Product Council

A regular cross-functional governance forum where senior leaders from product, engineering, design, sales, marketing, and customer success align on strategy, review progress against outcomes, and make major trade-off decisions. The product council is the primary mechanism through which strategy becomes organizational action.

Product Culture

The shared beliefs, practices, and decision-making norms that define how an organization approaches product work. Product culture encompasses what gets rewarded, how trade-offs are made, how evidence is weighted, and what behaviors indicate success.

Product Debt

Quality or architectural decisions made for speed that create future costs. Product debt includes: technical debt (code quality, system design issues), design debt (UI/UX compromises), data debt (incomplete or low-quality data infrastructure), and organizational debt (processes and structures optimized for short-term speed). Debt compounds over time and eventually constrains growth.

Product Differentiation

The set of unique capabilities, approach, or outcomes that distinguish a product from competitors in the same category. Differentiation is the reason customers choose you over alternatives when multiple options exist.

Product Discovery

Product discovery is the systematic process of identifying which products or features to build by validating customer needs, business viability, technical feasibility, and usability before committing development resources.

Product Governance

The structural mechanisms through which an organization makes and enforces product decisions. Governance includes decision-making authority boundaries, approval gates, budget allocation processes, metric review cadences, and escalation protocols that translate strategy into consistent execution.

Product Launch

The coordinated release of a product or significant feature to the market, accompanied by go-to-market execution to drive awareness and adoption. A launch is not the moment code ships; it is the orchestration of product, messaging, and customer acquisition.

Product Leadership

The executive function responsible for setting product strategy, defining value creation mechanisms, and aligning organizational incentives around customer outcomes. Product leadership operates at the strategic level, directly shaping how capital, authority, and attention flow within the organization.

Product Lifecycle

The sequence of phases a product moves through from launch to maturity to decline: introduction (early adoption), growth (market expansion), maturity (market saturation), and decline (disruption or obsolescence). Each phase requires distinct strategy.

Product Management

The discipline of governing a product's evolution by connecting customer needs with organizational capability. It integrates strategy, execution, and measurement to deliver sustained competitive advantage and measurable business outcomes.

Product Manager Role

The executive function responsible for defining a product's strategy, requirements, and success metrics. A product manager bridges customer needs, technical constraints, and business objectives to make portfolio-level decisions about what to build and why.

Product Metrics Framework

A structured hierarchy of metrics that defines what success looks like for a product. A framework typically includes north star (one overarching outcome), key results (2-3 major goals), and supporting metrics that indicate progress toward those goals. The framework creates alignment and accountability.

Product Mission

The ongoing, enduring purpose of a product—why it exists and what customer problem it exists to solve. Mission differs from vision in that it describes the permanent raison d'être rather than a future state.

Product Moat

A defensible advantage that protects a product from competition. Moats can be technical (proprietary algorithms), network effects, switching costs, brand, scale economies, or regulatory barriers. Without moats, products compete on features alone, which is expensive and unsustainable.

Product Operating Model

A product operating model is the integrated system of governance, budget allocation, decision authority, team structure, and incentive design that determines how an organization builds, delivers, and evolves its products.

Product Operations

The discipline of designing and governing the processes, systems, and metrics that enable product teams to operate effectively at scale. Product operations provides the infrastructure for product strategy to translate into execution.

Product Owner

The role accountable for ensuring delivered work meets quality standards, aligns with requirements, and delivers measurable value. A product owner bridges the definition of what to build (product management) and how it is built (engineering execution).

Product Portfolio

The collection of products and product variants an organization offers to serve different customer segments or use cases. Portfolio management balances investment across products at different lifecycle stages to optimize aggregate returns and reduce organizational risk.

Product Positioning

How a product is perceived in the market relative to alternatives. Positioning is the narrative that connects product capabilities to customer value, making the reason to choose your product explicit and memorable.

Product Principles

The decision-making values that guide product choices when multiple valid options exist. Principles are the behavioral expression of mission and vision, ensuring consistency in trade-offs across time and teams.

Product Prioritization

Product prioritization is the decision-making process of determining which features, improvements, or initiatives to pursue first based on their expected impact on user outcomes and business goals relative to the effort and risk involved.

Product Qualified Lead

A prospective customer who has demonstrated sufficient product engagement and product-market fit signals to warrant a sales conversation. A PQL has typically activated in a freemium product, used key features, and shown intent to expand. PQLs have higher conversion rates and shorter sales cycles than traditional marketing qualified leads.

Product Requirements Document

A structured specification that translates strategic direction into actionable work. A PRD documents the problem being solved, the proposed solution, success metrics, and acceptance criteria required for execution.

Product Review

A structured evaluation of product performance, progress against targets, and strategic course-correction. Product reviews typically happen monthly or quarterly and ask: Are we hitting our outcomes? If not, why? What do we need to change? Reviews are decision-making events, not reporting events.

Product Roadmap

A product roadmap is a strategic communication tool that shows the planned direction and priorities for a product over time, aligning stakeholders around outcomes rather than committing to a fixed feature timeline.

Product Sense

Intuitive pattern recognition about what product changes drive outcomes. Developed through repeated hypothesis testing, user interaction, and reflection on results.

Product Strategy

Product strategy is the deliberate set of choices about which problems to solve, for which customers, and how to win — translating business objectives into a focused product direction that guides prioritization, resource allocation, and roadmap decisions.

Product Trio

A cross-functional leadership structure comprising a product leader, engineering lead, and design lead who jointly own a product area and make strategic decisions together. The trio model distributes authority across functions while maintaining accountability and forcing collaborative problem-solving.

Product Vision

A statement of the desirable future state a product aspires to create for customers and the organization. Vision provides directional clarity and emotional commitment, grounding decisions about which capabilities to develop and which opportunities to decline.

Product-Led Growth

A go-to-market strategy where product experience itself drives user adoption and expansion, rather than sales, marketing, or partnerships. PLG succeeds when the product is self-explanatory, self-qualifying, and self-expanding.

Product-Market Fit

The state in which a product's capabilities reliably generate measurable value for a defined customer segment such that they willingly adopt it and recommend it. PMF is achieved when organic growth becomes sustainable and churn stabilizes at acceptable levels.

Prototyping

Construction of simplified or partial product models to test ideas, explore design concepts, or gather user feedback before full implementation. Reduces risk and cost of building wrong solutions.

Retention Analysis

Measurement of how long users remain engaged with a product after initial acquisition. Tracks whether users return and how frequently, revealing product-market fit.

Shape-Up

A product delivery methodology that combines shaped work (structured ideas with clear scope but room for implementation decisions) with fixed time-boxed cycles, enabling predictable delivery without detailed upfront planning.

Sprint Planning

The ceremony where a team selects work items from the backlog for a time-boxed development cycle, commits to capacity, and breaks down stories into executable tasks. It's the operational linkage between strategy and execution.

Stakeholder Management

The practice of identifying key stakeholders, understanding their incentives and constraints, and deliberately maintaining alignment throughout product decisions and execution. Stakeholder management recognizes that product work succeeds or fails based on coordination across multiple interests, not just customer needs.

Story Points

A relative unit of effort used to estimate work complexity without committing to clock time. Points capture unknowns, dependencies, and integration work—not just coding effort.

Survey Design

Construction of questionnaires to systematically gather attitudinal and behavioral data from a user population. Enables reaching larger samples but requires rigor to avoid bias.

Switching Costs

The effort, expense, or risk required for a customer to move from your product to a competitor's product. High switching costs create customer lock-in, allowing you to maintain margins and retain customers even when competitors offer superior alternatives.

Team Topologies

The organizational structure and interaction patterns between teams, deliberately designed to minimize cognitive load and communication overhead while enabling fast, independent delivery.

Technical Debt

Accumulated shortcuts, workarounds, and deferred quality investments in code and architecture that reduce velocity and increase operational risk. It compounds when not actively managed.

Throughput

The rate at which a team completes work items—typically measured as features or bugs shipped per unit time. It's the ultimate measure of delivery effectiveness.

Total Addressable Market

The overall revenue opportunity available if a product captured 100% of its target market. TAM is calculated as the number of potential customers multiplied by average selling price, informing whether a market opportunity is large enough to sustain a venture.