What Does a Product Manager Actually Do?

The Role in a Nutshell

If you've ever wondered what product managers spend their time on, you're not alone. It's one of the most misunderstood roles in tech. Some people think PMs are mini-CEOs. Others assume they're glorified project managers. The reality is more nuanced—and more interesting.

The Core Responsibility

A product manager owns the what and why of a product. Engineering owns the how. Design owns the experience. But PMs are responsible for deciding what gets built, in what order, and for what reason.

This sounds simple until you realise it means:

• Talking to customers to understand their problems
• Analysing data to spot patterns and opportunities
• Working with stakeholders to align on priorities
• Writing specs that engineers can actually build from
• Making trade-off decisions when resources are limited
• Saying no to 90% of feature requests

The best one-liner I've heard: A PM is responsible for the success of their product, without having direct authority over anyone who builds it. That's both the challenge and the appeal.

A Day in the Life

There's no typical day, but here's what a week might look like at a mid-stage startup:

Monday: Sprint planning with engineering. Review last week's metrics. Customer call to discuss a workflow issue they're hitting.

Tuesday: Write a product brief for a new feature. Get feedback from design lead. Stakeholder meeting with sales about enterprise requests.

Wednesday: User research session—watching three customers use the product. Synthesis and notes. Quick prioritisation discussion with the CPO.

Thursday: Spec review with engineers. Answer Slack questions. Competitor analysis for an upcoming strategy meeting. 1:1 with engineering manager.

Friday: Roadmap update presentation to leadership. Sprint retrospective. Clear the backlog of smaller decisions.

Notice what's missing: actual building. PMs don't write code or push pixels. They create the conditions for others to do that well.

PM vs. Project Manager

This confusion never dies, so let's be direct:

Some companies have both roles. Others expect PMs to handle project management too. Neither is wrong—it depends on team size and complexity.

At Atlassian, dedicated project managers handle Jira workflows while product managers focus on strategy. At a 20-person startup, one person probably does both.

The Three Types of PM Work

Most PM work falls into three buckets:

1. Discovery — Figuring out what's worth building

This includes customer research, data analysis, competitive intelligence, and opportunity sizing. Discovery answers: "Should we invest in this problem?"

2. Definition — Specifying what to build

Writing PRDs, user stories, acceptance criteria, and wireframes. Working with design on flows. Answering engineer questions before and during development.

3. Delivery — Getting it shipped and measured

Unblocking the team, managing stakeholders, running launches, analysing results, and iterating based on feedback.

Junior PMs spend more time on definition and delivery. Senior PMs spend more time on discovery and strategy.

Skills That Actually Matter

Forget the generic lists. Here's what separates good PMs from great ones:

Communication — You'll write more than you expect. Specs, emails, Slack messages, presentations, roadmap updates. If you can't write clearly, everything else breaks.

Prioritisation — Everyone wants everything. Your job is to make defensible choices about what gets attention. Frameworks like RICE and ICE help, but judgement matters more.

Technical fluency — You don't need to code, but you need to understand systems well enough to have informed conversations. Know why the engineer says something is hard.

Customer empathy — This isn't a soft skill—it's a competitive advantage. PMs who genuinely understand user problems build better products.

Data literacy — Basic SQL, familiarity with analytics tools, comfort with metrics. You should be able to answer your own questions instead of waiting for data science.

Stakeholder management — Sales wants one thing. Marketing wants another. Legal has concerns. You need to navigate these without making enemies or caving to every request.

What PMs Don't Do (Despite Common Belief)

• Make all the decisions. Good PMs facilitate decisions and break ties—they don't dictate.
• Manage people. PMs have influence, not authority. You can't fire the engineer who disagrees with you.
• Know everything. Your job is to ask good questions and synthesise answers, not to have all the answers yourself.
• Own the design. Designers own the design. You're a partner, not a boss.
• Guarantee success. Even well-run products fail. That's the nature of building things.

How Companies Structure PM Roles

Different companies have different expectations:

Big Tech (Google, Meta, Amazon): PMs often work on narrow problem spaces with large teams. More specialisation, more process, bigger impact at scale.

Growth-stage startups (Stripe, Figma, Notion): PMs own broader areas with smaller teams. More autonomy, faster decisions, closer to customers.

Early-stage startups: PM might be the CEO or a co-founder. Or there's one PM doing everything across the whole product.

Enterprise software (Salesforce, SAP): PMs work closely with sales and customer success. More stakeholder management, longer release cycles.

Getting Into Product Management

Most PMs don't start as PMs. Common paths include:

• Engineering → PM: Understand the technical side, want more customer contact
• Design → PM: Good at user research, want more strategic influence
• Consulting → PM: Strong analytical skills, need to learn product intuition
• Operations → PM: Understand business problems, need technical exposure
• Customer success → PM: Deep customer knowledge, need to learn product development

The best way in? Build something. Ship a side project. Run a community. Create something people use. Nothing signals PM potential like actually shipping a product, even a small one.

What Makes a PM Successful

After working with hundreds of PMs, here's what separates the top performers:

1. Bias to action. They ship things rather than perfecting plans.
2. Strong opinions, loosely held. They have conviction but update based on evidence.
3. Relentless customer focus. They talk to users weekly, not quarterly.
4. Effective cross-functional relationships. Engineers and designers want to work with them.
5. Clear communication. Their specs are unambiguous. Their emails are concise. Their presentations are compelling.

Is Product Management Right for You?

You'll thrive as a PM if you:

• Like solving ambiguous problems
• Enjoy working across disciplines
• Get energy from customer conversations
• Can handle influence without authority
• Don't need to build things with your own hands

You might struggle if you:

• Want clear daily tasks and defined success
• Prefer working alone
• Get frustrated by politics and stakeholder management
• Need to see your direct handiwork in the final product

Final Thoughts

Product management is a craft, not a checklist. The job looks different at every company and changes as you grow. But the core remains constant: understand what's worth building and rally a team to build it well.

The best PMs I know are intensely curious, slightly impatient, and deeply pragmatic. They care more about outcomes than output. And they never stop talking to customers.

That's the job. It's messy, exhausting, and deeply satisfying when you get it right.