Ask ten product leaders to define the PM role and you'll get ten different answers. The ambiguity creates real problems: unclear expectations, misaligned incentives, and constant role confusion with engineering and design partners.
Clear PM roles are essential to an effective product operating model. This article offers a clear framework for defining the PM mandate—what product managers should own, what they should influence, and how to measure their success. We draw heavily on Shreyas Doshi's work on PM role clarity.
Why PM Role Clarity Matters
The product manager role is notoriously hard to define. Unlike engineers who write code or designers who create interfaces, PMs don't produce a tangible artifact. Their work is in the gaps—connecting people, synthesizing information, and driving decisions.
- PMs and engineers clash over who decides what gets built
- Design and product compete for customer insight ownership
- Leadership can't evaluate PM performance because expectations are unclear
- New PMs flounder without a clear definition of success
- The role expands to include everything (and therefore nothing)
The Three Lenses of PM Work
Shreyas Doshi offers a helpful lens: PMs operate in three modes, and clarity comes from understanding which mode applies when.
1. The Strategist
- Strategist Mode
- The PM focuses on what to build and why: understanding customer problems, connecting work to business strategy, making prioritization decisions, and managing vision and roadmap.
The strategist asks: "Are we solving the right problems for the right customers in the right order?"
2. The Executor
- Executor Mode
- The PM focuses on getting things done: writing clear requirements, managing stakeholder communication, removing blockers, coordinating launches, and ensuring quality.
The executor asks: "Is the team unblocked and moving toward our goals?"
3. The Leader
- Leader Mode
- The PM focuses on enabling others: building shared understanding, creating alignment, coaching team members, fostering healthy dynamics, and representing the team.
The leader asks: "Is the team set up for sustained success?"
The Right Balance
- Early-stage products: Need more strategist
- Complex organizations: Need more executor
- Growing teams: Need more leader
The danger is getting stuck in one mode. PMs who only strategize become disconnected from reality. PMs who only execute become glorified project managers. PMs who only lead without substance lose credibility.
What PMs Own vs. Influence
Role clarity requires distinguishing between what PMs own (are accountable for) versus what they influence (contribute to but don't decide).
- Problem definition: Articulating what problem we're solving and for whom
- Success criteria: Defining how we'll know if we succeeded
- Prioritization: Deciding what to build in what order
- Roadmap: Communicating the plan and rationale
- Stakeholder management: Keeping the right people informed and aligned
- Launch readiness: Ensuring everything is in place for successful release
- Solution design: Collaborate with design and engineering
- Technical approach: Input into feasibility and tradeoffs
- User experience: Partner with design on interactions
- Team health: Contribute but don't own (typically engineering management)
- Go-to-market: Partner with marketing and sales
- How to build: Engineering owns technical implementation
- Visual design: Designers own aesthetics and interaction patterns
- People management: Unless explicitly a people manager role
- Sales execution: Sales owns closing deals
These boundaries aren't walls—healthy overlap and collaboration is essential. But clarity on defaults prevents turf wars and enables clear decision rights.
The PM Accountability Question
If you can't answer this clearly, you have a role definition problem. The answer varies by organization, but commonly includes:
- Product outcomes: Did the product achieve its intended business results?
- Customer value: Did we solve real problems for real customers?
- Strategic alignment: Does what we built connect to company strategy?
- Opportunity cost: Did we work on the most important things?
Notice these are outcomes, not activities. PMs aren't accountable for writing PRDs—they're accountable for whether the product succeeds.
Common Anti-Patterns
PM as backlog manager—taking requests, writing tickets, prioritizing by loudest voice. No strategic thinking, no customer discovery, no outcome ownership.
Fix: Shift focus from output to outcomes. Require PMs to articulate why something matters before adding it to the backlog.
PM as final decision-maker on everything—overruling engineering on technical choices, design on UX, and generally acting without accountability.
Fix: Clarify decision rights. PMs decide prioritization; engineers decide implementation; designers decide experience.
PM as passive coordinator—scheduling meetings, sending status updates, but never making a substantive decision or taking a real position.
Fix: Require PMs to have a point of view. Push them to make recommendations, take positions, and be willing to be wrong.
Measuring PM Success
If PMs are accountable for outcomes, measure them on outcomes:
- Product outcomes: Did key metrics improve? Did features achieve their goals?
- Team effectiveness: Is the team focused, aligned, and unblocked?
- Strategic contribution: Is the PM making the organization smarter about product?
- Stakeholder trust: Do stakeholders trust the PM's judgment and communication?
Defining Your PM Mandate
Role clarity is a foundation for effective product work. Without it, every collaboration becomes a negotiation, every decision a potential conflict.
To define your PM mandate:
- Articulate what PMs are uniquely accountable for
- Clarify the boundaries with engineering and design
- Define success in terms of outcomes, not activities
- Document it and revisit it as the organization evolves
For more on building strong product teams, explore our guide on Building Product Capability, our framework for Decision Rights, or learn how we help companies clarify PM responsibilities.