Role Expectations Template

What This Template Is For

Most product managers cannot clearly articulate what their manager expects of them. This is not because they are unaware or disengaged. It is because the expectations were never written down. The PM role is notoriously ambiguous: it varies by company, team, product stage, and organizational culture. Without explicit expectations, PMs operate on assumptions, and those assumptions diverge from their manager's assumptions until the gap surfaces in a performance review.

This template helps product leaders define clear, level-specific expectations for PM roles. Each role definition covers what the PM is responsible for, what competency level is expected, what deliverables they own, and how success is measured. It is the foundation for hiring (you need to know what you are hiring for), performance reviews (you need a baseline to evaluate against), and career development (PMs need to know what the next level looks like).

Use this template to build expectations for each PM level in your organization. For the complementary assessment tool, the PM performance review template provides the evaluation framework. The PM career path finder helps PMs understand career trajectories across levels and specializations. For compensation benchmarks by level, the PM salary guide covers market rates.

How to Use This Template

1. Identify the PM levels in your organization (e.g., APM, PM, Senior PM, Staff PM, Group PM, Director, VP).
2. For each level, fill out the Role Expectations Canvas below. Start with the level you hire for most frequently.
3. Differentiate between levels by specifying how scope, autonomy, impact, and influence change at each level.
4. Share draft expectations with current PMs at each level for feedback. Their input catches blind spots in what the role actually requires versus what leadership imagines it requires.
5. Publish the expectations in a shared location (wiki, Notion, team handbook).
6. Reference the expectations in hiring, onboarding, 1:1 meetings, and performance reviews.

The Template

Role Expectations Canvas

Fill out one canvas per PM level.

Scope

Responsibilities

Core responsibilities (expected every week/sprint):

• ☐ [Responsibility 1, e.g., "Own the product backlog and keep it groomed with refined, estimated tickets"]
• ☐ [Responsibility 2, e.g., "Facilitate sprint planning and ensure the team commits to achievable scope"]
• ☐ [Responsibility 3, e.g., "Communicate sprint progress and risks to stakeholders via weekly async update"]
• ☐ [Responsibility 4, e.g., "Make scope and priority decisions within the committed roadmap"]
• ☐ [Responsibility 5, e.g., "Partner with design on UX direction for in-progress features"]

Strategic responsibilities (expected every quarter):

• ☐ [Responsibility 1, e.g., "Develop and present the quarterly roadmap with clear rationale"]
• ☐ [Responsibility 2, e.g., "Conduct user research or customer interviews (minimum 5 per quarter)"]
• ☐ [Responsibility 3, e.g., "Define and monitor OKRs for the product area"]
• ☐ [Responsibility 4, e.g., "Identify and evaluate competitive threats or market opportunities"]

Organizational responsibilities (expected ongoing):

• ☐ [Responsibility 1, e.g., "Mentor 1-2 junior PMs or APMs"]
• ☐ [Responsibility 2, e.g., "Contribute to PM hiring (interview 2+ candidates per quarter)"]
• ☐ [Responsibility 3, e.g., "Improve PM team processes or documentation"]

Competency Expectations

Rate the expected competency level for this role. This calibrates what "meets expectations" looks like at this level.

Competency level definitions:

Key Deliverables

Success Criteria

How do we know this PM is succeeding at this level?

Outcome metrics (lagging):

• ☐ [e.g., "Primary product metric is trending in the right direction"]
• ☐ [e.g., "Sprint commitment accuracy > 80%"]
• ☐ [e.g., "Quarterly OKRs achieved at 70%+ (stretch target calibration)"]

Process metrics (leading):

• ☐ [e.g., "PRDs are reviewed and approved before engineering starts work"]
• ☐ [e.g., "Stakeholder updates are sent weekly without being prompted"]
• ☐ [e.g., "Customer interviews conducted at the expected cadence"]

Peer signals (qualitative):

• ☐ [e.g., "Engineers describe this PM as organized and decisive"]
• ☐ [e.g., "Designers describe this PM as open to iteration and collaborative"]
• ☐ [e.g., "Stakeholders describe this PM as reliable and proactive"]

Anti-Patterns (What Failure Looks Like)

