What This Template Is For
Product teams operate at the intersection of strategy, design, engineering, and business. The range of skills required is wide, and no individual PM covers all of them equally. A capability assessment maps your team's actual skills against the skills your product and organization need, revealing gaps that affect execution and growth opportunities that affect retention.
This is not a performance review. Performance reviews evaluate past results. A capability assessment evaluates current skill levels to inform hiring, training, mentoring, and project assignment decisions. A PM who delivered strong results last quarter might still have a significant gap in data analysis that limits their effectiveness on the next project. The assessment catches that.
This template provides a structured framework for evaluating product team members across six skill dimensions: product strategy, execution and delivery, analytics and measurement, technical depth, stakeholder management, and leadership. Each dimension includes specific skills rated on a 1-5 scale with clear definitions. For individual career path exploration, see the Career Path Finder. For a broader view of PM competencies across levels, the PM career ladder glossary entry outlines the typical progression from APM to CPO.
When to Use This Template
- During quarterly or semi-annual team planning. Assess your team's capabilities before setting goals for the next period. Align development plans with the skills the roadmap will require.
- When hiring for a new role. Before writing a job description, map your team's existing capabilities. The new hire should fill gaps, not duplicate strengths. Use the PM job description template once you have identified the specific gap.
- When restructuring teams or projects. If you are reorganizing product teams around new domains, assess capabilities to assign people to roles where they will be most effective and where they have room to grow.
- During one-on-one conversations about career development. The assessment gives both the manager and the PM a shared vocabulary for discussing strengths, growth areas, and career goals. Pair it with your one-on-one template for structured career conversations.
- When a team is underperforming. Before assuming the problem is motivation or process, check whether the team has the skills required for the work. A team tasked with building an ML-powered feature without anyone who understands ML will struggle regardless of how good their sprint process is.
- When building a training or mentoring program. Aggregate individual assessments to find common gaps across the team. These gaps become the curriculum for team-wide learning investments.
How to Use This Template
- The manager completes an initial assessment for each team member. Rate each skill based on observed behavior and output, not potential or tenure. A PM with 8 years of experience who has never run an A/B test scores a 2 on experimentation, not a 4 because "they could probably figure it out."
- The team member completes a self-assessment. Use the same template and scoring scale. Self-assessments reveal blind spots in both directions: people who overestimate their skills and people who underestimate them.
- Compare and discuss. The most valuable part of the process is the calibration conversation. Where the manager and the team member disagree by 2+ points, dig into why. This conversation often surfaces misaligned expectations or invisible contributions.
- Identify 2-3 priority growth areas. Do not try to improve everything at once. Pick the 2-3 skills that are most important for the team member's current role and upcoming projects.
- Create specific development actions. "Get better at analytics" is not actionable. "Complete an SQL course by March, shadow the data team for 2 sprint retrospectives, and own the activation funnel analysis for Q2" is actionable.
- Re-assess every 6 months. Skills change. Projects change. Review and update the assessment to track growth and adjust development plans.
The Template
Assessment Metadata
Assessment Date. [YYYY-MM-DD]
Team Member. [Name, Current Role/Level]
Assessed By. [Name, Role]
Assessment Type. [Manager / Self / Peer / 360]
Product Area. [Team or product domain]
Scoring Scale
| Score | Label | Definition |
|---|---|---|
| 1 | Novice | Has heard of the concept but has no practical experience. Needs hands-on guidance to apply it. |
| 2 | Developing | Has applied the skill in limited contexts with significant support. Can execute with detailed instructions. |
| 3 | Competent | Independently applies the skill in standard situations. Produces reliable work without oversight. |
| 4 | Advanced | Applies the skill in complex or ambiguous situations. Coaches others. Adapts approach based on context. |
| 5 | Expert | Recognized as a go-to resource. Shapes the team's approach. Can teach, mentor, and define best practices. |
Dimension 1: Product Strategy
| Skill | Score (1-5) | Evidence / Examples | Growth Priority (Y/N) |
|---|---|---|---|
| Defining product vision and positioning | |||
| Market and competitive analysis | |||
| Customer segmentation and targeting | |||
| Business model understanding (revenue, unit economics) | |||
| Strategic planning (annual / multi-quarter) | |||
| Opportunity sizing and TAM analysis | |||
| Pricing strategy | |||
| Dimension Average |
Dimension 2: Execution and Delivery
| Skill | Score (1-5) | Evidence / Examples | Growth Priority (Y/N) |
|---|---|---|---|
| Writing clear requirements (PRDs, specs, user stories) | |||
| Prioritization and backlog management | |||
| Sprint planning and velocity management | |||
| Cross-functional coordination (design, eng, QA) | |||
| Scope management and tradeoff decisions | |||
| Release planning and launch execution | |||
| Quality assurance and attention to detail | |||
| Dimension Average |
Dimension 3: Analytics and Measurement
| Skill | Score (1-5) | Evidence / Examples | Growth Priority (Y/N) |
|---|---|---|---|
| Defining success metrics and KPIs | |||
| SQL and data querying | |||
| A/B testing and experimentation design | |||
| Funnel analysis and cohort analysis | |||
| Interpreting statistical significance | |||
| Dashboard design and data storytelling | |||
| User research and qualitative analysis | |||
| Dimension Average |
Dimension 4: Technical Depth
| Skill | Score (1-5) | Evidence / Examples | Growth Priority (Y/N) |
|---|---|---|---|
| Understanding system architecture and APIs | |||
| Evaluating technical tradeoffs with engineering | |||
| Reading and understanding code (not writing production code) | |||
| Data modeling and database concepts | |||
| Infrastructure and scalability awareness | |||
| Security and compliance fundamentals | |||
| AI / ML concepts (if applicable to domain) | |||
| Dimension Average |
Dimension 5: Stakeholder Management
| Skill | Score (1-5) | Evidence / Examples | Growth Priority (Y/N) |
|---|---|---|---|
| Executive communication (written and verbal) | |||
| Managing up (proactive updates, expectation setting) | |||
| Cross-functional influence without authority | |||
| Conflict resolution and negotiation | |||
| Customer-facing communication | |||
| Building alignment across competing interests | |||
| Presenting data and recommendations persuasively | |||
| Dimension Average |
Dimension 6: Leadership
| Skill | Score (1-5) | Evidence / Examples | Growth Priority (Y/N) |
|---|---|---|---|
| Mentoring and developing junior team members | |||
| Decision-making under uncertainty | |||
| Taking ownership and accountability | |||
| Building team culture and psychological safety | |||
| Hiring (sourcing, interviewing, evaluating candidates) | |||
| Strategic thinking beyond the current product | |||
| Adaptability when plans change | |||
| Dimension Average |
Capability Summary
| Dimension | Manager Score | Self Score | Gap | Priority |
|---|---|---|---|---|
| Product Strategy | ||||
| Execution & Delivery | ||||
| Analytics & Measurement | ||||
| Technical Depth | ||||
| Stakeholder Management | ||||
| Leadership | ||||
| Overall Average |
Development Plan
Top 3 Growth Priorities.
| # | Skill | Current Level | Target Level | Development Actions | Timeline | Support Needed |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Strengths to Amplify.
[List 2-3 skills where this person is at 4 or 5. How can they use these strengths to add more value? Can they mentor others, lead initiatives, or take on stretch projects that build on existing strengths?]
Next Assessment Date. [YYYY-MM-DD, typically 6 months out]
Filled Example: Mid-Level Product Manager
Context. A Director of Product at a Series C fintech company assessed a PM with 4 years of experience who manages the payments product. The PM is strong in execution but wants to move into a Senior PM role, which requires stronger strategic thinking and stakeholder management.
Capability Summary
| Dimension | Manager Score | Self Score | Gap | Priority |
|---|---|---|---|---|
| Product Strategy | 2.7 | 3.4 | -0.7 | High |
| Execution & Delivery | 4.1 | 3.9 | +0.2 | Low |
| Analytics & Measurement | 3.3 | 2.9 | +0.4 | Medium |
| Technical Depth | 3.9 | 4.1 | -0.2 | Low |
| Stakeholder Management | 2.9 | 3.1 | -0.2 | High |
| Leadership | 2.4 | 2.6 | -0.2 | Medium |
| Overall Average | 3.2 | 3.3 |
Development Plan
| # | Skill | Current | Target | Actions | Timeline | Support |
|---|---|---|---|---|---|---|
| 1 | Strategic planning | 2 | 4 | Lead Q3 strategy doc for payments; attend monthly strategy review with VP | 6 months | VP Product to review drafts and provide feedback |
| 2 | Executive communication | 3 | 4 | Present at 2 business reviews; take a storytelling workshop; write 3 monthly stakeholder updates | 6 months | Director to co-present at first review |
| 3 | A/B testing | 2 | 3 | Design and run 2 experiments on the checkout funnel; pair with data scientist on statistical analysis | 4 months | Data team to provide analysis support |
Key Takeaways
- Assess skills, not effort or intent. A PM who works 60-hour weeks but cannot write a clear PRD has a skill gap, not a motivation problem. The assessment should identify what to develop, not judge how hard someone is trying.
- The calibration conversation matters more than the scores. The numbers are a starting tool. The real value is in the discussion about why the manager scored a 2 where the PM scored a 4 on strategic planning. That conversation reveals misaligned expectations and invisible work. For frameworks on running productive career conversations, see the Stakeholder Management Handbook.
- Limit development priorities to 2-3 per period. Spreading effort across seven growth areas produces no meaningful improvement in any of them. Focus on the skills that will have the most impact in the next 6 months.
- Use project assignments as development tools. If a PM needs to improve their analytics skills, assign them a project that requires funnel analysis instead of sending them to a generic course. Learning by doing beats learning by watching. Use the RICE Calculator to score which development investments yield the highest return.
- Re-assess every 6 months. Growth happens slowly, and skipping assessments signals that the exercise was performative. Consistent reassessment shows the team that development is a real investment, not a one-time checkbox.
About This Template
Created by: Tim Adair
Last Updated: 3/5/2026
Version: 1.0.0
License: Free for personal and commercial use