The Master Competency Matrix
This is the keystone of the Atlas: every one of the 4 areas and 12 competencies from The PM Competency Model, with a row per competency and a column per level, summarizing what good looks like at each rung. It's the single-page version of the model, and it's the grid I actually use to level and coach.
Levels run APM → PM → Senior → Staff/Principal → VP. The skill never changes; the altitude does, meaning scope, autonomy, ambiguity, and influence (see What Changes at Each Level). Read across a row to see a single competency escalate; read down a column to see what a level demands across the board. Nobody is uniformly high across all twelve. You're spiky, and that's the design.
The escalation follows one pattern across all twelve: self/feature scope → multi-feature and trade-off mastery → team ownership → cross-team and company influence → org culture-building. Roughly, an APM does it for a feature with manager support; a PM does it independently for complex work and influences the team's roadmap; a Senior owns team outcomes and coaches; a Staff/Principal drives strategy and reallocates investment; a VP builds the culture and the company-wide process. The scoring rubric underneath each cell is simple: 2+ Outperform · 1 to 1.5 On Track · 0 to 0.5 Needs Focus (see The Proficiency Scale).
#Area 1: Product Execution
Define, build, and launch exceptional products.
| Competency | APM | PM | Senior | Staff/Principal | VP |
|---|---|---|---|---|---|
| Feature Specification | Writes a clear spec for a minor feature; contributes to major ones; defines an achievable goal. | Specs major, complex functionality independently; finds the right level of detail; uses comps and prototypes. | Sequences multiple interrelated specs; considers all devices and points of sale; estimates effort into requirements. | Reviews the team's specs and coaches to clarity; improves the spec process itself. | Owns continuous improvement of how the whole org writes and reviews specs. |
| Product Delivery | Coordinates with the immediate team on a feature; communicates clearly; delivers small scope to plan. | Drives delivery of complex work independently; involves design/eng/business early; minimal surprises. | Coordinates across interdependent teams; explains trade-offs; protects the schedule under pressure. | Improves delivery practices for the team; unblocks systemic delivery issues; models the bar. | Builds the company's delivery operating rhythm and cadence. |
| Product Quality | Identifies and reports quality issues; resolves simple ones; learns the standard. | Owns quality for a complex feature across devices/use cases; classifies and prioritizes issues. | Sets the quality bar for the team's area; balances decisions on impact vs effort. | Coaches quality judgment; raises the definition of good across teams. | Owns the org's quality philosophy and the systems that enforce it. |
#Area 2: Customer Insight
Understand and fulfill customer needs.
| Competency | APM | PM | Senior | Staff/Principal | VP |
|---|---|---|---|---|---|
| Fluency with Data | Pulls and reads basic metrics; runs simple analyses with help. See Product Analytics and Metrics. | Designs and reads A/B tests with valid sample sizes; turns data into actions. | Connects metrics to business outcomes across an area; spots causation vs correlation. | Coaches analytical rigor; builds the team's measurement discipline. | Sets how the org instruments, measures, and learns. |
| Voice of the Customer | Sits in on research; captures feedback; learns the personas. See User Research and Discovery. | Runs discovery for a complex area; translates research into improvements. | Shapes strategy from synthesized insight across the area; advocates user needs in prioritization. | Builds the team's discovery habit and research standard. | Embeds customer-centricity as org culture. |
| User Experience Design | Gives basic design feedback; learns the product's UX patterns. See Design Sense and Critique. | Partners with design on complex flows; balances usability, feasibility, impact. | Drives UX coherence across an area; champions simplicity and consistency. | Elevates the team's design judgment; sets UX standards. | Owns the org's design bar and craft culture. |
#Area 3: Product Strategy
Deliver business impact via product innovation.
| Competency | APM | PM | Senior | Staff/Principal | VP |
|---|---|---|---|---|---|
| Business Outcome Ownership | Connects a feature to a goal; tracks whether it moved. | Owns outcomes for a complex initiative; root-causes shortfalls and adjusts. | Owns the team's outcomes; reallocates effort toward leverage. | Owns outcomes across multiple teams; drives the outcome culture. | Owns a P&L-scale set of outcomes for the org. |
| Strategic Impact | Understands the team's strategy; executes against it. | Contributes to the area's strategy; frames work in business terms. See The DHM Model. | Defines strategy for the area; synthesizes market/user/competitive inputs. | Sets cross-team strategy; influences company direction. | Sets and owns company product strategy. |
| Product Vision and Roadmapping | Maintains a feature-level roadmap; prioritizes with help. See RICE and Scoring Models. | Builds and manages an outcome-focused roadmap for a complex area. | Defines a vision for the area and a prioritized multi-quarter roadmap. | Drives portfolio-level vision; reallocates investment across teams. | Owns and evangelizes the company-wide product vision. |
#Area 4: Influencing People
Rally people around the team's work.
| Competency | APM | PM | Senior | Staff/Principal | VP |
|---|---|---|---|---|---|
| Stakeholder Management | Identifies stakeholders for a feature; keeps them informed. | Manages stakeholders for a complex area; resolves conflict with empathy. See Internal and External Stakeholders. | Aligns senior stakeholders across an area; manages external partners credibly. | Aligns cross-team and exec stakeholders; sets the comms standard. | Manages company-level and external/market stakeholders. |
| Team Leadership | Not applicable; no reports, so leads through example. | Begins informal leadership; mentors juniors; influences the team's roadmap. | Coaches peers and reports; owns team accountability for outcomes. See Coaching and Feedback. | Drives product-wide influence; improves processes, hiring, and standards. See Hiring and Building a Product Team. | Builds the product culture; develops leaders; owns org design. |
| Managing Up | Keeps their manager informed; asks for help well. | Uses senior managers to unblock; frames asks in business terms. | Influences exec direction for the area; navigates competing interests. See Executive Communication. | Shapes company strategy through exec relationships; builds exec trust. | Operates as the executive; sets the context others manage up to. |
In the source model, Team Leadership is "Not applicable" at the APM level, because you can't manage and mentor reports you don't have. It begins informally at PM (mentoring, roadmap influence) and only becomes a load-bearing competency from Senior up. This is one reason a "title is not a level" (see Myths and Misconceptions).
#Using the matrix to assess and grow
This grid is a map, not a verdict. To turn it into action:
- Score yourself down the rows with The Competency Self-Assessment and the The Proficiency Scale.
- Find your shape, the three or four spikes and the gaps (Identifying Growth Areas).
- Build a plan against the lowest few, not the highest (Building a Growth Plan).
- Calibrate honestly, because leveling is evidence-based, not vibes (Score-Gated Leveling, Calibration and Promotion).
#Continue Reading
- The PM Competency Model for the full prose model this grid compresses.
- Competency Quick Reference by Level for the same levels summarized by scope, autonomy, ambiguity, and influence.
- What Changes at Each Level for the four dials that drive every escalation in this table.
- The Six Stages of Mastery for the progression engine under each cell.
- The Competency Self-Assessment for how to score yourself against these rows.