the pm competency model

You have just walked out of a performance review. Your manager said: “You’re great at execution, but you need to be more strategic.” You nodded. You smiled. And now you are sitting at your desk wondering what the hell that means.

Does “be more strategic” mean you should think about the market more? Talk to customers less? Write longer documents? Attend more leadership meetings? Say “vision” in sentences?

This is the problem with PM feedback. It is almost always vague because the person giving it does not have a shared model of what PM competency actually looks like. Neither do you. So the feedback floats — well-meaning but unactionable.

I have trained over 10,000 PMs across India and Southeast Asia. The single highest-impact thing I have seen accelerate PM careers is not a framework or a tool. It is a competency model — a shared language for what good looks like at each level, so that feedback becomes specific and growth becomes directed.

Why most competency models fail

The industry has no shortage of PM competency frameworks. The 280 Group surveys 15 skill dimensions. Sequent Learning Networks has a six-cluster acumen model. Exponent breaks it into four major skill sets. Google has its internal rubric. Ravi Mehta published a well-known 12-competency model.

The problem is not a lack of models. The problem is that most of these models are built for HR departments, not for working PMs.

They have too many dimensions (15? 12? nobody self-assesses against 15 dimensions). They are flat — they do not tell you which competencies matter more at which career stage. And they assume a Western big-tech context that does not map to a 30-person Indian startup where the PM is also doing pre-sales, customer support, and vendor management.

What follows is a model I have refined over six years of training PMs. Seven competencies. Not 15. Not 12. Seven — because that is the most a human being can track and develop simultaneously.

The seven competencies

   EXECUTION              SENSE                  INFLUENCE
 ─────────              ─────                  ─────────
 ┌──────────────┐       ┌──────────────┐       ┌──────────────┐
 │ delivery     │       │ product      │       │ stakeholder  │
 │ experimentation│     │ sense        │       │ management   │
 │ user stories │       │              │       │              │
 └──────────────┘       └──────────────┘       └──────────────┘

               ╲             ╱
                ╲    STRATEGY ╱
                 ╲  ─────────╱
                  ┌──────────┐
                  │ vision   │
                  │ pricing  │
                  └──────────┘

 → apm focuses on execution
 → pm bridges execution + sense
 → senior pm holds sense + influence + early strategy
 → gpm+ is mostly strategy + influence

Here are the seven competencies, grouped into three layers:

Layer 1: Foundation (required at every level)

1. Execution The ability to ship. Scoping work, writing clear specs, coordinating across engineering/design/QA, managing timelines, unblocking the team. This is where every PM starts. It is necessary but not sufficient — you cannot be promoted on execution alone past PM2.

2. Communication Translating between audiences — writing specs engineers trust, presenting to leadership without jargon, running meetings that produce decisions, writing crisp Slack messages that do not require three follow-up threads. In India specifically, this includes navigating hierarchical communication norms while still driving clarity.

Layer 2: Craft (the differentiators)

3. Product Sense The instinct for what makes a good product. Spotting friction before users report it. Knowing when a feature is solving the wrong problem. Understanding second-order effects of design decisions. This is the competency that separates PMs who ship features from PMs who ship outcomes.

4. Analytical Rigor Defining the right metrics, interpreting data honestly (including when it contradicts your hypothesis), running experiments correctly, and making quantitative arguments. Not “being good with numbers” — being disciplined about what the numbers mean and what they do not mean.

5. User Understanding Going beyond personas and survey data to develop genuine empathy for user behavior. Conducting research that surfaces real needs, not confirmation of existing assumptions. In India, this means understanding extreme diversity in digital literacy, connectivity, and price sensitivity across the same product’s user base.

Layer 3: Leadership (what makes you senior, then director)

6. Strategic Thinking Connecting product decisions to business outcomes. Understanding competitive dynamics, market timing, and where the company should (and should not) play. This is the competency your manager means when they say “be more strategic.” It is not about writing strategy documents — it is about making product choices that reflect an understanding of the business.

