Product management

Business basics2min read

Product management is the work of deciding which customer problems a product should solve, setting priorities, and checking whether the changes create value for customers and the business. It covers both new products and improvements to existing ones.

How product management works

Product managers combine customer research, usage data and business goals to choose what to build, defer or stop. They work with designers and engineers rather than simply handing over feature requests.

A product requirements document (PRD) records the problem, intended outcome, scope and success measure. A roadmap communicates priorities, but it should change when evidence changes.

At an early startup, a founder often does this work before hiring a product manager. The goal is evidence of demand, not a longer feature list.

Improving checkout instead of adding a wishlist

In this illustrative example, an online store has 10,000 checkout starts per month and a $50 average order value. Research points to surprise delivery charges as a reason shoppers leave. The team tests showing those charges earlier instead of building a wishlist.

Here is the monthly impact if checkout completion rises from 40% to 44%, with traffic and order value unchanged:

MetricBeforeAfter
Checkout starts10,00010,000
Completion rate40%44%
Completed orders4,0004,400
Revenue$200,000$220,000

Extra revenue = 10,000 × (44% − 40%) × $50 = $20,000 per month, before costs.

Product management connects the customer problem to that outcome. Shipping the change is not enough: the team must check whether it actually improves completion.

Questions people ask

What exactly is the role of a product manager?

A product manager coordinates problem selection, priorities and outcome measurement. They help the team decide what to build and why. Project management focuses more on coordinating delivery against scope, time and budget.

What are the 7 stages of product management?

There is no universal seven-stage standard. Different frameworks divide the work differently. Most cover understanding customers, choosing problems, testing solutions, building, launching and measuring results. Teams revisit earlier decisions rather than following a fixed sequence once.

Related terms