Free Skill Matrix Template for Excel & Google Sheets | HR Gap Analysis Tool
Free Skill Matrix Template for Excel & Google Sheets | HR Gap Analysis Tool
A product management skills matrix is a table that maps PM core competencies against career levels — from Associate PM through PM and Senior PM to Product Lead — and fills every cell with a concrete behavioral anchor. Instead of vague ratings, it shows what good looks like at each level. This guide gives you a fully filled-in template, the DACH legal context, and an optional AI literacy row.
Here is what you will get:
- The 9 PM core competencies, mapped to established frameworks
- A filled-in matrix: 9 competencies × 4 levels with behavioral anchors
- A 5-point rating scale based on the BARS principle
- How to build the template in Excel, Google Sheets, or Notion
- The legal context for skill data: works council, GDPR, and the AI Act
When someone asks in the next promotion discussion what separates a Senior PM from a PM, and the answer stays vague, this is exactly the matrix that is missing. Let us fill it in.
Why a PM skills matrix cannot be generic
Product management has the broadest competency spread of any tech role. A PM sits at the intersection of user experience, engineering, business, and strategy. A generic skills matrix that fits every department therefore misses what matters most: what "stakeholder management" means for a PM is fundamentally different from the same label in sales.
The most widely used reference model comes from Ravi Mehta. His Product Competency Toolkit organizes 12 competencies into four themes: Product Execution, Customer Insight, Product Strategy, and Influencing People. Mehta's core observation: early PMs need execution as their foundation first, while for senior PMs strategy and influencing people become the critical path. That shift is the through-line of every good matrix.
A second guiding principle comes from practice: the T-shaped profile. In his PM skill matrix with 26 skills across four levels, Markus Müller describes a broad base across all competencies plus one or two specializations. That replaces the older image of the generalist PM. No one needs to be elite in all nine fields — but solid everywhere, and outstanding in two.
For the generic build process of a matrix — columns, tabs, rating logic — see our ultimate guide for successful skill management. Here we focus on what is unique to PMs: the concrete behavioral anchors per level.
The 9 PM core competencies
These nine competencies capture what ranking frameworks have in common. They condense Mehta's 12 competencies, the eight areas of Paweł Huryn's PM competency map (based on interviews with 200+ product professionals), and the level-based skills framework from the Product Led Alliance into a workable number.
- Product Discovery — user research, interviews, jobs-to-be-done, insight synthesis
- Strategy & Vision — product vision, strategic impact, market scanning
- Roadmapping & Prioritization — RICE/ICE, opportunity scoring, backlog management
- Stakeholder Management — cross-functional alignment, executive communication, managing up
- Data & Metrics — OKRs, north-star metric, A/B testing, statistical significance
- UX Sense — usability instinct, design collaboration, user-journey concepts
- Technical Fluency — API concepts, estimating complexity, build vs. buy
- Go-to-Market — launch coordination, pricing, enabling marketing, sales, and CS
- Leadership & Coaching — leading without authority, feedback, developing PMs
Each competency traces back to an established source. Product Discovery and UX Sense map to Mehta's "Voice of the Customer" and "User Experience Design." Data & Metrics covers the Data Analytics and Experimentation areas of the Product Compass map. Leadership & Coaching bundles Mehta's "Team Leadership" and "Managing Up." That keeps the matrix compatible with the models your PMs already know.
The filled-in matrix: Associate PM to Product Lead
This is the heart of the guide. The four career levels differ not by years of experience but by scope, autonomy, and strategic influence. The overview below frames the levels before the full matrix follows.
| Level | Scope | Core question | Typical evidence |
|---|---|---|---|
| Associate PM | Single features or components | Does this person execute defined initiatives cleanly? | Completed feature specs, contributed discovery notes |
| PM | One product area, end-to-end | Does this person own a feature from discovery to launch? | Led roadmap session, shipped feature |
| Senior PM | Annual roadmap, multiple teams | Does this person shape strategy and prioritization independently? | Reprioritized roadmap, influenced company OKRs |
| Product Lead | Portfolio or business unit | Does this person align several areas on one vision? | Board presentation, coached and promoted PMs |
The matrix below fills each of the nine competencies across all four levels with an observable behavioral anchor. It is meant as a download core: copy the table into Excel, Sheets, or Notion and add columns for self-assessment and manager assessment.
| Competency | Associate PM | PM | Senior PM | Product Lead |
|---|---|---|---|---|
| Product Discovery | Joins user interviews as an observer and takes structured notes | Runs user interviews independently and synthesizes findings into feature requests | Owns discovery cycles from recruiting to synthesis and defines the team's research agenda | Sets the discovery standard for the whole PM team and coaches other PMs on methods |
| Strategy & Vision | Understands and can explain the product vision; executes defined initiatives | Defines feature strategy within the vision and prioritizes the backlog against strategic goals | Develops product strategy for their area, influences company OKRs, and scans the market proactively | Owns portfolio strategy across business units and presents the vision at board level |
| Roadmapping & Prioritization | Maintains tickets and updates the existing roadmap on request | Runs roadmap sessions independently and prioritizes with RICE or ICE for their area | Builds annual roadmaps from strategic goals and reprioritizes when the market shifts | Coordinates roadmaps across multiple teams and allocates resources across product lines |
| Stakeholder Management | Gives status updates in team meetings and escalates conflicts to the manager | Manages cross-functional stakeholder expectations and justifies feature decisions | Facilitates executive reviews and resolves conflicts between stakeholder groups independently | Secures executive buy-in for product strategy and maintains C-level relationships |
| Data & Metrics | Reads dashboards and understands KPIs without defining them | Defines feature metrics, analyzes A/B test results, and spots outliers | Sets area OKRs, interprets statistical significance, and identifies growth levers | Defines the north-star metric and drives data-informed portfolio decisions |
| UX Sense | Gives structured feedback on wireframes and uses design tools as a viewer | Defines UX requirements in PRDs, runs usability checks, and decides trade-offs with design | Shapes user-journey concepts and establishes design principles for the product area | Sets UX standards for the whole product organization and embeds accessibility requirements |
| Technical Fluency | Understands API concepts and database basics and communicates with engineering without misunderstandings | Estimates technical complexity, scopes features with engineering, and spots risks during planning | Leads API scoping, evaluates build vs. buy vs. integrate, and communicates systemic dependencies | Coordinates platform decisions and understands architecture implications for product strategy |
| Go-to-Market | Supports GTM prep with release notes and FAQ documents | Coordinates feature launches with marketing, sales, and CS and creates enablement material | Runs product launches cross-functionally, defines pricing tiers, and manages launch risks | Owns the market entry of new product lines and coordinates GTM with C-level and investors |
| Leadership & Coaching | Learns from senior PMs and shows proactivity and initiative | Leads without formal authority and aligns engineering and design on shared goals | Coaches junior PMs informally, gives structured feedback, and drives team rituals like retros | Leads the PM team formally, owns hiring and development, and builds a high-performance culture |
These anchors are deliberately observable. "Reprioritizes the roadmap when the market shifts" can be evidenced with an artifact — a vision like "thinks strategically" cannot. That is the difference between a matrix that carries promotions and one that just looks good.
The rating scale: 5 points on the BARS principle
Behavioral anchors need a scale that is equally observable. Behaviorally Anchored Rating Scales describe each point through concrete behavior rather than an abstract "good" or "very good." For PM competencies, a five-point variant works well.
| Level | Meaning | Example evidence |
|---|---|---|
| 1 | Observes / learns — shadows others on this competency | Shadowed three user interviews, took notes |
| 2 | Guided — executes, but with close support | Ran an interview while observed by a PM |
| 3 | Independent — performs the competency on their own | Owned a roadmap prioritization alone |
| 4 | Optimizes — improves the process for others | Revised the RICE template, adopted team-wide |
| 5 | Coaches / sets standards — develops others and defines benchmarks | Trained two PMs on discovery methods |
Two rules make the scale robust. First, from level 4 onward evidence is mandatory — a link to an artifact (roadmap, OKR dashboard, feature spec) instead of a claim. Second, calibrate across self-assessment, peer review, manager review, and a final calibration meeting. For practical examples of anchored scales, see our piece on skill management software including an RFP checklist.
Building the template: Excel, Google Sheets, or Notion
The simplest build uses five tabs: one per level plus a summary tab that aggregates everyone's scores. That avoids one overloaded mega-table and keeps each role readable.
- Competency — one of the nine core competencies
- Behavioral anchor — the level-specific anchor from the matrix above
- Self-assessment — 1 to 5 on the BARS scale
- Manager assessment — 1 to 5, recorded separately
- Evidence link — mandatory artifact from level 4 onward
- Development action — a concrete next step with a target date
For color coding, Müller's scheme works well: grey (not applicable), red (not met), yellow (below expectation), blue (met), green (exceeded). The generic, step-by-step build of a matrix — independent of role — is covered in depth in our skill management guide. If you are looking for a tool to manage it, the skills and competency management category is a good place to compare options.
Legal context: works council, GDPR, and the AI Act
In companies operating in Germany, Austria, and Switzerland, a PM skills matrix is not a purely internal HR tool. Once it applies company-wide, it touches co-determination and data protection law. Accounting for that early avoids a later stop from the works council.
Section 94(2) BetrVG: the works council must consent
A company-wide competency matrix counts as a "general assessment guideline." Establishing such guidelines requires the works council's consent under Section 94(2) of the German Works Constitution Act (BetrVG). The statute states that paragraph 1 applies accordingly "to the establishment of general assessment guidelines." Without that consent, the works council can demand that the guidelines be discontinued and that assessments already produced be destroyed — consistent with the settled case law of the Federal Labour Court on assessment guidelines.
If an HR software with a rating function is involved as well, Section 87(1) no. 6 BetrVG on technical monitoring devices often applies too. The practical consequence is the same: a works agreement before roll-out is the clean route.
GDPR and Section 26 BDSG: skill data is personal data
Skill ratings are personal employee data and require a legal basis. Section 26(1) of the German Federal Data Protection Act (BDSG) permits processing where it is necessary for the employment relationship. As an opening clause, Article 88 GDPR explicitly allows a works agreement to set more specific rules for processing employee data — it can therefore serve as proof of lawfulness.
- Proportionality — capture only job-relevant competencies, no non-professional attributes
- Purpose limitation — use skill data only for the documented purpose, such as development and promotion
- Works agreement — conclude one before roll-out as a legal basis
- Data protection impact assessment — review it for ongoing digital skill tracking
- Retention periods — define and document them
AI literacy as a PM competency under the EU AI Act
If your PMs build AI features — recommendation engines, LLM functions, predictive analytics — a dedicated matrix row belongs in the mix. Article 4 of the EU AI Act has applied since 2 February 2025 and obliges providers and deployers of AI systems to ensure a sufficient level of AI literacy among their staff. PMs who co-own an AI feature are, in effect, deployers under the regulation. An AI literacy row makes that responsibility visible in the matrix.
| Competency | Associate PM | PM | Senior PM | Product Lead |
|---|---|---|---|---|
| AI Literacy | Understands basics like ML, LLM, hallucination, and bias and distinguishes AI from classic features | Defines acceptance criteria for AI features, spots ethical risks, and communicates AI limitations to users | Scopes AI features with the tech team, evaluates model output quality, and designs transparency UX | Owns AI product strategy, ensures Article 4-compliant AI literacy for the team, and leads responsible-AI reviews |
Common mistakes with PM matrices — and how to avoid them
These pitfalls are PM-specific, not generic. They decide whether the matrix sets promotion signals correctly or distorts them.
- Outputs instead of outcomes — "shipped 5 features" says nothing. Anchor to impact, such as "user retention +15%."
- Homogenizing levels too early — rating Associate PM and Senior PM with identical anchors creates false promotion signals.
- Treating UX Sense and Technical Fluency as optional — in modern product teams both are mandatory, even for non-technical PMs.
- No evidence requirement — without artifact links from level 4 onward, ratings turn subjective.
- No update cycle — PM competencies shift with AI and platform trends. Review at least annually.
Frequently asked questions
What is a product management skills matrix?
A product management skills matrix is a structured tool that maps PM core competencies against career levels — from Associate PM to Product Lead. Each cell holds a behavioral anchor describing what strong performance looks like at that level. It adds fields for self-assessment, manager assessment, and evidence. Common formats are Excel, Google Sheets, or Notion.
Which competencies does a product manager really need?
Established frameworks cover nine core fields: Product Discovery, Strategy & Vision, Roadmapping & Prioritization, Stakeholder Management, Data & Metrics, UX Sense, Technical Fluency, Go-to-Market, and Leadership & Coaching. The guiding principle is the T-shaped profile: a solid base across all fields, plus one or two real specializations.
How does a Senior PM differ from a PM?
The difference is scope, autonomy, and strategic influence — not years of experience. A PM owns a product area end-to-end. A Senior PM shapes strategy and prioritization independently, owns an annual roadmap across multiple teams, and influences company OKRs. This shift from execution toward strategy and influence is the through-line of every PM career ladder.
Does the works council have to consent to a competency matrix?
Usually yes. A company-wide competency matrix counts as a general assessment guideline, and establishing such guidelines requires works council consent under Section 94(2) BetrVG. Without consent, the works council can demand discontinuation and destruction of assessments already produced. The clean route is a works agreement before roll-out.
How often should I update the PM skills matrix?
Assessments sensibly run quarterly or twice a year, paired with calibration. The matrix itself — the anchors — should be reviewed at least annually. PM competencies shift with AI and platform trends faster than most frameworks reflect. A static matrix loses credibility within a year.
A filled-in matrix is the fastest way from gut feeling to fair development paths. Copy the table, adapt the anchors to your business model, and connect every rating to a concrete development action. The framework for doing so is in our skill management guide.
Jürgen Ulbrich
Jürgen Ulbrich has more than a decade of experience in developing and leading high-performing teams and companies. As an expert in employee referral programs as well as feedback and performance processes, Jürgen has helped over 100 organizations optimize their talent acquisition and development strategies.
