Product Management: Foundations to Practice · Foundations of Product Management
What Does a Product Manager Actually Do?
Product management is one of the most misunderstood roles in tech, partly because the job looks different at every company and partly because its most valuable work is invisible. This chapter breaks down what a PM actually does, why the popular framing of the role is often wrong, and how the job changes with company size.
You will hear this phrase constantly in product culture, and it causes real damage if taken literally. A CEO has budget authority, hiring authority, and the power to fire people who do not execute. A product manager has none of that. What a PM actually has is information: the clearest cross-functional view of the customer, the data, and the business context available on the team. The job is to use that information to make the case for a direction, not to dictate one. PMs who act as though they hold CEO-level authority over engineers and designers burn trust quickly. The PMs who succeed treat every major decision as something they must earn buy-in for, repeatedly, through evidence and clear reasoning rather than title [1].
- A PM leads through influence and evidence, not formal authority; treating the role as having CEO-level power damages trust.
- Good product decisions sit inside the overlap of feasible, usable, and viable; most bad decisions optimize one at the expense of the others.
- The hardest, most valuable PM work (discovery, prioritization, alignment) is largely invisible; specs and backlog grooming are necessary but not differentiating.
- The day-to-day of the role looks meaningfully different at a startup, a mid-size company, and a large tech company.