What is product management and what does a product manager do?

Question

Accepted Answer

**Product management** is the discipline of deciding *what* to build and *why*, so the team ships things that are valuable to users and good for the business. A **product manager (PM)** owns the product's direction, not the code. The classic shorthand: a PM sits at the intersection of **business, technology, and user experience**.

## What a PM actually does

```text
✓ DISCOVERY → talk to users, study data, find real problems worth solving
✓ PRIORITIZATION → decide what matters most right now (and what to skip)
✓ DEFINITION → write down what we're building and the success criteria
✓ COORDINATION → align engineering, design, marketing, sales around a plan
✓ MEASUREMENT → track whether the released work moved the needle
```

## A concrete example

Users keep abandoning signup. The PM digs into the funnel data, interviews a few drop-offs, and finds the email-verification step is the culprit. Rather than ordering "remove verification," the PM frames the problem, weighs it against other work, and brings a proposal to engineering and design.

## A common misconception

A PM is **not** the "boss" of engineers and is usually not a people manager. PMs lead through influence and clarity, not authority. You succeed by making the right thing obvious, not by giving orders.

## Why it matters

Building the wrong thing well is still waste.

Product management exists to reduce that risk by grounding decisions in user needs and business value.

For a junior engineer, understanding the PM role makes you a better collaborator: you'll ask *why* a feature matters and push back when the goal is unclear.