Assessing Product Team Strengths and Identifying Skill Gaps
This skill teaches you how to run a structured competency assessment across your product team, producing a scored heatmap that reveals individual proficiency levels, shared blind spots, and the highest-impact areas for development investment.
Start by defining the competencies that matter for your team's context using a structured framework. Have each PM self-assess their proficiency on a consistent scale, then layer in manager ratings and peer input. Aggregate the scores into a team-level heatmap to surface patterns: shared blind spots, individual development needs, and strengths you can leverage. Prioritize gaps by their impact on current team objectives.
Outcome: You produce a team competency heatmap that makes invisible skill gaps visible, enabling targeted hiring, training, and role-assignment decisions backed by data instead of gut feel.
Prerequisites
- A defined set of product management competencies (use the Product Team Competencies Framework or an equivalent)
- Familiarity with the strategic vs. tactical and internal vs. external axes from the parent framework
- Access to direct reports or peers who will participate in the assessment
- A spreadsheet tool or competency tracking system for scoring and aggregation
Overview
Every product leader eventually faces the same question: where is my team strong, and where are we exposed? The answer usually lives in scattered impressions from 1:1s, performance reviews, and the occasional crisis that reveals a missing capability. Assessing product manager skills systematically replaces those impressions with a structured picture of your team's collective proficiency. The output is a team competency heatmap, a single artifact that maps each PM's self-assessed and manager-validated scores across every competency in your framework. This heatmap is the foundation for nearly every downstream decision: who needs coaching, what training to invest in, which roles to hire for next, and how to distribute work across the team to maximize coverage.
This skill sits at the diagnostic center of the Product Team Competencies Framework. Before you can build career development plans, write targeted job descriptions, or design interview rubrics, you need to know what you have and what you lack. The assessment process described here works for teams of any size, from a two-person PM function at a startup to a 30-person product organization at a growth-stage company. It works across different PM archetypes (growth PMs, platform PMs, customer-facing PMs) because it evaluates proficiency against a shared competency model rather than a single role template.
The process itself is straightforward but requires discipline. You will define the competency set, calibrate the scoring rubric, run self-assessments and manager assessments in parallel, reconcile divergences in a calibration conversation, aggregate results into a team view, and then prioritize the gaps that matter most given your current business context. The entire cycle should take 3-5 hours for the initial round with a team of 4-8 PMs, and roughly half that time for subsequent quarterly or semi-annual refreshes. The result is not a performance review. It is a diagnostic tool, designed to make invisible gaps visible so you can act on them before they become costly.
How It Works
The assessment works by converting subjective impressions about product manager skills into structured, comparable data points. At its core, the technique relies on three mechanisms: a shared competency taxonomy, a calibrated proficiency scale, and multi-perspective scoring.
The shared competency taxonomy is your list of specific skills that matter. The Product Team Competencies Framework organizes these across two axes: strategic vs. tactical (how high-level or execution-oriented the skill is) and internal vs. external (whether the skill faces the organization or the market). Examples include user research, data analysis, stakeholder management, roadmap planning, experimentation design, and technical fluency. The taxonomy ensures everyone is evaluated against the same dimensions, so comparisons between individuals are meaningful rather than apples-to-oranges.
The calibrated proficiency scale is what turns vague assessments into usable data. A typical scale runs from 1 to 5, but the key is anchoring each level with observable behaviors rather than abstract labels. "3 = Proficient" means nothing on its own. "3 = Can independently run a discovery sprint, select appropriate research methods, and synthesize findings into prioritized opportunity statements without manager review" gives assessors something concrete to calibrate against. Without behavioral anchors, scores cluster around 3-4 because people default to the comfortable middle.
Multi-perspective scoring is the mechanism that catches blind spots. Self-assessments alone are unreliable in predictable ways: high performers tend to underrate themselves (the Dunning-Kruger inverse), while less experienced PMs often overrate capabilities they have not yet been tested on. Manager assessments add an external check, but managers have their own blind spots, particularly around skills they do not personally value or rarely observe. Adding a peer perspective (even informally) creates a triangulation effect that produces more accurate readings.
The aggregation step is where individual data becomes team intelligence. When you lay out all scores in a matrix (PMs on one axis, competencies on the other), patterns emerge that are invisible at the individual level. You might discover that your entire team scores below 2 on experimentation design, which explains why your A/B testing program keeps stalling. Or you might find that strategic skills cluster in one or two senior PMs, creating a bus-factor risk. These patterns are the real output of the assessment. Individual scores matter for coaching conversations, but team-level patterns drive organizational decisions about hiring, training, and restructuring.
The prioritization layer is what prevents the assessment from becoming an academic exercise. Not all gaps are equally urgent. A gap in competitive analysis matters less if you are in a market with no direct competitors. A gap in stakeholder management matters enormously if your product team is losing credibility with the executive team. Prioritization connects the competency data to your current business context, turning a diagnostic into an action plan.
Step-by-Step
Step 1: Select and Customize Your Competency Set
Start with the competencies defined in the Product Team Competencies Framework, which maps skills across the strategic-tactical and internal-external axes. Review each competency and decide whether it applies to your team's current context. A B2B enterprise PM team might weight stakeholder management and technical fluency heavily, while a consumer growth team might prioritize experimentation design and data analysis. Remove competencies that are genuinely irrelevant (not just underdeveloped) and add any that are missing for your domain.
Aim for 10-18 competencies total. Fewer than 10 gives you an incomplete picture; more than 18 creates assessment fatigue and dilutes focus. Document each competency with a one-sentence definition so every participant shares the same understanding of what 'user research' or 'go-to-market strategy' means in your organization.
Tip: If you are unsure whether a competency belongs, ask: 'Would a PM on this team ever need to demonstrate this skill in the next 12 months?' If the answer is no, cut it. You can always add it back in a future cycle.
Step 2: Define Behavioral Anchors for Each Proficiency Level
Create a 1-5 proficiency scale with behavioral anchors for each competency. Level 1 means the PM has awareness of the skill but cannot execute it independently. Level 2 means they can execute with significant guidance. Level 3 means they can execute independently in routine situations.
Level 4 means they can handle complex or ambiguous situations and coach others. Level 5 means they are a recognized expert who shapes the team's approach. Write 1-2 sentence descriptions for each level of each competency. ' This step takes the most time upfront but is the single biggest determinant of assessment quality.
Without anchors, scores are meaningless because each assessor interprets the scale differently.
Tip: Write anchors for levels 1, 3, and 5 first. Levels 2 and 4 are naturally the transitions between them, and you can usually derive their descriptions by interpolating.
Step 3: Run Self-Assessments
Share the competency list and behavioral anchors with each PM and ask them to score themselves on every competency. Use a simple spreadsheet or form with one row per competency and a column for the score. Ask each PM to also write a one-sentence justification for any score of 1, 2, 4, or 5. Justifications for extreme scores surface the reasoning behind the rating and give you material for the calibration conversation.
Set a clear deadline (3-5 business days is sufficient) and emphasize that this is a development tool, not a performance evaluation. The distinction matters because performance anxiety compresses scores toward the middle. Collect all self-assessments before sharing any manager assessments to avoid anchoring effects.
Tip: Frame the self-assessment as 'where are you today, not where you should be.' PMs who feel judged will inflate scores on competencies they think are expected of them, which defeats the purpose of the diagnostic.
Step 4: Complete Manager Assessments Independently
Before looking at any self-assessment results, score each PM yourself using the same competency list and behavioral anchors. Work from concrete evidence: recent project outcomes, observable behaviors in meetings, artifacts they have produced, feedback from cross-functional partners. Score each competency and write a brief justification for scores where you feel confident. Mark any competency where you lack sufficient observation data with a flag rather than guessing.
Flagged competencies are valuable information because they reveal areas where you have limited visibility into a PM's work, which is itself a management gap worth addressing. Complete all manager assessments before moving to the calibration step.
Tip: Block 20-30 minutes per PM and do all assessments in a single sitting if possible. Switching between PMs mid-assessment tends to introduce comparison bias where you start scoring relative to each other rather than against the behavioral anchors.
Step 5: Run Calibration Conversations
Schedule a 30-45 minute 1:1 with each PM to compare self-assessment and manager assessment scores side by side. Focus the conversation on divergences of 2 or more points, which typically indicate either a blind spot (PM rates themselves higher than you do) or hidden strength (PM rates themselves lower than you do). For each divergence, share the specific evidence behind your score and ask the PM to share theirs. The goal is not to negotiate a consensus score but to arrive at a more accurate picture together.
Update scores where the conversation changes your assessment. Document the agreed-upon scores and the key discussion points. This calibration step is where the real development value lives, because the conversation itself builds self-awareness regardless of the final number.
Tip: Start the calibration conversation with a competency where you scored the PM higher than they scored themselves. This sets a constructive tone and makes the PM more receptive when you discuss areas where your assessment is lower than theirs.
Step 6: Aggregate into a Team Competency Heatmap
Build a matrix with PMs as rows and competencies as columns. Enter the calibrated scores from Step 5. Apply conditional formatting so that scores of 1-2 appear in red or orange, scores of 3 appear in yellow, and scores of 4-5 appear in green. This visual heatmap is your primary diagnostic artifact.
Look for three patterns: vertical stripes (a single competency is weak across the whole team, indicating a systemic gap), horizontal stripes (a single PM is weak across many competencies, indicating a role-fit or experience issue), and clusters of strength (competencies where your team has depth, which represent organizational advantages to protect). Calculate averages for each competency column to produce a team-level proficiency score. Sort competencies by average score to create a rank-ordered list of team strengths and gaps.
Tip: Add a row at the bottom showing the 'minimum viable proficiency' you need for each competency given your current business context. This makes gaps concrete: the distance between the team average and the minimum viable level is your development urgency for that competency.
Step 7: Identify Concentration Risks and Coverage Gaps
Beyond averages, look for concentration risk: competencies where only one PM scores 4 or higher. These are bus-factor risks. If that PM leaves or changes roles, the team loses its only source of that capability. Flag any competency where fewer than two PMs score 3 or above.
Also check for coverage gaps across the strategic-tactical and internal-external axes from the parent framework. If all your team's strength clusters in tactical-internal skills (execution, process management, internal communication) and you have systematic weakness in strategic-external skills (market analysis, competitive positioning, vision-setting), you have a structural imbalance that hiring one senior PM might not fix. Document these concentration risks and structural patterns alongside the heatmap.
Tip: Overlay the competency map against the four quadrants from the Product Team Competencies Framework (strategic-external, strategic-internal, tactical-external, tactical-internal). If any quadrant has no competency averaging above 3, that is your highest-priority area.
Step 8: Prioritize Gaps by Business Impact
List all competencies where the team average falls below your minimum viable proficiency threshold from Step 6. For each gap, answer three questions: How much does this gap affect our ability to hit this quarter's goals? How much does this gap affect our ability to hit next year's goals? Can we mitigate this gap through hiring, training, or redistributing work?
Score each gap on urgency (1-3) and addressability (1-3). Gaps that are both urgent and addressable go to the top of the action list. Gaps that are urgent but hard to address (like needing deep technical fluency that takes years to build) require a different intervention, such as hiring or embedding with engineering. Gaps that are neither urgent nor addressable get documented for future cycles but do not consume current resources.
Tip: Limit your active development focus to 2-3 gaps per quarter. Product teams that try to close five or six gaps simultaneously make no meaningful progress on any of them.
Step 9: Translate Priorities into Action Plans
For each priority gap, define the intervention: individual coaching, structured training, stretch assignments, hiring, or organizational change. Connect each intervention to the specific PMs who will participate and the specific competency scores you expect to shift. Set a concrete review date (typically 90 days) when you will re-assess those competencies to measure progress. Share the team-level findings (anonymized or aggregated) with the full PM team so everyone understands the collective priorities.
Share individual findings privately in 1:1s. Feed the prioritized gaps into the sibling skill for building career development plans, where each PM gets a personalized growth roadmap based on their specific scores and the team's collective needs.
Tip: Pair PMs with complementary strengths for collaborative work. If one PM scores 4 on user research and 2 on data analysis, and another has the reverse profile, pairing them on a discovery project creates a natural peer-learning dynamic.
Examples
Example: Early-stage startup with a 3-person PM team
A Series A SaaS company has 3 PMs: one senior (5 years experience), one mid-level (2 years), and one associate who transitioned from customer success 6 months ago. The head of product needs to figure out who can own what as they scale from one product to two. They have limited budget for external training and need to prioritize ruthlessly.
The head of product selects 12 competencies from the Product Team Competencies Framework, dropping enterprise-specific skills like procurement management that are not relevant yet. They write behavioral anchors for levels 1, 3, and 5 only, keeping the process lightweight. Self-assessments take each PM about 20 minutes. The heatmap reveals that the senior PM scores 4-5 on strategic competencies (vision, roadmap, stakeholder management) but only 2 on data analysis and experimentation.
The mid-level PM is the reverse: strong on data and execution (4s), weak on strategy and stakeholder management (2s). The associate PM scores 1-2 across most competencies but has a surprising 4 on user research from their customer success background. The team-level pattern shows a dangerous gap in experimentation, where no PM scores above 2. The head of product prioritizes two actions: send the mid-level PM to a stakeholder management workshop (urgent because they are about to lead the second product), and pair the senior PM with the mid-level PM on a structured A/B testing initiative to build experimentation capability across both.
The associate PM gets a 90-day development plan focused on roadmapping and prioritization, with the senior PM as their mentor. Total time for the full cycle: about 4 hours including calibration conversations.
Example: Growth-stage B2B company with 8 PMs across 3 squads
A Series C B2B platform company has 8 PMs organized into 3 squads: core platform (3 PMs), growth (2 PMs), and integrations (3 PMs). The VP of Product suspects that the growth squad is struggling because they lack certain competencies, but is not sure which ones. The company recently lost a deal because the competitor had stronger partner ecosystem positioning.
The VP selects 16 competencies and distributes the assessment with detailed behavioral anchors. Two PM managers each handle calibration conversations for their direct reports. The aggregated heatmap reveals that the growth squad scores 1-2 on competitive analysis and go-to-market strategy, which explains their recent struggles. Interestingly, the core platform squad has the opposite profile: strong on competitive awareness (their lead PM used to work at the main competitor) but weak on technical API fluency, which is causing friction with engineering.
8 across all 8 PMs, the lowest score on the entire heatmap. The VP recognizes this as a structural gap: they do not need 8 PMs trained in go-to-market, but they need at least 2-3 who can handle launches independently. The concentration risk analysis shows that competitive analysis depends entirely on one PM on the core platform squad. The VP takes three actions: hires a senior PM with go-to-market expertise for the growth squad, creates a monthly competitive intelligence session led by the strong PM on the platform team to build capability across the organization, and assigns the integrations squad lead a stretch project involving partner API design to close the technical fluency gap.
The re-assessment is scheduled for 5 months out.
Example: Consumer product team assessing after a reorg
A consumer fintech app just reorganized its product team from feature-based squads to outcome-based squads (activation, retention, monetization). The 6 PMs have been reshuffled into new squad assignments. The Director of Product needs to validate whether each squad has the right mix of product manager skills for its outcome area, and whether any squad has a critical blind spot.
The Director runs the assessment using 14 competencies, grouped by the four quadrants of the Product Team Competencies Framework. The assessment reveals that the activation squad (2 PMs) has strong experimentation and data analysis skills (both PMs at 4) but scores 1-2 on user research, meaning they optimize funnels without deep qualitative understanding of why users drop off. The retention squad has the opposite imbalance: excellent at qualitative research (one PM is a former UX researcher) but weak on quantitative rigor. The monetization squad scores well overall but has a critical concentration risk: only one PM (out of 2) understands pricing strategy at a proficient level.
Looking at the quadrant overlay, the entire team skews heavily toward tactical-external skills (experimentation, user research, analytics) and is systematically weak on strategic-internal skills (organizational alignment, roadmap communication, resource planning). This explains why the team ships well but struggles to get executive buy-in for longer-term bets. The Director prioritizes two interventions: swap one PM between activation and retention to balance the qualitative-quantitative mix, and invest in a structured stakeholder communication training for the full team. The monetization squad's pricing gap gets flagged for the next hire.
Total assessment time across 6 PMs and two calibration sessions: approximately 5 hours.
Example: Large product org benchmarking across regions
A global enterprise software company has 24 PMs across three regions (US, EMEA, APAC). Each region has a Head of Product. The Chief Product Officer wants to understand whether there are systemic competency differences across regions and establish a baseline for a new global PM development program. The assessment needs to be lightweight enough to run across time zones without excessive meeting overhead.
The CPO and the three regional heads agree on 15 competencies and co-author the behavioral anchors to ensure cultural consistency in interpretation. Self-assessments are distributed via a shared form with a 7-day window. Manager assessments are completed independently by each regional head. Calibration conversations happen in existing 1:1 slots rather than scheduling new meetings, keeping the overhead manageable.
The aggregated heatmap across all 24 PMs reveals two striking patterns. 1). The US team shows the reverse. This is not about individual capability but about organizational culture: the APAC office rewards consensus-building, while the US office rewards bold strategic bets.
5 on platform thinking and technical architecture fluency, a gap that matters because the company is mid-migration to a platform model. The CPO uses these findings to design a global PM development program with two tracks: a strategic positioning module prioritized for APAC, and a platform-thinking module required globally. She also creates a cross-regional mentoring program pairing high-scoring PMs in one region with developing PMs in another. The assessment becomes a semi-annual process anchored to the company's planning cycles.
Best Practices
Write behavioral anchors before distributing the assessment, not after. If you define what each proficiency level looks like in observable terms before anyone scores, you eliminate 80% of the calibration arguments. Teams that skip anchors and 'know it when they see it' produce scores that reflect personal standards rather than shared criteria, making cross-team comparisons meaningless.
Separate the assessment from the performance review cycle by at least one month. When competency assessments are bundled with compensation discussions, PMs inflate scores on competencies tied to promotion criteria and deflate scores on competencies they see as optional. Running the assessment in a different month, framed explicitly as a development tool, produces more honest data.
Score confidence independently in writing before any calibration discussion. When you and a PM discuss scores together, the first number stated becomes an anchor that pulls the other person's assessment toward it. Having both parties commit their scores to paper (or a spreadsheet) before the conversation preserves the information value of disagreements.
Re-assess on a consistent cadence, typically every 6 months. Quarterly is too frequent for most competencies to show meaningful change and creates assessment fatigue. Annual is too infrequent to catch emerging gaps or validate that development investments are working. Semi-annual gives enough time for growth while maintaining accountability.
Include at least one peer data point for each PM when possible. Manager assessments miss skills that manifest in cross-functional collaboration, pair work, or mentoring. Even an informal peer check (asking 2-3 partners to rate a PM on 3-5 competencies) adds signal in areas where manager visibility is low, such as technical communication with engineers or stakeholder management with sales.
Document the business context alongside each assessment cycle. Record what your team's goals were, what projects were active, and what constraints existed. Six months later, you will need this context to interpret why scores looked the way they did and whether shifts represent genuine growth or just a change in project mix.
Keep the raw data but present the heatmap. Stakeholders (your VP, HR partners, hiring managers) need the visual pattern, not a spreadsheet of numbers. The heatmap communicates 'we are systematically weak in experimentation design' faster than any table. Reserve the raw data for your own calibration work and 1:1 coaching conversations.
Treat the assessment as a team diagnostic, not individual report cards. The highest-value insight is almost always the team-level pattern (e.g., 'nobody on this team can run a pricing analysis') rather than any single PM's score. Lead with team patterns in group settings and save individual data for private conversations.
Common Mistakes
Using vague proficiency labels without behavioral anchors
Correction
Scales labeled 'Beginner, Intermediate, Advanced' without concrete examples produce scores that reflect each assessor's personal calibration rather than observable skill levels. You can spot this when two managers score the same PM dramatically differently on the same competency, or when self-assessment scores cluster tightly around 3. Fix it by writing 1-2 sentence behavioral descriptions for levels 1, 3, and 5 of each competency before distributing the assessment. Anchoring eliminates ambiguity and makes scores comparable across raters.
Running the assessment once and never repeating it
Correction
A single assessment produces a snapshot, but the value is in the trend. Teams that assess once, build a development plan, and never re-assess have no way to know whether their investments in training or coaching actually moved the needle. The lack of follow-through also signals to PMs that the exercise was performative. Set the re-assessment date during the initial cycle, put it on the calendar, and treat it as non-negotiable.
Even a lightweight re-assessment of just the priority gaps takes under an hour and closes the feedback loop.
Trying to close every gap simultaneously
Correction
After the heatmap reveals six or seven gaps, the temptation is to launch a development initiative for each one. This scatters attention so thin that no gap closes meaningfully. 5 points. Limit active development focus to 2-3 gaps per quarter, chosen based on business impact.
Accept that some gaps will persist until a future cycle, and document that decision explicitly so it is a conscious trade-off rather than an oversight.
Conflating the competency assessment with a performance review
Correction
When PMs believe their scores will affect compensation or promotion decisions, they game the assessment. You will notice this as uniformly inflated self-assessment scores (mostly 4s and 5s) with little differentiation between competencies. The assessment loses its diagnostic value because it reflects what PMs want to project rather than what is true. Separate the assessment from the review cycle by framing and timing.
Run it in a different month, use different language ('development diagnostic' vs. 'performance evaluation'), and explicitly state that scores will not be used in promotion or compensation decisions.
Assessing only individual PMs without looking at team-level patterns
Correction
Managers who focus exclusively on individual scores miss the most actionable insights. An individual PM scoring 2 on competitive analysis is a coaching opportunity. Every PM on the team scoring 2 on competitive analysis is a structural problem that coaching alone will not fix. After building the heatmap, spend at least 20 minutes analyzing column patterns (team-wide gaps) and quadrant imbalances (strategic-tactical or internal-external skews) before diving into individual development conversations.
Team patterns drive different interventions: hiring, training programs, or restructuring work allocation.
Ignoring concentration risk in areas where the team scores well on average
Correction
A team average of 3.5 on a competency looks healthy at first glance, but if that average comes from one PM at 5 and three PMs at 2-3, you have a fragile capability that disappears if that one PM leaves. Scan every competency that averages above 3 and check the distribution. If fewer than two PMs score 3 or above, flag it as a concentration risk even though the average looks fine. Address it by using the strong PM as a mentor or pairing them with a developing PM on relevant projects.
Other Skills in This Method
Showcasing PM Competencies in Portfolios and Resumes
How to use the competency framework to structure a product manager resume or portfolio that clearly demonstrates breadth and depth across strategic, tactical, internal, and external skills.
Defining Competency Expectations from Associate PM to Senior PM
How to calibrate expected proficiency levels across each quadrant of the framework for associate, mid-level, and senior product manager roles.
Building Personalized PM Career Development Plans Using Competency Data
How to translate competency assessment results into actionable growth plans that guide product managers on how to advance their careers.
Differentiating PM Role Types Using the Competency Framework
How to use the quadrant model to distinguish technical product managers, growth PMs, and platform PMs from generalist roles based on their competency emphasis.
Mapping PM Competencies Across Strategic vs. Tactical and Internal vs. External Axes
How to plot core product management skills onto the 2D competency grid to visualize where each capability falls along the strategic-tactical and internal-external dimensions.
Writing Competency-Based Product Manager Job Descriptions
How to translate framework quadrants into clear, measurable job descriptions and hiring criteria that attract the right candidates for specific PM roles.
Designing PM Interview Rubrics Aligned to Competency Quadrants
How to structure product manager interview questions and scoring rubrics that evaluate candidates across all four quadrants of the competency framework.
Frequently Asked Questions
How do I assess product manager skills if my team is too small for meaningful patterns?
Even a 2-person PM team benefits from the assessment. You will not get statistically significant team patterns, but you will get two valuable outputs: a clear map of where each PM's strengths and gaps lie (useful for coaching and work allocation), and a view of which competencies have zero coverage on the team (useful for your next hire profile). For teams under 4, skip the team-level heatmap and focus the calibration conversation on identifying the 2-3 competencies most critical for the next 6 months.
How long should the full assessment cycle take from start to finish?
Plan for 2-3 weeks from distributing the self-assessment to completing all calibration conversations and building the heatmap. The self-assessment itself takes each PM 20-30 minutes. Manager assessments take 20-30 minutes per PM. Calibration conversations run 30-45 minutes each. The heatmap aggregation and prioritization takes 1-2 hours. The biggest bottleneck is usually scheduling the calibration 1:1s, so book those early in the process.
Should I assess product manager skills before or after defining competency level expectations?
Ideally, define your competency expectations first using the sibling skill on [defining competency levels from associate to senior PM](/skills/defining-competency-levels-from-associate-to-senior-pm). The level expectations become your behavioral anchors, which makes the assessment more precise. However, if you are in a hurry, you can run a rough assessment with simple 1-5 behavioral anchors and refine the level definitions later. A rough assessment this week beats a perfect assessment next quarter.
How do I handle a PM who strongly disagrees with my assessment of their skills?
Disagreements of 2 or more points are expected and valuable. They almost always stem from one of three causes: the PM has evidence of capability you have not observed (ask for specific examples), you have evidence of a gap the PM has not recognized (share specific situations), or you are interpreting the behavioral anchor differently (re-read the anchor together). Do not force consensus. If you cannot resolve the divergence, record both scores and note the disagreement. The discussion itself builds self-awareness, which is more valuable than the number.
Why does my team's assessment keep producing scores clustered around 3?
Score compression around the middle is the most common assessment failure, and it almost always indicates that your behavioral anchors are not specific enough. When assessors are unsure what distinguishes a 2 from a 3 or a 3 from a 4, they default to the safe middle. Rewrite your anchors with more concrete, observable behaviors. A 3 should describe specific outputs the PM can produce independently. Also check whether PMs perceive the assessment as linked to performance reviews, which causes them to avoid low scores while also avoiding seeming arrogant with high scores.
How do I use the assessment results to inform hiring decisions?
After building the team heatmap, look at competencies where the team average is below your minimum viable threshold and where no current PM is likely to close the gap through development in the next 6-12 months. These are your hiring criteria. Feed the priority gaps directly into the sibling skill on [writing competency-based PM job descriptions](/skills/writing-competency-based-pm-job-descriptions), which translates gap data into specific job requirements. This approach produces job descriptions grounded in actual team needs rather than generic wishlists.
Can I use the same assessment across different PM role types like growth PMs and platform PMs?
Yes, but adjust the 'minimum viable proficiency' threshold per role type rather than changing the competency list. All PMs should be assessed on the same competency set so you can compare across the team. The difference is in expectations: a growth PM might need a 4 in experimentation but only a 2 in technical architecture, while a platform PM has the reverse profile. Use the sibling skill on [differentiating PM role types](/skills/differentiating-product-manager-role-types) to set role-specific thresholds, then apply them as the comparison baseline in your heatmap.