Mapping Product Manager Skills Across Strategic-Tactical and Internal-External Axes
This skill teaches you to classify and plot every core product management competency onto a two-dimensional grid, giving you a visual map of where each capability sits along strategic-tactical and internal-external dimensions so you can diagnose gaps, shape roles, and guide development.
List every core PM competency your organization values. For each one, score it on two dimensions: strategic versus tactical (does it shape long-term direction or drive near-term execution?) and internal versus external (does it face the team and organization, or the market and customers?). Plot each competency onto a 2x2 grid using those scores. The resulting visual map reveals concentration patterns, coverage gaps, and role-shaping insights you can act on immediately.
Outcome: You produce a completed 2x2 competency map that visually shows where your organization's PM skills cluster and where blind spots exist, enabling concrete decisions about hiring priorities, role differentiation, and individual development plans.
Prerequisites
- A working list of 10-20 product management competencies relevant to your organization
- Basic understanding of strategic vs. tactical work in product management
- Familiarity with the concept of internal (team/org-facing) vs. external (market/customer-facing) PM activities
- Access to a whiteboard, spreadsheet, or diagramming tool for plotting
Overview
Mapping product manager skills onto a two-dimensional competency grid is the foundational exercise of the Product Team Competencies Framework. Without this map, conversations about PM growth, hiring, and team composition stay abstract. People talk about "strategic thinking" or "execution ability" without agreeing on what those labels actually contain or how they relate to each other. The mapping exercise forces that clarity. It turns a flat list of competencies into a spatial picture that reveals patterns invisible in a spreadsheet or bullet list.
The two axes capture the essential tensions of product management work. The vertical axis runs from strategic (shaping long-term direction, defining vision, influencing company bets) to tactical (shipping features, triaging bugs, running standups, writing specs). The horizontal axis runs from internal (stakeholder management, engineering collaboration, organizational influence) to external (user research, competitive analysis, market positioning, customer conversations). Every PM competency lands somewhere in the space these axes create, and that placement tells you something important about the competency's nature, who needs it most, and when it matters.
The artifact you produce is a plotted grid, either a physical whiteboard diagram, a slide, or a structured spreadsheet, with every competency placed at specific coordinates. This map becomes the input for nearly every downstream activity in the framework: assessing team strengths, differentiating role types, defining level expectations, and building career development plans. Getting the placement right matters, but perfection is not the goal. The goal is a shared, defensible picture that a team can use to make better decisions about people and priorities.
When done well, the completed map typically reveals two or three insights that surprise the team. Maybe the organization's competency list is heavily weighted toward internal-tactical skills, reflecting a culture that prizes execution over discovery. Maybe there is a gap in external-strategic capabilities, meaning nobody owns competitive strategy or market sensing at a senior level. These insights are the payoff. They convert a theoretical framework into actionable organizational intelligence.
How It Works
The 2x2 grid works because it decomposes the complexity of product management into two independent, meaningful dimensions. Each dimension represents a genuine tension in the PM role, and crossing them creates four quadrants that correspond to recognizable clusters of work.
The strategic-tactical axis captures time horizon and altitude of thinking. Strategic competencies shape what gets built and why over quarters and years: product vision, roadmap strategy, business model design, market entry planning. Tactical competencies determine how well things get shipped in days and weeks: backlog grooming, sprint planning, bug triage, release management, spec writing. Most competencies are not purely one or the other. "Roadmapping" is a good example. Defining a 12-month roadmap is strategic. Sequencing the next three sprints is tactical. When you map it, you place it according to its center of gravity for your organization, or you split it into two competencies if the distinction matters enough.
The internal-external axis captures audience and information flow. Internal competencies face the organization: influencing engineering leads, managing up to executives, facilitating cross-functional alignment, mentoring junior PMs. External competencies face the market and users: running discovery interviews, analyzing competitor positioning, crafting product messaging, interpreting usage data from real customers. Again, some competencies straddle the line. "Data analysis" can be internal (reporting to leadership) or external (understanding user behavior). Place it where the primary value creation happens, or split it.
Crossing the axes creates four quadrants. In the Product Team Competencies Framework, these quadrants are sometimes labeled: Strategic-External (visionary, market-shaping work), Strategic-Internal (organizational leadership, long-term planning), Tactical-External (customer-facing execution, support escalation, user testing), and Tactical-Internal (process management, sprint execution, documentation). The labels are less important than the spatial relationships. Competencies near each other on the grid are complementary. Competencies in opposite quadrants represent fundamentally different modes of working.
The mapping works best when you treat position as continuous rather than binary. Instead of forcing every competency into one of four boxes, use a 1-to-10 scale on each axis. A competency that scores 7 on strategic and 3 on internal sits in the upper-left area but close to the center, signaling it has tactical components. This continuous placement is more accurate and produces a richer map. It also makes disagreements productive: when two people place "stakeholder management" at different spots, the conversation about why is where the real insight lives.
A common misconception is that strategic-external is inherently more valuable or senior than tactical-internal. That hierarchy is false, and baking it into the map will distort every decision downstream. The grid is descriptive, not prescriptive. A team that lacks tactical-internal strength will ship late and burn out engineers, regardless of how brilliant the strategy is. The map's value comes from showing the full picture, not from ranking quadrants.
Step-by-Step
Step 1: Compile your master competency list
Gather every product management competency your organization recognizes or values. Pull from existing job descriptions, performance review rubrics, career ladder documents, and any internal competency models already in use. If no formal list exists, start with a brainstorm. " Aim for 12-20 competencies.
Fewer than 10 usually means you have rolled too many distinct skills into vague umbrella terms. More than 25 creates mapping fatigue without adding proportional clarity. Standardize the granularity: if "data analysis" is one item, "SQL querying" is too granular and "technical skills" is too broad.
Tip: If your organization has no existing competency list, interview three experienced PMs and ask: 'What are the ten most important things a PM at our company needs to be able to do?' Merge and deduplicate the responses. This takes 30 minutes and produces a list grounded in your actual context rather than generic frameworks.
Step 2: Define your axis anchors with concrete examples
Before scoring anything, get agreement on what the extremes of each axis mean in your context. Write down one or two competencies that are clearly strategic, one or two that are clearly tactical, one or two that are clearly internal, and one or two that are clearly external. These anchors calibrate all subsequent scoring. " Document these anchors visibly, on a shared screen or at the edges of a whiteboard, so every participant can reference them during scoring.
If the team disagrees on the anchors, resolve that before proceeding. Unresolved anchor disagreements will produce inconsistent placements across the entire map.
Tip: Choosing anchors that are not controversial accelerates alignment. Pick the most obviously extreme examples first, like 'product vision' for strategic and 'release checklist management' for tactical. Save debatable competencies for the scoring phase.
Step 3: Score each competency on the strategic-tactical axis
Take each competency from your list and assign it a score from 1 (purely tactical) to 10 (purely strategic). Score based on the competency's center of gravity in your organization, not its theoretical ideal. "Roadmapping" at a startup where the roadmap is a two-week lookahead might score a 4. At an enterprise company where roadmapping means 18-month market bets, it might score an 8.
Have each participant score independently before sharing, to avoid anchoring bias. Once individual scores are visible, discuss any competency where scores diverge by more than 3 points. The goal is not forced agreement. The goal is that every score has a stated rationale.
Record the consensus or average score for each competency.
Tip: When people struggle to score, ask: 'If a junior PM did this task, would it feel normal or would it feel like a stretch?' Tactical competencies feel appropriate for juniors. Strategic competencies feel like a stretch. This heuristic is imperfect but breaks logjams quickly.
Step 4: Score each competency on the internal-external axis
Repeat the scoring process for the horizontal axis. Assign each competency a score from 1 (purely internal, team-facing and org-facing) to 10 (purely external, market-facing and customer-facing). Apply the same principles: score independently first, discuss divergences, record consensus. Pay attention to competencies that feel ambiguous on this axis.
"Data analysis" might involve both internal reporting and external user behavior analysis. "Communication" might encompass both stakeholder updates and customer presentations. When a competency genuinely spans the axis, you have two options. Place it near the center (score of 5) with a note explaining the dual nature.
" Splitting is better when the skills involved are actually different. Centering is better when the underlying capability is the same regardless of audience.
Tip: If more than a third of your competencies land between 4 and 6 on this axis, your competency labels are probably too broad. Splitting 'communication' into 'executive alignment' and 'customer discovery interviewing' produces more actionable placement.
Step 5: Plot competencies onto the 2x2 grid
Create your grid. Draw two axes crossing at their midpoints. " Using the scores from Steps 3 and 4 as coordinates, place each competency on the grid. A competency scoring 8 on strategic and 3 on internal goes in the upper-left area.
A competency scoring 2 on strategic and 9 on external goes in the lower-right area. Use a consistent visual marker for each competency: a sticky note on a whiteboard, a labeled dot in a diagramming tool, or a row in a spreadsheet with X and Y columns. If two competencies land on nearly identical coordinates, offset them slightly so both remain visible, but note the clustering, which is itself an insight.
Tip: Color-code competencies by category if your list has natural groupings, like 'discovery skills' in blue and 'delivery skills' in green. The color patterns on the finished grid often reveal that entire skill categories cluster in one quadrant, which is a conversation starter.
Step 6: Identify quadrant concentrations and gaps
Step back and examine the distribution. Count how many competencies fall in each quadrant. A healthy, balanced competency model has representation in all four quadrants, though perfect equality is neither necessary nor common. Note which quadrant has the most competencies and which has the fewest.
If a quadrant is empty or has only one competency, that is a significant signal. It may mean your organization does not value that type of work, does not recognize it as a distinct skill, or has a genuine blind spot. Document these observations explicitly. ' This distribution summary is the single most important output of the mapping exercise because it drives every downstream decision.
Tip: An empty strategic-internal quadrant is the most common gap. Organizations readily list market-facing and execution skills but forget organizational leadership competencies like 'influencing without authority,' 'cross-team alignment,' and 'mentoring.' Check for this gap explicitly.
Step 7: Validate placements with role-based sanity checks
Test your map against real PM roles in your organization. Pick one junior PM and one senior PM. For the junior PM, check that the competencies expected of them cluster toward the tactical end of the axis. For the senior PM, check that their expected competencies extend into strategic territory.
If a competency you placed as highly strategic is actually a daily expectation for junior PMs in your company, the placement is likely wrong, or your expectation of juniors is unusual and worth examining. Similarly, pick one growth PM and one platform PM (or any two distinct role types). Their expected competency profiles should occupy different regions of the grid. If they do not, either the roles are not genuinely differentiated or your competency labels are too abstract to capture the real differences.
Tip: This sanity check often reveals that the team mapped competencies based on their ideal definitions rather than how the skills actually manifest in daily work. Adjust placements to match reality, not aspiration.
Step 8: Document the final map and rationale
Create a clean version of the map suitable for sharing beyond the immediate mapping team. Include the grid itself with all competencies plotted, a table listing each competency with its strategic-tactical score, internal-external score, and a one-sentence description of what the competency means in your context. Add a summary section with the key findings: quadrant distribution counts, notable clusters, identified gaps, and any competencies that generated significant debate during scoring. This document becomes the canonical reference for all downstream framework activities.
Store it where the team can access and update it. Date the document, because the map should be revisited at least annually as the organization's product challenges evolve.
Tip: Include the axis anchors and any split decisions in the documentation. Six months later, when someone questions why 'data analysis' is placed at (6, 7), the recorded rationale saves a full re-debate.
Examples
Example: Early-stage B2B SaaS startup with 2 PMs
A 30-person B2B SaaS startup selling project management software has two PMs and no formal competency model. The VP of Product wants to differentiate the two PM roles and build a development plan. They have 45 minutes and a whiteboard.
The VP lists 14 competencies from recent job descriptions and performance conversations: customer discovery interviewing, competitive analysis, sprint planning, backlog grooming, pricing strategy, stakeholder reporting, feature spec writing, user story mapping, product vision articulation, sales enablement, release management, analytics setup, roadmap prioritization, and onboarding flow design. They anchor strategic with 'product vision articulation' (10, meaning purely strategic) and tactical with 'release management' (2). They anchor external with 'customer discovery interviewing' (9) and internal with 'sprint planning' (2). Scoring produces clear patterns.
Nine competencies cluster in the tactical half. Only three sit in the strategic half: product vision articulation (9, 6), pricing strategy (8, 8), and roadmap prioritization (7, 4). The external-tactical quadrant has five competencies, including customer discovery, competitive analysis, sales enablement, onboarding flow design, and analytics setup. The strategic-internal quadrant is completely empty.
The VP realizes neither PM is being asked to do organizational influence work, long-term planning, or team building. They add 'cross-functional alignment' (7, 3) and 'technical architecture input' (6, 2) to fill the gap. The final map makes the role differentiation obvious: one PM should own the external-heavy competencies (customer-facing, market-facing), the other should own internal-heavy competencies (process, engineering collaboration), and both need to stretch into the strategic half as the team grows.
Example: Enterprise product organization with 15 PMs across three squads
A mid-size enterprise company with 15 PMs organized into three squads (Growth, Platform, Core Product) wants to standardize PM expectations. The Head of Product facilitates a mapping workshop with the three squad leads. They have 90 minutes and use a shared spreadsheet.
The four participants brainstorm 22 competencies, then merge duplicates down to 18. They score independently using a shared Google Sheet where each person has a hidden column. After revealing scores, they find strong consensus on most competencies (within 2 points). Four competencies show divergence greater than 3 points: 'data analysis' (one lead scores it 8 strategic because they use data for annual planning, another scores it 3 because their team uses it for A/B test analysis), 'stakeholder management' (scores range from 5 to 9 on the internal-external axis, because the Growth lead's stakeholders are external partners while the Platform lead's are internal engineering teams), 'technical depth' (disagreement on whether it is strategic or tactical), and 'experimentation design' (disagreement on whether it is internal process or external-facing).
They split 'data analysis' into 'strategic analytics and insights' (8, 5) and 'experiment analysis and reporting' (3, 6). They keep 'stakeholder management' as a single item at (6, 4) but add a note that its internal-external position varies by squad. After plotting, the map reveals the organization's competency model is strongest in the tactical-internal quadrant (7 competencies) and weakest in the strategic-external quadrant (2 competencies). This matches the Head of Product's intuition that the team is execution-heavy but underdeveloped in market strategy.
The map becomes the basis for squad-specific competency profiles, where Growth PMs need stronger external skills and Platform PMs need stronger internal skills.
Example: Solo PM at a B2C consumer app doing self-assessment
A solo PM at a 50-person consumer mobile app company wants to identify personal development priorities. They have no formal framework and no other PMs to calibrate with. They do the exercise alone using a slide deck over a lunch break.
The PM lists 15 competencies based on their actual job activities over the past quarter: user research, A/B testing, push notification strategy, app store optimization, feature prioritization, bug triage, design collaboration, analytics dashboard building, competitor benchmarking, retention analysis, sprint facilitation, launch coordination, executive updates, pricing and monetization, and community feedback management. They score each competency on both axes. ' for the internal-external axis. The completed map shows a heavy concentration in the tactical-external quadrant (8 competencies), reflecting the PM's daily focus on user-facing execution.
The strategic-internal quadrant has zero competencies. The PM realizes they never practice organizational influence, long-term planning, or mentoring, not because those are unimportant but because as a solo PM they have been heads-down on delivery. They add 'product vision and strategy' and 'cross-functional roadmap alignment' to the grid as aspirational competencies they need to develop to grow into a senior role. They share the map with their manager as the basis for a development conversation, using the quadrant gaps to justify specific stretch assignments.
Example: Large organization calibrating across global offices
A global product organization with 40 PMs across four offices (New York, London, Singapore, Sao Paulo) wants a unified competency map. The VP of Product runs asynchronous scoring over one week using a survey tool, then hosts a 60-minute alignment call.
The VP starts with the company's existing 20-competency list from the career ladder. They distribute a survey asking each PM to score all 20 competencies on both axes. They receive 34 responses. 5 on both axes).
Four competencies have high variance: 'market research' (the Singapore team scores it as highly strategic because they do market entry analysis, the New York team scores it as tactical because they do feature-level surveys), 'regulatory compliance' (London places it as strategic-external, New York sees it as tactical-internal), 'partner management' (varies by whether the office has partner-facing PMs), and 'team leadership' (senior PMs rate it strategic, junior PMs rate it tactical). On the alignment call, the VP addresses each high-variance competency. They decide to split 'market research' into 'market entry and sizing' (strategic-external) and 'feature validation research' (tactical-external). They keep 'regulatory compliance' as one item but note it sits in different quadrants depending on the PM's seniority and market.
The final map, with 22 competencies, becomes the global standard. Each regional office overlays their team's actual strengths on the map to identify local development priorities, producing four different gap analysis views from one shared grid.
Best Practices
Score each axis independently and in separate passes. When you try to place competencies on both dimensions simultaneously, people unconsciously create pleasing spatial patterns rather than accurate placements. Score the full list on the strategic-tactical axis first, take a break, then score the full list on the internal-external axis. This separation produces more honest results.
Use continuous scoring (1-10) rather than forcing competencies into four binary quadrants. A competency at (6, 4) is meaningfully different from one at (9, 1), even though both nominally sit in the 'strategic-internal' quadrant. Continuous placement preserves nuance that binary classification destroys, and that nuance matters for role differentiation and gap analysis.
Include at least two perspectives beyond product management when scoring. Engineering leads, designers, and business stakeholders see PM competencies differently. A skill that PMs consider strategic might look tactical to an executive. These perspective differences are valuable data, not noise. If only PMs do the scoring, the map will reflect PM self-image rather than organizational reality.
Revisit and update the map quarterly for the first year, then annually thereafter. Competency importance shifts as organizations grow. A startup's map is heavily weighted toward external-tactical skills like customer discovery and rapid shipping. As the company matures, internal-strategic skills like organizational design and portfolio management gain importance.
A stale map produces stale development plans.
Keep the competency list between 12 and 20 items. Fewer than 12 competencies creates a sparse map where quadrant analysis is unreliable because one competency moving changes the entire distribution. More than 20 creates clutter and scoring fatigue, which reduces accuracy on later items. If your brainstorm produces 30 items, merge related skills or identify which are sub-skills of a parent competency.
Distinguish between 'competency center of gravity' and 'competency range.' A competency like 'roadmapping' has a center of gravity (maybe strategic at 7) but also a range (it extends down to tactical at 4 in daily practice). Plot the center of gravity, but annotate range when it matters. This prevents arguments where both sides are right because they are describing different expressions of the same skill.
Never rank quadrants as better or worse. The moment your map implies that strategic-external is 'senior' and tactical-internal is 'junior,' people will game their self-assessments and avoid tactical skills. The grid is descriptive. All four quadrants contain essential work. Make this explicit in any presentation of the map.
Common Mistakes
Using vague competency labels that span multiple quadrants
Correction
Labels like 'leadership,' 'communication,' or 'analytical skills' are too broad to place meaningfully. They describe bundles of distinct capabilities that actually sit in different quadrants. 'Leadership' includes 'team mentoring' (tactical-internal), 'product vision setting' (strategic-external), and 'executive influence' (strategic-internal). When you cannot place a competency confidently, it is a signal to split it into more specific labels.
The test is simple: can two reasonable people independently place this label within 2 points of each other on both axes? If not, the label is too vague.
Mapping based on aspirational definitions rather than actual organizational practice
Correction
Teams frequently place 'user research' as highly strategic because they believe research should inform product vision. But in their actual organization, user research is used to validate specific feature ideas at the sprint level, which is tactical-external work. Map competencies as they are practiced today, not as you wish they were practiced. The gap between aspiration and reality is itself a useful insight, but only if the map reflects reality first.
' If the answer describes tactical output, score it tactically regardless of its theoretical strategic potential.
Letting one vocal participant anchor all the scores
Correction
In group scoring sessions, the first person to speak sets an anchor that biases subsequent responses. This is a well-documented cognitive bias, and it compresses score variance, making the map look more uniform than it actually is. The fix is structural: have every participant write their scores privately before any discussion. Use silent scoring on sticky notes, a shared spreadsheet with hidden columns, or anonymous polling.
Only reveal and discuss after everyone has committed. Divergent scores are the most valuable inputs because they surface genuine differences in how the organization thinks about a competency.
Creating the map once and treating it as permanent
Correction
A competency map reflects a moment in time. As the product matures, the market shifts, and the team grows, the relative importance and nature of competencies change. 'Customer acquisition' might start as tactical-external (running landing page experiments) and evolve into strategic-external (defining market entry strategy for new segments). Teams that treat the map as permanent make development decisions based on outdated organizational context.
Schedule a map review at the same cadence as your strategic planning cycle, and look specifically for competencies that have drifted on either axis.
Overcrowding one quadrant and leaving another empty without investigating why
Correction
When 60% of competencies cluster in one quadrant, most teams shrug and move on. This is a missed opportunity. The clustering pattern is the map's most important finding. An overcrowded tactical-internal quadrant means your competency model describes process management in great detail but barely acknowledges market-facing skills.
An empty strategic-internal quadrant means no one is being evaluated on organizational influence or long-term team building. ' Often the answer is yes, and the map improves significantly.
Confusing the mapping exercise with performance assessment
Correction
Mapping decides where competencies sit on the grid. Assessment decides how well individuals perform each competency. These are separate activities with different goals and different emotional stakes. When mapping and assessment happen simultaneously, people advocate for placing competencies in quadrants where they personally excel, distorting the map to serve self-interest.
Complete the mapping exercise first and gain consensus on the grid before anyone is asked to rate themselves or others against it. This separation is especially important if the mapping group includes people who will later be assessed.
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.
Assessing Product Team Strengths and Identifying Skill Gaps
How to use the competency framework to evaluate individual and team-level proficiency, surface blind spots, and prioritize areas for development.
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.
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 many competencies should I include on the grid?
Target 12 to 20 competencies for the most useful map. Fewer than 12 makes the grid too sparse to reveal meaningful patterns, because one competency moving changes the quadrant distribution significantly. More than 20 creates scoring fatigue and visual clutter that makes the map hard to read and discuss. If your brainstorm produces 25-30 items, look for competencies that are sub-skills of a broader capability and merge them, or identify items that are really the same skill applied in different contexts.
Should I map competencies before or after defining PM levels?
Map first, then define levels. The mapping exercise determines what your competency landscape looks like and where gaps exist. Level definitions then specify how much of each competency a PM at each level should demonstrate. If you define levels first, you are building expectations on a competency list that has not been validated for coverage or placement. The map also makes level differentiation easier because you can describe junior PMs as owning tactical-quadrant competencies and senior PMs as owning strategic-quadrant competencies, with specific skills to point to. See [defining competency levels](/skills/defining-competency-levels-from-associate-to-senior-pm) for the follow-on exercise.
What do I do when a competency genuinely belongs in two quadrants?
You have two options: place it at the center of gravity (the position that best reflects how the competency is most commonly practiced in your organization), or split it into two distinct competencies with different names. Split when the underlying skills are actually different. 'Communication' should almost always be split, because writing a product spec (tactical-internal) and presenting a market opportunity to the board (strategic-internal) are fundamentally different capabilities. Center when the capability is consistent but the audience varies, like 'data analysis' that uses the same analytical rigor whether the audience is internal or external.
How do I handle disagreements about where a competency belongs?
Disagreements are the exercise's most valuable output, not a problem to suppress. When two people disagree by more than 3 points on an axis, ask each to describe the last time they saw the competency in action and what the PM was actually doing. Usually the disagreement stems from different mental examples: one person is thinking of strategic roadmap conversations while the other is thinking of sprint-level prioritization, and both are calling it 'prioritization.' The fix is almost always to make the competency label more specific. Document the disagreement and resolution, because it reveals important differences in how the organization thinks about PM work.
Can I use this mapping for non-PM roles like product designers or engineering managers?
Yes, the two-dimensional grid works for any role where work spans strategic-tactical and internal-external dimensions. Product designers, engineering managers, and even marketing managers all face these tensions. However, the axis anchors and competency lists must be customized. What counts as 'strategic' for a designer (design system architecture, brand direction) is different from what counts as 'strategic' for a PM (product vision, market positioning). Do not reuse a PM competency map for other roles. Run a fresh mapping exercise with role-appropriate competencies and anchors.
How often should I redo the mapping exercise?
Review the map quarterly during the first year after creation, then annually. The first year has the highest rate of corrections because you discover placements that do not match reality. After the map stabilizes, annual reviews aligned with strategic planning are sufficient. Trigger an out-of-cycle review if the company undergoes a major shift: new product line, significant org restructure, pivot in target market, or major change in team size. Each of these changes can move multiple competencies on the grid.
Why does my map keep showing everything clustered in one quadrant?
Clustering usually has one of three causes. First, your competency labels may be too specific in one area and too vague in another. If you have five variants of 'execution' skills but only one label for all 'strategy' work, the map will skew tactical. Audit your list for granularity consistency. Second, you may genuinely have a one-dimensional competency model that only values a certain type of PM work, which is a real finding worth acting on. Third, your scoring anchors may be off, compressing the axis range. If your most strategic anchor is only moderately strategic (like 'quarterly planning'), then truly strategic competencies have nowhere to go. Reset anchors to genuine extremes and rescore.