A product manager skills matrix maps the competencies a PM needs against career levels — from Associate PM to Product Lead — using behavioral anchors instead of vague 1-to-5 scores. Generic templates fail because they list skills without describing what each level actually looks like. Below is a filled-in matrix of 9 competencies, a BARS rating scale, and a free Excel/Sheets download.

We built this by synthesizing three of the most-referenced public frameworks — Ravi Mehta's Product Competency Toolkit (12 competencies across 4 areas), Markus Müller's skill matrix (26 skills across 4 experience levels), and the Product Compass PM Competence Map (built from 200+ interviews and validated against 1,428 assessment responses) — into one practical matrix you can adopt without a signup.

What a good PM skills matrix needs (and why generic templates fail)

Most templates you find are a wish-list of skills with a 1-to-5 column next to each one. They fail for a simple reason: a "3 in Strategy" means nothing without a description of what a 3 does that a 2 does not. When ratings are undefined, two managers score the same PM two levels apart, calibration collapses, and the matrix becomes political rather than developmental.

A good PM skills matrix has four properties:

The frameworks above disagree on the exact count — 12, 26, or 32 items — but they converge on the same underlying areas: execution, customer insight, strategy, and influence. We collapse that into 9 core competencies, which is granular enough to be useful and short enough that people actually fill it in.

The 9 core PM competencies

These are the competencies — the "core competencies by job family" that hiring and leveling conversations keep returning to. Each one earns its place because it separates levels in practice, not just on paper.

The filled-in matrix: Associate PM to Product Lead

This is the core asset — a filled-in matrix, not an empty shell. Read each row across the four levels to see how the same competency grows. Use it as your baseline and adjust the wording to your own ladder.

If you are running competency development at organization scale rather than for one squad, the same logic extends beyond product — see our guide to successful skill management for the org-wide version.

The rating scale: a 5-point BARS

Use a behaviorally anchored rating scale (BARS), not a naked 1-to-5. The difference: each number carries a behavior, so scores are defensible. Level 3 is the expected bar for the role — not the ceiling.

Building the template: Excel, Google Sheets, or Notion

The matrix above works in any tool. A practical build takes about 30 minutes:

1. Put the 9 competencies in column A and your four levels as a header row on a second tab — that is your reference matrix.
2. On the assessment tab, list PMs as rows, competencies as columns, and enter a 1–5 score per cell with conditional formatting (red-to-green).
3. Add a "target level" column per PM so the gap between current and target is visible at a glance.
4. Add a comments cell per competency for the evidence behind each score — this is what makes calibration possible.
5. Lock the reference tab so people rate against the same anchors every cycle.

Excel and Google Sheets are the right starting point. The moment you have more than about 15 people, multiple raters, and a need for history and permissions, a spreadsheet starts to fight you. That is the point to compare dedicated skill-management software, or to browse the skills and competency management category to see what running this at scale looks like.

DACH context: works council and GDPR

If you operate in Germany, Austria, or Switzerland, a competency matrix is not just an HR tool — it can be co-determined and it is almost always personal data. Two points no template we reviewed mentions:

Getting this right early saves a painful re-do later. For the wider DACH picture on data protection and works-council handling in HR tooling, our enterprise performance management guide covers how competency data feeds — and must not silently drive — performance reviews.

AI literacy as a PM competency

We add AI Literacy as the ninth competency deliberately. PMs now scope AI features, judge model output, and decide where automation is safe. Frame it as capability, not hype: can the PM reason about model limits, evaluation, and risk?

There is also a compliance angle. Under the EU AI Act, Article 4, providers and deployers of AI systems must ensure a sufficient level of AI literacy among staff who work with those systems. For product teams shipping AI features in the EU, "AI literacy" is moving from a nice-to-have to something you can be expected to demonstrate — a good reason to make it an explicit line in the matrix.

Where teams keep the matrix alive (or let it go stale)

The hardest part is not building the matrix — it is keeping it honest. From our work with HR and product teams in DACH, three failure patterns come up again and again:

One pattern that helps: capture skill evidence continuously — from shipped work, peer feedback, and project reviews — instead of reconstructing a year of memory in one annual sitting. Tooling like sprad can gather that evidence between review cycles so the matrix reflects reality rather than recency bias. The principle matters more than the tool: little and often beats a once-a-year fill-in.

Common mistakes with PM skills matrices

• Too many competencies. A 26-line matrix looks thorough and never gets filled in. Nine is a workable ceiling.
• Levels without anchors. "Advanced" is not a standard; a described behavior is.
• Using it as a weapon. A matrix designed for growth, then quietly repurposed for PIPs, loses all trust.
• One rater, no calibration. Single-manager scores are biased by definition — calibrate.
• No target levels. Without a target per person, the matrix diagnoses but never develops.

Frequently asked questions

What is a product manager skills matrix?

It is a grid that maps the core competencies a PM needs against career levels, with a behavioral description of what each competency looks like at each level. It is used for hiring, leveling, promotion, and development conversations.

Which competencies does a PM really need?

The public frameworks converge on four areas — execution, customer insight, strategy, and influence. We express them as 9 concrete competencies, including Data Fluency and AI Literacy, which increasingly separate strong PMs from the rest.

How does a Senior PM differ from a PM?

Scope and ambiguity. A PM owns an area and delivers it well; a Senior PM handles cross-team complexity, shapes strategy for a product line, and coaches other PMs. The matrix makes that difference explicit per competency rather than leaving it to a title.

Does the works council have to consent to a competency matrix?

In Germany, if the matrix sets principles for assessing employees or uses assessment questionnaires, it can require works-council consent under § 94 Abs. 2 BetrVG. Involve the Betriebsrat early and treat the scores as personal data under the GDPR and § 26 BDSG.

How often should the matrix be updated?

Review the framework itself once a year and re-score people each review cycle (typically twice a year). Better still, capture evidence continuously so each review reflects the whole period rather than the last few weeks.

Next step

Download the filled-in matrix, adapt the level names to your ladder, and run one calibration session before you attach it to anything high-stakes. Start developmental, keep an owner, and — if you are in DACH — loop in the works council before rollout.