Top 100 Vocabulary for Adults | Product Management Professionals
Product management vocabulary is the language of deciding what should be built, for whom, why now, and how success will be known. Product professionals sit between customer problems, business constraints, technology, design, data and delivery. Their job is less about owning every answer than about keeping the decision system coherent.
This profession-specific flagship belongs to the eduKate Adult Vocabulary for Professionals system. It complements Data & Analytics Professionals, AI & Machine Learning Professionals and Software & Technology Professionals.
The Four Banks
Customer & Discovery: customer, user, segment, persona, need, problem, pain point, job to be done, outcome, behaviour, workflow, context, interview, observation, research, evidence, insight, assumption, hypothesis, discovery, validation, desirability, usability, accessibility, adoption.
Strategy & Prioritisation: vision, mission, strategy, objective, key result, positioning, differentiation, value proposition, market, competition, opportunity, constraint, trade-off, priority, roadmap, theme, initiative, bet, option, sequencing, dependency, opportunity cost, focus, portfolio, product-market fit.
Delivery & Experimentation: requirement, user story, acceptance criteria, scope, MVP, prototype, experiment, A/B test, feature, release, launch, milestone, backlog, sprint, iteration, design, engineering, QA, bug, defect, telemetry, instrumentation, rollout, rollback, deprecation.
Metrics & Stakeholders: metric, north star metric, KPI, activation, conversion, engagement, retention, churn, cohort, funnel, lifetime value, revenue, margin, cost, growth, impact, outcome measure, leading indicator, lagging indicator, stakeholder, alignment, buy-in, executive sponsor, communication, accountability.
Top 100 Product Management Vocabulary: Working Meanings
| # | Word | Professional meaning |
|---|---|---|
| 1 | Customer | A person or organisation receiving or purchasing product value. |
| 2 | User | The person actually interacting with the product. |
| 3 | Segment | A defined group sharing relevant needs or behaviours. |
| 4 | Persona | A research-informed representation of a user type. |
| 5 | Need | A desired outcome or problem requiring resolution. |
| 6 | Problem | A condition preventing the user from achieving a desired outcome. |
| 7 | Pain point | A specific source of friction, cost or dissatisfaction. |
| 8 | Job to be done | The progress a user is trying to make in a given situation. |
| 9 | Outcome | The result the user or business wants to achieve. |
| 10 | Behaviour | Observable user action in context. |
| 11 | Workflow | A sequence of tasks through which a user completes work. |
| 12 | Context | The circumstances shaping how and why a product is used. |
| 13 | Interview | A structured conversation used to understand users and needs. |
| 14 | Observation | Direct study of how people behave in real settings. |
| 15 | Research | Structured investigation used to reduce uncertainty. |
| 16 | Evidence | Information supporting or challenging a product decision. |
| 17 | Insight | A useful interpretation that changes understanding of a user or problem. |
| 18 | Assumption | A proposition accepted without complete proof. |
| 19 | Hypothesis | A testable proposition about user behaviour or product effect. |
| 20 | Discovery | Work intended to understand problems, opportunities and uncertainty before or during delivery. |
| 21 | Validation | Testing whether a problem, solution or assumption holds under evidence. |
| 22 | Desirability | The degree to which users want or value a solution. |
| 23 | Usability | The ease and effectiveness with which users can use a product. |
| 24 | Accessibility | The degree to which people with different abilities can use a product. |
| 25 | Adoption | Actual use of a product or feature by intended users. |
| 26 | Vision | A compelling description of the future the product seeks to create. |
| 27 | Mission | The enduring purpose the product or organisation serves. |
| 28 | Strategy | A system of choices about where and how the product will compete or create value. |
| 29 | Objective | A defined result the product team aims to achieve. |
| 30 | Key result | A measurable outcome indicating progress toward an objective. |
| 31 | Positioning | The place a product seeks to occupy in the customer’s mind. |
| 32 | Differentiation | A meaningful distinction from alternatives. |
| 33 | Value proposition | The reason a target customer should choose the product. |
| 34 | Market | The environment of customers, alternatives and transactions relevant to the product. |
| 35 | Competition | Alternative products, services or behaviours competing for the same need. |
| 36 | Opportunity | A customer or business problem worth pursuing. |
| 37 | Constraint | A limit restricting product choices. |
| 38 | Trade-off | A gain in one dimension requiring cost elsewhere. |
| 39 | Priority | A problem or initiative deliberately given precedence. |
| 40 | Roadmap | A high-level view of intended product direction and sequencing. |
| 41 | Theme | A broad strategic area organising product work. |
| 42 | Initiative | A coordinated body of work aimed at an outcome. |
| 43 | Bet | A product decision made under uncertainty with an expected payoff. |
| 44 | Option | A possible course of product action retained for future choice. |
| 45 | Sequencing | The deliberate ordering of product work. |
| 46 | Dependency | A condition or work item on which another outcome relies. |
| 47 | Opportunity cost | The value of the best alternative forgone. |
| 48 | Focus | Concentration on the few product problems that matter most. |
| 49 | Portfolio | A collection of products or initiatives managed together. |
| 50 | Product-market fit | A state in which a product strongly satisfies a meaningful market need. |
| 51 | Requirement | A condition the product or feature must satisfy. |
| 52 | User story | A concise description of desired user value from a particular perspective. |
| 53 | Acceptance criteria | Conditions defining when work meets agreed expectations. |
| 54 | Scope | The boundaries of what is included in a piece of work. |
| 55 | MVP | Minimum viable product: the smallest viable product version that can test important assumptions or deliver core value. |
| 56 | Prototype | An early representation used to test form, behaviour or concept. |
| 57 | Experiment | A structured test designed to learn about an assumption or effect. |
| 58 | A/B test | A controlled comparison of two product variants. |
| 59 | Feature | A product capability designed to create user or business value. |
| 60 | Release | A version of product functionality made available for use. |
| 61 | Launch | The coordinated introduction of a product or feature to users or market. |
| 62 | Milestone | A significant checkpoint in product delivery or adoption. |
| 63 | Backlog | A prioritised list of potential product work. |
| 64 | Sprint | A time-boxed development period in some agile methods. |
| 65 | Iteration | A cycle of building, learning and revising. |
| 66 | Design | The shaping of product experience, interaction and form. |
| 67 | Engineering | The technical work required to build and operate the product. |
| 68 | QA | Quality assurance activities intended to prevent and detect product defects. |
| 69 | Bug | An unintended software behaviour or defect. |
| 70 | Defect | A failure to meet required product behaviour. |
| 71 | Telemetry | Product usage and system data collected from live operation. |
| 72 | Instrumentation | Implementation of measurement events and signals within a product. |
| 73 | Rollout | Controlled expansion of a feature or product to more users. |
| 74 | Rollback | Reversion to an earlier product version after a problem. |
| 75 | Deprecation | Planned retirement of a feature, API or capability. |
| 76 | Metric | A defined quantitative measure of product behaviour or performance. |
| 77 | North star metric | A primary measure intended to represent delivered customer value over time. |
| 78 | KPI | A key performance indicator linked to an important objective. |
| 79 | Activation | The point at which a new user first experiences meaningful product value. |
| 80 | Conversion | Movement from one desired user or commercial stage to another. |
| 81 | Engagement | Meaningful product use or interaction. |
| 82 | Retention | Continued product use over time. |
| 83 | Churn | Loss of users or customers. |
| 84 | Cohort | A group of users sharing a defined start point or characteristic. |
| 85 | Funnel | A sequence of stages through which users progress. |
| 86 | Lifetime value | Estimated economic value generated across a customer relationship. |
| 87 | Revenue | Income generated by the product. |
| 88 | Margin | The difference between revenue and specified costs. |
| 89 | Cost | Resources consumed to build, operate or support the product. |
| 90 | Growth | Increase in users, usage, revenue or another chosen measure. |
| 91 | Impact | The significance of product change on users or business. |
| 92 | Outcome measure | A metric showing whether the intended user or business result changed. |
| 93 | Leading indicator | A measure expected to move before a later outcome. |
| 94 | Lagging indicator | A measure reflecting an outcome after it has occurred. |
| 95 | Stakeholder | A person or group influencing or affected by product decisions. |
| 96 | Alignment | Shared understanding of direction, priorities and trade-offs. |
| 97 | Buy-in | Active stakeholder support for a product direction or decision. |
| 98 | Executive sponsor | A senior leader providing organisational support and decision authority. |
| 99 | Communication | Clear exchange of product reasoning, evidence and decisions. |
| 100 | Accountability | Obligation to answer for product decisions and outcomes. |
A Roadmap Is Not a Promise Calendar
A useful roadmap communicates direction, priorities and sequencing under uncertainty. When every item becomes a fixed date commitment before evidence is sufficient, the roadmap stops being a strategic instrument and becomes a delivery queue.
Scenario: Users Ask for a Feature
Do not stop at the requested solution. Ask what they are trying to achieve, how they solve it today, how often the problem occurs, what the cost is and whether other users share the need. The request is evidence, but it is not yet the product requirement.
Seven-Day Product Management Vocabulary Plan
| Day | Practice |
|---|---|
| 1 | Separate user, customer, problem, need and outcome. |
| 2 | Turn assumptions into testable hypotheses. |
| 3 | Map vision, strategy, priority and roadmap. |
| 4 | Design one MVP or experiment around the riskiest assumption. |
| 5 | Audit product metrics for customer value and behaviour. |
| 6 | Recall 75+ product terms by function. |
| 7 | Write a one-page product brief connecting evidence, trade-offs, outcome and next decision. |
Complete the Digital Profession Wing
- Cybersecurity Professionals
- Data & Analytics Professionals
- AI & Machine Learning Professionals
- Software & Technology Professionals
Conclusion
Product-management vocabulary creates discipline around choice. It helps professionals distinguish requests from problems, output from outcome, roadmaps from promises and activity from evidence that the product is genuinely becoming more useful.