Product Management: Key Terms and Vocabulary

Prefer Polish? Read the polish version.

Product Management combines business, technology, and customer knowledge. If you are looking for a product-oriented role, you will often see terms such as product roadmap, backlog, MVP, product discovery, user stories, OKRs, and product-market fit in job descriptions.

This glossary explains common Product Management terms in plain English. It is useful if you are starting a career in Product, preparing for a job interview, or working with a Product team. It also explains how the Product Manager and Product Owner roles can differ, including the Product Owner Scrum context.

1. Product Management

Product Management is the function responsible for deciding what a product should achieve, who it is for, and how it should develop over time.

Product Managers work across Engineering, Design, Marketing, Sales, and Customer Success. Their goal is to build products that solve real customer problems and support business objectives.

2. Product Manager (PM)

A Product Manager is responsible for a product’s direction and development. Depending on the company, the role may include product strategy, customer research, prioritization, the product roadmap, requirements, and measuring product performance.

A Product Manager usually coordinates different teams rather than directly managing every person involved in building the product. For people starting their careers, a junior product manager role can be an entry point into Product Management. Its responsibilities depend on the company and team structure.

3. Product Owner (PO)

A Product Owner is a role commonly associated with Agile and Scrum teams. The Product Owner manages and prioritizes the product backlog and helps the development team focus on the most valuable work.

In some companies, Product Manager and Product Owner are separate roles. In others, one person performs both functions. A Junior Product Owner may support backlog management, requirements, and stakeholder communication. Job descriptions may also mention Product Owner Scrum experience when they are looking for someone to work in a Scrum team.

4. Product Strategy

Product strategy is the high-level plan for achieving a product’s goals. It usually defines the target customers, the problems the product solves, business objectives, competitive positioning, and the product’s direction.

A good product strategy connects customer needs with business goals.

5. Product Roadmap

A product roadmap is a high-level plan showing a product’s direction and priorities over time. It may include planned features, improvements, strategic initiatives, and major product goals.

A roadmap is not necessarily a fixed list of everything the team will build. Priorities can change as the team learns more about customers, the market, or the business.

6. Product Backlog

A product backlog is a prioritized list of work that may need to be completed for a product. It can include new features, improvements, technical work, bugs, research tasks, and other product activities.

The backlog is continuously updated as priorities change.

7. User Story

A user story describes a product requirement from the perspective of the person using the product.

Common format:

As a [type of user], I want [something], so that [benefit].

Example: “As a customer, I want to save my payment details so that I can check out faster.” User stories help teams understand what users need and why.

8. Product Discovery

Product discovery is the process of understanding customer problems and identifying which solutions are worth building. It can involve customer interviews, surveys, competitor research, data analysis, usability testing, and experiments.

The goal is to avoid spending time and resources on something customers do not need.

9. User Research

User research involves collecting information about users, their needs, behaviors, problems, and expectations. Product teams can use interviews, surveys, usability tests, observation, and product data to understand users better.

10. MVP

MVP stands for Minimum Viable Product. It is the simplest version of a product that can be released to test an idea and learn from real users.

An MVP should provide enough value to generate useful feedback. It does not mean building a low-quality product. The goal is to avoid building more than is necessary before validating the concept.

11. Product-Market Fit

Product-market fit (PMF) means that a product meets a real market need and customers see enough value in it to use, buy, or recommend it.

There is no single universal metric that proves product-market fit. Teams may look at demand, retention, usage, revenue, customer feedback, and other indicators.

12. Feature

A feature is a specific product function or capability. In a mobile banking app, features might include money transfers, bill payments, transaction notifications, or biometric login.

Product Managers evaluate which features to build or improve based on customer needs and business priorities.

13. Feature Request

A feature request is a suggestion from a customer, user, employee, or stakeholder for a new feature or improvement.

Product teams collect feature requests and evaluate them against other priorities rather than automatically building every requested feature.

14. Product Requirements

Product requirements describe what a product or feature needs to do. They can include functionality, user needs, business rules, technical requirements, and expected outcomes.

Clear requirements help Product, Design, and Engineering teams understand what needs to be built.

15. Prioritization

Prioritization is the process of deciding which product initiatives, features, or problems to address first. Product Managers may consider customer impact, business value, effort, urgency, risk, and strategic importance.

Popular prioritization frameworks include RICE, MoSCoW, and Impact vs. Effort.

16. RICE

RICE is a prioritization framework based on four factors:

• Reach: how many users will be affected;
• Impact: how much the initiative could help;
• Confidence: how confident the team is in its estimates;
• Effort: how much work is required.

RICE helps Product teams compare initiatives in a more structured way.

17. MoSCoW

MoSCoW divides requirements into four categories:

• Must have: essential;
• Should have: important but not essential;
• Could have: useful but lower priority;
• Won’t have: not planned for the current scope.

18. Agile

Agile is an approach to product and software development that emphasizes iterative work, customer feedback, collaboration, and adapting to change.

Instead of planning everything upfront, Agile teams work in smaller cycles and improve the product based on new information.

19. Scrum

Scrum is an Agile framework commonly used by Product and software development teams. Scrum teams work in short development cycles called sprints and use regular meetings to plan work, review progress, and identify improvements.