List the specific behaviors that indicate a PM is not meeting expectations at this level. These are more actionable than abstract success criteria because they describe observable behaviors.

• ☐ [Anti-pattern 1, e.g., "Tickets go into sprint planning without clear acceptance criteria"]
• ☐ [Anti-pattern 2, e.g., "Stakeholders learn about decisions after the fact rather than being consulted"]
• ☐ [Anti-pattern 3, e.g., "The PM cannot articulate why the current quarter's roadmap is the right set of priorities"]
• ☐ [Anti-pattern 4, e.g., "Engineers regularly ask clarifying questions that should have been answered in the PRD"]
• ☐ [Anti-pattern 5, e.g., "The PM defers all scope decisions to the engineering lead or VP"]

Level Differentiation Guide

Use this table to map how expectations change across levels. Each column represents a PM level in your org.

Filled Example: Senior PM Role Expectations

Role Overview

Scope

Responsibilities

Core (weekly):

• ☑ Own the Growth Squad backlog: groomed, estimated, prioritized
• ☑ Facilitate sprint planning and hold the team accountable for commitments
• ☑ Send weekly async update to stakeholders: shipped, in progress, risks, metrics
• ☑ Make scope and priority decisions. Do not defer to the VP for decisions within your authority
• ☑ Partner with the designer on UX direction. Review designs before handoff to engineering

Strategic (quarterly):

• ☑ Develop the quarterly roadmap using RICE scoring and present to VP Product with rationale
• ☑ Conduct 8+ customer interviews per quarter. Synthesize findings into actionable insights
• ☑ Define and monitor Growth Squad OKRs. Flag off-track OKRs by week 6 with a recovery plan
• ☑ Evaluate competitive landscape quarterly. Present 1-2 competitive insights per quarter

Organizational (ongoing):

• ☑ Mentor 1 APM. Meet weekly, review their PRDs, include them in customer interviews
• ☑ Interview PM candidates (2+ per quarter). Serve as the "product sense" interviewer using the PM interview template
• ☑ Contribute to PM team processes: document one process improvement per quarter

Competency Expectations

Anti-Patterns

• ☐ Regularly defers roadmap decisions to VP Product instead of making a recommendation
• ☐ PRDs are written after engineering has started (not before)
• ☐ Customer interviews are skipped or delegated entirely to UX research
• ☐ Stakeholders are surprised by scope changes or delays
• ☐ The Growth Squad's metrics are not monitored between monthly reviews
• ☐ Junior PM mentoring is passive (available for questions but does not proactively coach)

Common Mistakes to Avoid

• Writing job descriptions instead of expectations. Job descriptions list requirements for hiring. Role expectations define what success looks like for someone already in the role. They overlap, but expectations are more specific about deliverables, cadence, and quality standards.
• Making every level sound the same with more adjectives. "Owns a product area" vs. "Owns a large product area" vs. "Owns a critical product area" is lazy differentiation. Differentiate by scope (breadth of ownership), autonomy (what they can decide alone), and influence (who they influence).
• Not defining anti-patterns. Positive expectations tell PMs what to aim for. Anti-patterns tell them what failure looks like. Anti-patterns are more useful in practice because they describe observable behaviors that are easier to catch and coach on than abstract competencies.
• Writing expectations alone. If the Director of Product writes all expectations without input from current PMs, the expectations will reflect what the director imagines the role is, not what it actually requires. Get input from people currently in the role.
• Not updating for company stage. A Senior PM at a 20-person startup has a different scope than a Senior PM at a 2,000-person enterprise company. Update expectations when the company stage shifts meaningfully (post-fundraise, post-IPO, post-acquisition). The Product Operations Handbook covers how PM roles evolve as organizations scale.

Key Takeaways

• Role expectations should be explicit, written, and shared. Implicit expectations create misalignment that only surfaces during performance reviews
• Differentiate levels by scope, autonomy, and influence, not by adjective intensity
• Include anti-patterns (observable failure behaviors) alongside positive expectations
• Get input from PMs currently in the role. Manager-only expectations often miss what the job actually requires
• Review and update expectations annually or when the organization changes significantly

About This Template

Created by: Tim Adair

Last Updated: 3/5/2026

Version: 1.0.0

License: Free for personal and commercial use