What product managers actually do

A product manager (PM) is responsible for what gets built and why, so the team delivers outcomes that matter to users and the business. PMs don't usually manage people; they lead through clarity, evidence and trust.

The PM's core responsibilities

• Discover: understand users, their problems and the market; find the most valuable problems to solve.
• Decide: set strategy and priorities; say no to most ideas.
• Define: turn problems into clear requirements with the team (PRDs, user stories, success metrics).
• Deliver: work with engineering and design through build and launch; unblock, make trade-offs.
• Measure and iterate: check whether the outcome happened, learn, adjust.

Outputs vs outcomes

An output is a shipped feature; an outcome is a change in user behaviour or business results ("job seekers who complete a profile get 2× more interview invites"). Great PMs are judged on outcomes.

The three overlaps

Product sits at the overlap of users (desirable), business (viable) and technology (feasible). Good PMs also consider ethics (is this right for users?) and usability.

Types of PM roles

Consumer (B2C) apps, B2B SaaS, platform/API products, growth PMs (acquisition, activation, retention, monetisation), technical PMs (infrastructure, developer tools), AI product managers. APM (associate PM) programmes are the common entry route for freshers; product analyst, business analyst, engineering, design and consulting are common lateral routes.

Check yourself

• Give an example of an output and the outcome it should drive for a food delivery app.
• Why do PMs need to say no?