7. Influence Getting things done without authority. Aligning stakeholders who disagree. Building coalitions across teams. Navigating organizational politics without becoming political. At senior levels, this becomes the primary competency — you spend more time aligning people than writing specs.

How competencies shift with career stage

This is the part most models get wrong. They present competencies as a flat list, implying all seven matter equally at every level. They do not.

At each career stage, there is a primary competency (the one you are evaluated on most), a growth edge (the one you should be actively developing), and table stakes (the ones that should already be solid).

The critical transition is PM to Senior PM. This is where most PMs get stuck. They have been rewarded for execution for 2-3 years. They are the most reliable shipper on the team. And then they hit a ceiling because the next level requires product sense and strategic thinking — competencies they were never evaluated on and may never have developed.

The self-assessment rubric

For each competency, rate yourself from 1 to 4. Be honest — this is for you, not for HR.

Now score yourself:

The evidence column is the important part. If you cannot point to a specific recent example that demonstrates your score, lower it by one. PMs are consistently 0.5 to 1 point too generous in self-assessment. The Dunning-Kruger effect hits product management especially hard because PM work is ambiguous enough that you can convince yourself you are doing well without clear evidence.

What the scores tell you

All 2s and 3s: You are a solid PM who has not specialized. This is normal at the PM level. Pick one Layer 2 competency and drive it to a 4.

High execution, low product sense: You are the reliable shipper who is about to hit a ceiling. You need to spend less time in Jira and more time with users and data.

High product sense, low execution: You have strong opinions but teams do not trust you to deliver. Your ideas die in committee because you have not earned credibility through shipping.

High strategy, low influence: You see the right direction but cannot get people to follow. This is common with PMs who came from consulting — they are trained to produce recommendations, not to build alignment.

Low across the board: You are early in your career, or you are in the wrong role. Both are fixable. The first requires patience and deliberate practice. The second requires honesty.

The India-specific competency wrinkle

In India, there is an eighth dimension that does not appear in Western competency models: context-switching across scale extremes.

An Indian PM might be building for a Jio user on a Rs 6,000 smartphone with patchy 4G and a first-generation WhatsApp user at the same time as an enterprise buyer at a Mumbai bank who expects SAP-level configuration. The same product, two radically different users.

This is not “user understanding” — it is a form of cognitive flexibility that Western PM models do not account for. The best Indian PMs I have seen develop an almost physical instinct for which user they are designing for at any given moment. They can switch between “optimize for 100ms load time on 3G” and “support complex role-based access controls” in the same sprint.

If you work in India, add this to your self-assessment. It is real, it is hard, and it is a competitive advantage that PMs from more homogeneous markets do not have.

Turning feedback into action

The competency model is only useful if it changes how you give and receive feedback. Here is how to use it in your next review cycle.

When receiving feedback: If your manager says “be more strategic,” translate it: “Which specific competency are you pointing to — strategic thinking, product sense, or influence? Can you give me a recent example where you saw the gap?” Force the conversation into competency-specific language.

When giving feedback (to your reports or peers): Never say “you need to improve.” Say “Your execution is a 3 — strong and reliable. Your analytical rigor is a 2 — I noticed in the payments feature launch that we did not define success metrics upfront. Let’s work on that.”

When negotiating promotions: Map the next level’s primary competency. Show evidence you are already operating at that level. “The Senior PM role requires product sense as a primary competency. Here are three times this quarter where I identified the wrong problem being solved and redirected the team.”

Where to go next

Your competency profile should now tell you where to focus. Follow the signal:

• If product sense is your gap, start with Product Thinking — that is where we build the muscle.
• If execution needs work, the Writing PRDs and Sprint Planning sections cover the mechanics.
• If strategic thinking is the growth edge, Product Vision & Strategy breaks down how to develop it without an MBA.
• If user understanding scored low, go to User Research Methods and start doing the work — no PM ever developed user empathy from reading about it.
• If influence is the bottleneck, Stakeholder Management covers the mechanics of alignment without authority.

Do not read all of them. Read the one that matches your gap. Then practice it for 90 days before reassessing.