What Is Product Management?
ReShelf is a phone app where college students buy and sell used textbooks with classmates on their own campus. Its three engineers could build twenty different things next month: chat, a price guide, book rentals, a dark mode. Someone has to decide which problem is worth solving first, and be able to explain why. That person is the product manager.
The rule
The PM owns the why and the what; the team owns the how.
- Why: which problem matters, for whom, and what evidence says so. "First-years can't tell whether a listed book is the edition their course uses. A third of last semester's complaints were about wrong editions."
- What: the change that should solve it, how big the first version is, and what success looks like. "Tag every listing with a course code and edition. Success means wrong-edition complaints halve."
- How: the design and the code. Tanvi, the designer, decides how the tag looks; Arjun, the engineering lead, decides how the data is stored. The PM joins those conversations but does not overrule the experts.
A good PM checks every idea through three lenses at once:
| Lens | Question | ReShelf example |
|---|---|---|
| Valuable | Will users want it? | Do buyers really care about editions? |
| Viable | Does it work for the business? | Can listing stay free for sellers? |
| Feasible | Can the team build it? | Can we get each course's book list? |
The PM is judged on outcomes, such as students saving money or more books changing hands, not on output, such as the number of features shipped. A PM who ships ten features nobody uses has been busy, not successful.
The shortcut
When a request lands on your desk, sort it into why, what and how before reacting. The missing bucket tells you what to find out, and the bucket itself tells you who decides.
The request arrives
Kabir, the founder, says: "Buyers and sellers need to talk. Add chat by Friday." That is a how, delivered as an order.
The trap runs both ways. A PM who dictates the database design is doing someone else's job, and a PM who builds whatever the loudest person asks for is not doing their own.
Drills
Answer fast — trust the rule.
Which of these is ReShelf's PM's call to make?
Which number best shows whether ReShelf's PM is succeeding?
An idea is valuable and feasible, but ReShelf would lose money on every sale it handles. Which lens does it fail?
Kabir says, "Build a price-guide page by next week." What is the PM's best first move?
Remember
- The PM owns the why and the what; designers and engineers own the how.
- Sort every request into why, what and how, and check it against value, viability and feasibility.
- Trap: measuring yourself by features shipped instead of outcomes for users.