The 12 Product Management Competencies
Map every PM skill into four areas — execution, customer insight, product strategy, influence — and 12 competencies that hold from APM to CPO.
- Difficulty
- Easy
- Time to result
- ~ongoing to results
- Steps
- 4
- Confidence
- 92%
A competency model that defines the PM role as 12 sub-skills across four areas: product execution, customer insight, product strategy, and leadership/influence. The 12 competencies stay constant across seniority; what changes is the altitude at which you apply them — an APM executes personally, a CPO builds the systems that let teams execute.
Origin
Built by Ravi Mehta and the head of product at TripAdvisor to support a product rotational program that hired people with no prior PM experience and grew them into senior PMs through four six-month rotations. It's the writing of his that podcast host Lenny Rachitsky says he has shared most.
Core principles
- 01The 12 competencies are the same for an APM as for a CPO; only the altitude of application changes.
- 02Move from thinking about product as shipping features to driving business outcomes.
- 03User experience design is broader than UI — for an API product the experience is the API spec.
- 04Self-scoring each competency 'needs focus / on track / outperforming' surfaces where you and your manager disagree.
How to run it
- 1
Master product execution
Build the foundation: functional specification (defining the PRD), product delivery (turning specs into working product with eng and design), and product quality (technical, design, usability, and business quality).
- 2
Develop customer insight
Understand who to build for: fluency with data (using data at your fingertips to decide what customers need), voice of the customer (advocating for the customer across the company), and user experience design.
Pro tip Treat user experience design broadly — for ML products your 'experience' may be the training models; for APIs it's the spec.
- 3
Grow product strategy
Connect work to the business: owning business outcomes (not just shipping features), product vision and roadmapping, and strategic impact (a sequence of business outcomes that moves the strategy forward).
- 4
Build leadership and influence
Influence people: stakeholder inclusion (rallying the organization around your work), team leadership (developing direct reports, once you have them), and managing up (winning leadership's support).
Pro tip Team leadership only activates once you have direct reports — don't over-index on it before then.
In the wild
A newly-public TripAdvisor needed to grow its product team fast, but hiring an experienced PM in Boston took three to six months. Instead they hired directly out of business school and undergrad, regardless of prior product experience, and ran them through four six-month rotations across zero-to-one, growth, and infrastructure teams. The 12-competency framework was built to define the role clearly and give recruits a concrete growth plan.
→ In roughly two years, people with no product background came out equipped to be senior, effective product managers.
Common mistakes
Thinking about product as shipping features
The 'own business outcomes' competency exists because PMs default to measuring themselves by features shipped. The skill is understanding how your product plugs into and drives value for the business, then sequencing outcomes that move the strategy.
Confusing seniority with only operating at high altitude
PMs assume becoming senior means never touching tactics. In reality a CPO still zooms into details like button text; the shift is expanding dynamic range — moving fluidly between strategy and specifics — not abandoning the low end.
Is it for you?
Best for
PMs mapping their own growth, and leaders designing PM career ladders or evaluation rubrics.
Not ideal for
Non-product roles or very early founders who don't yet need a formal skills taxonomy.
From the transcript
“the framework consists of 12 competencies in four different areas”
“these competencies I think are the same for apms as they are for cpos”
“the first thing that's really important is product execution”
“it's really important to move away from thinking about product as shipping features to driving business outcomes”
From the episode
Building your product strategy stack
Ravi Mehta (Tinder, Facebook, Tripadvisor, Outpace)