The Product Manager’s Atlas
Introduction

The PM Competency Model

3 min readΒ·563 words
introductioncompetency-modelframeworkmoc

This is the spine of the whole Atlas. Over years of leveling and coaching PMs, I converged on a model with four competency areas, each holding three competencies, for twelve in total. It is adapted from the Reforge and Ravi Mehta "Peak Product Manager" model, which is the closest thing our field has to a complete definition of the job. What I have added is the part that makes it usable day to day: a verbatim set of behaviors under each competency, a career ladder mapped to it, and a leveling system that actually gates promotions (Score-Gated Leveling).

#The four areas and twelve competencies

AreaWhat it meansThe three competencies
Product ExecutionDefine, build, and launch exceptional productsFeature Specification Β· Product Delivery Β· Product Quality
Customer InsightUnderstand and fulfill customer needsFluency with Data Β· Voice of the Customer Β· User Experience Design
Product StrategyDeliver business impact via product innovationBusiness Outcome Ownership Β· Strategic Impact Β· Product Vision and Roadmapping
Influencing PeopleRally people around the team's workStakeholder Management Β· Team Leadership Β· Managing Up

There is a rough arc here. Execution is where most careers start, and strategy and influence are where they mature. Treat that as a center of gravity, not a rule. Which brings me to the most important idea in the model.

#You are spiky, not well-rounded

✦Know your shape

Almost nobody is strong across all twelve, and you do not need to be. The best PMs I have worked with are spiky. They are exceptional at three or four competencies and competent at the rest, and they win by knowing their shape and building teams that fill the gaps. Chasing a flat, uniformly "high" profile is a good way to end up mediocre at everything. More in The T-Shaped PM and Knowing Your Shape.

#Levels: the same competencies, a higher bar

The twelve competencies do not change as you climb. The altitude does. I map progress on a six-stage mastery spine, running from Gaining Experience to Recognized Thought Leader, detailed in The Six Stages of Mastery. The same skill, say Feature Specification, means "writes a clear spec for one feature with help" at the APM level and "improves the spec process for every team" at the VP level. The full progression lives in The Product Career Ladder, and the at-a-glance grid in The Master Competency Matrix.

#Where this model is thin (and how I patch it)

I would rather be honest than dogmatic about this. A clean 4x12 grid under-weights a few things, so I treat these as first-class even though they do not sit neatly in one box: discovery as its own discipline (Continuous Discovery, The Four Big Product Risks), product sense (Product Sense and Judgment), technical and GTM fluency, and, loudest of all right now, the way AI is rewriting which competencies even matter (Competencies AI Commoditizes vs Elevates).

#Continue Reading