Common Scrum terms include Sprint, Product Backlog, Sprint Planning, Daily Scrum, Sprint Review, and Retrospective.

20. Sprint

A sprint is a fixed period during which a Scrum team works on selected tasks or a product goal. It commonly lasts one to four weeks, depending on the team’s setup.

At the end of a sprint, the team reviews what was completed and discusses what could be improved.

21. Stakeholder

A stakeholder is a person or group with an interest in a product, project, or business decision. Stakeholders may include company leadership, customers, Sales, Marketing, Customer Success, Engineering, Finance, and other internal teams.

Product Managers often need to balance different stakeholder needs and expectations.

22. Product Analytics

Product analytics uses product usage data to understand how users interact with a product. Teams may analyze activation, engagement, retention, feature adoption, and conversion.

Tools such as Amplitude, Mixpanel, and Google Analytics may be used for product analytics.

23. Activation

Activation is the point at which a new user experiences the key value of a product. The definition depends on the product. For a project management tool, activation might mean creating a first project and inviting another team member.

24. Retention

Retention measures how many users continue using a product over time. For example, a team may measure how many users who signed up in January are still active after 30, 60, or 90 days.

High retention can indicate that a product provides ongoing value.

25. User Engagement

User engagement describes how actively users interact with a product. It can be measured through frequency of use, number of sessions, feature usage, or specific actions completed by users.

26. Product Metrics

Product metrics are measurements used to understand product performance and user behavior. Common examples include:

• activation rate;
• conversion rate;
• retention rate;
• churn rate;
• Daily Active Users (DAU);
• Monthly Active Users (MAU);
• feature adoption;
• session frequency;
• Customer Lifetime Value (LTV).

The most important metrics depend on the product and its business model.

27. DAU and MAU

DAU (Daily Active Users) is the number of active users on a product or platform on a given day. MAU (Monthly Active Users) is the number of active users during a given month.

These metrics are commonly used to measure activity and engagement in digital products and platforms.

28. Product Experiment

A product experiment is a controlled test used to learn how a change might affect users or business outcomes. Experiments can test new features, pricing, onboarding flows, user interfaces, or other product changes.

A/B testing is one common type of product experiment.

29. User Feedback

User feedback is information provided by customers or users about their experience with a product. It can come from interviews, surveys, support tickets, reviews, Sales teams, social media, or in-product feedback.

Product teams use feedback to identify problems, validate ideas, and improve the product.

30. Product Launch

A product launch is the process of introducing a new product, feature, or major update to users or the market. It can involve Product, Engineering, Marketing, Sales, Customer Success, and other teams.

Launch work may include testing, communication, documentation, training, and monitoring results after release.

Why Product Management Vocabulary Matters

Knowing basic Product Management terminology makes it easier to understand job descriptions, prepare for interviews, and communicate with Product, Engineering, Design, Marketing, and other teams.

You do not need to know every framework or methodology to start a career in Product. Understanding the most common terms can make job descriptions and interviews much easier to navigate. Roles such as Junior Product Manager or Junior Product Owner can provide an opportunity to build experience and learn how different Product teams operate.

Looking for your next role in Product? Explore the latest Product Manager, Product Owner, Product Analyst, Product Operations, and other business roles on our job board.

Product Management FAQ

What is Product Management?

Product Management is the work of deciding what a product should achieve, who it serves, and how it should evolve. Product Managers connect customer needs with business goals and coordinate with teams such as Engineering, Design, Marketing, and Sales.

What does a Product Manager do?

A Product Manager helps set product direction, understand customer problems, prioritize work, shape the roadmap, and measure results. The exact responsibilities vary by company and team.

What is the difference between a Product Manager and a Product Owner?

A Product Manager often focuses on product direction, customer needs, and business goals. A Product Owner, commonly part of a Scrum team, typically manages and prioritizes the product backlog. Some companies separate the roles; others combine them.

What is a product roadmap?

A product roadmap is a high-level view of a product’s goals, priorities, and planned initiatives over time. It can change as the team learns more about customers, the market, or business needs.

What is a product backlog?

A product backlog is a prioritized list of work the team may do, such as features, improvements, bugs, technical tasks, and research. The team updates it as priorities change.

What is an MVP in Product Management?

MVP stands for Minimum Viable Product. It is an early version of a product or feature that delivers enough value to test an idea and learn from users. An MVP is designed to support learning, not to excuse poor quality.

What is product discovery?

Product discovery helps teams understand customer problems and decide which solutions are worth building. It may involve interviews, surveys, usability tests, product data, and experiments.

What is product-market fit?

Product-market fit means a product meets a real market need and customers find enough value in it to use, buy, or recommend it. Teams may assess it using indicators such as retention, demand, usage, revenue, and customer feedback.

What Product Management terms should beginners know?

Useful terms to start with include product strategy, roadmap, backlog, user story, MVP, product discovery, prioritization, Agile, Scrum, and product-market fit. Knowing these terms can help you understand job descriptions and prepare for Product interviews.

Explore current Product Management jobs, including Product Manager, Product Owner, Product Analyst, and Product Operations roles.