deliberate skill building
Auditing your skills is super important. Find your hip pocket skill, build on it, become really good at this one thing that becomes your superpower. But pick those one or two things that you go really, really deep on.
Most PMs treat their own development the way they would never treat their product — reactively, without measurement, and with no clear hypothesis about what will move the needle.
They read blog posts when they feel insecure. They take a course when their manager suggests it. They attend conferences when their company pays. None of this is skill building. It is career tourism.
Deliberate skill building is different. It is the same discipline you apply to product development — gap analysis, hypothesis, focused investment, measurement — applied to yourself. I have watched over 10,000 PMs go through this process at Pragmatic Leaders. The ones who grew fastest were not the ones who consumed the most content. They were the ones who identified their specific gaps and closed them through structured practice.
The skill audit nobody does
Here is the uncomfortable truth: most PMs cannot accurately assess their own skill level.
Annual review at a mid-stage fintech company in Gurgaon. A PM with three years of experience is meeting their director.
Nisha (PM, 3 years): “I think my main development area is probably strategy. I want to get more exposure to strategic thinking.”
Director of Product: “Nisha, you have written three solid strategy docs this year. Strategy is actually one of your strengths. Where I see the gap is in your user research. You have not run a single user interview in six months.”
Nisha (PM, 3 years): “But I read the research reports that the UX team shares...”
Director of Product: “Reading reports is consuming research. Running interviews is practising empathy. They are completely different skills.”
Nisha had self-assessed based on what she found interesting (strategy) rather than what she was actually weak at (direct user contact). This is the norm, not the exception.
Self-assessment is unreliable. The skills you want to develop and the skills you need to develop are usually different.
The reason PMs get this wrong is predictable. We overweight the skills we enjoy and underweight the skills we avoid. If you hate running user interviews, you will find every excuse not to — and then tell yourself the gap is somewhere else.
A real skill audit requires external input. Here is how to do it:
Step 1: Map the six PM skill domains. These are not arbitrary. Every PM competency model converges on roughly the same categories:
| Domain | What it covers | How to spot weakness |
|---|---|---|
| Discovery & Research | User interviews, market research, Jobs to Be Done, competitive analysis | You rely on second-hand research. You have not talked to a user in the last month. |
| Strategy & Vision | Product vision, roadmap rationale, prioritisation, market positioning | Your roadmap is a feature list. You cannot explain why Q2 matters differently from Q3. |
| Execution & Delivery | PRDs, sprint planning, working with engineering, managing scope | You miss deadlines. Engineers complain about ambiguous specs. Scope creeps every sprint. |
| Analytics & Data | Metrics definition, data interpretation, experimentation, SQL | You cannot answer “how is your product doing?” without asking the data team first. |
| Communication & Influence | Stakeholder management, presentations, writing, negotiation | Your proposals get stuck in review. You struggle to get buy-in from senior leadership. |
| Design & User Experience | UX principles, wireframing, accessibility, working with designers | Your specs lack user flows. Designers frequently push back on your feature definitions. |
Step 2: Rate yourself honestly on each domain. Use a 1-5 scale: 1 = I avoid this, 2 = I do it poorly, 3 = I am adequate, 4 = I am strong, 5 = this is my superpower.
Step 3: Get three external ratings. Ask your manager, one engineering partner, and one cross-functional peer (designer, data analyst, or marketer) to rate you on the same six domains. Do not argue with their ratings. The delta between your self-rating and the average external rating is your blind spot map.
Step 4: Pick two gaps. Not six. You cannot improve everything at once. Pick the two domains where the external rating is lowest — not the two you find most interesting.
The hip pocket skill
Before you fix your weaknesses, understand your strength.
A Google PM on one of our sessions coined the term “hip pocket skill” — the one thing you are so good at that you can pull it out in any situation and add value. For some PMs, it is data analysis. For others, it is user empathy. For a few, it is the ability to synthesize chaos into a clear narrative.
Your hip pocket skill is your career anchor. It is what makes you memorable in a room, what earns you trust fast in a new team, and what you should never stop investing in even while you close gaps elsewhere.
The mistake is going all-in on weaknesses and letting your strength atrophy. The right ratio is roughly 70-30: 70% of your development time on closing gaps, 30% on deepening your superpower.
This is the insight most development plans miss. You do not fix weaknesses by reading about them. You fix them by doing real work that forces you to exercise them — ideally work that also uses your existing strengths so you are not operating entirely outside your comfort zone.
The development plan that works
I have seen hundreds of PM development plans. The ones that fail share three characteristics: they are too vague (“get better at strategy”), too broad (five goals simultaneously), and they have no accountability mechanism.
The ones that work follow this structure:
1. Pick one skill gap per quarter.
Not two. One. You will close it faster and the learning will be deeper. If your audit says you are weak in both user research and stakeholder management, pick the one that is hurting your current work more. The other one waits.
2. Define the gap in behavioral terms.
“Get better at user research” is not a goal. “Run four user interviews per month and synthesize findings into a one-page document shared with the team” is a goal. The behavioral definition makes it measurable and it makes avoidance impossible.
3. Find a forcing function.
A forcing function is a commitment that makes it structurally difficult to skip the practice. If your gap is user research, volunteer to own the next discovery sprint. If your gap is stakeholder management, ask to present the quarterly roadmap to the leadership team. If your gap is data analysis, commit to writing the weekly metrics review.
The forcing function works because willpower does not. You will not run user interviews because you decided you should. You will run them because you volunteered to present discovery findings next Friday and you have nothing to present.
4. Get a feedback partner.
This is not a mentor. This is someone who will watch you practice and give you specific, honest feedback. If your gap is presentation skills, ask a colleague to sit in on your next three presentations and give you notes. If your gap is writing, ask someone whose writing you admire to review your next two PRDs before you share them with the team.
The feedback must be specific. “That was good” is useless. “You lost the room at slide seven because you went into technical detail that the sales team did not need” is actionable.
5. Review at 90 days.
At the end of the quarter, re-do the skill audit. Did the external ratings on your focus area move? If yes, pick the next gap. If no, your practice method was wrong — you were going through the motions without actually stretching.
What the India market demands right now
Skill building does not happen in a vacuum. The Indian PM market has specific demands that should influence your development priorities.
If you are at 0-3 years: The market rewards execution speed and technical fluency. Indian startups expect PMs to do more with less — you are often the PM, the analyst, and the project manager simultaneously. Prioritise SQL and data skills, PRD writing, and sprint management. These are table stakes. Without them, you will not survive your first year.
If you are at 3-6 years: The market rewards specialisation. Indian B2B SaaS is growing fast — Zoho, Freshworks, Postman, Razorpay, and hundreds of Series A-C companies need PMs who can own a domain. Pick your specialisation: growth, platform, payments, developer tools, or enterprise. Build deep expertise in one vertical rather than spreading thin across all of them.
If you are at 6+ years: The market rewards leadership and influence. The gap between a senior PM and a product director in India is not technical skill — it is the ability to set direction, build teams, and influence the business. Invest in strategic thinking, executive communication, and cross-functional leadership. These skills are in acute short supply.
Across all levels: AI fluency is no longer optional. PMs who can evaluate AI capabilities, design AI-assisted features, and use AI tools for their own productivity are pulling ahead fast. This is not about becoming an ML engineer. It is about understanding what AI can and cannot do, so your product decisions are informed rather than naive.
Do this exercise right now. Not tomorrow. Not when you “have time.”
-
Write down the six PM skill domains from the table above. Rate yourself 1-5 on each.
-
Identify your hip pocket skill — the one domain where you would rate yourself 4 or 5. Write a sentence about how you use it in your daily work.
-
Pick your weakest domain based on honest self-assessment (or better, ask a colleague to rate you). Write a behavioral goal for this domain:
- Bad: “Improve my stakeholder management.”
- Good: “Present the roadmap to the leadership team once per month and collect feedback on clarity and persuasiveness.”
-
Identify your forcing function. What real project or commitment in the next 30 days will make you practice this skill? Write it down. Tell someone about it — accountability matters.
-
Schedule the 90-day review. Put a calendar event for 90 days from now. When it arrives, re-rate yourself and ask the same colleagues to re-rate you. Did the gap close?
The entire exercise should take 20 minutes. If you spend longer than that, you are overthinking it. The plan does not need to be perfect. It needs to exist.
The learning modes that actually work
Not all learning is equal. For PM skills, the hierarchy is:
Doing > Teaching > Observing > Reading
Reading a book about user research is the lowest-impact way to get better at user research. Running user interviews is the highest. Most PMs over-index on reading because it feels productive and is not uncomfortable. The discomfort is the signal that you are learning.
Specific methods that work:
Shadowing. If you are weak at user research, sit in on interviews run by your UX researcher. Do not take notes on the findings — take notes on the method. How do they phrase questions? When do they probe deeper? How do they handle silence? Then run the next interview yourself while they observe.
Reverse mentoring. Find someone junior to you who is strong where you are weak. A fresh graduate who is excellent at SQL can teach you more in two hours of pair analysis than a week-long course. This also works in reverse — teaching someone else forces you to articulate what you know, which deepens your understanding.
Teardown practice. Pick one product per week. Spend 30 minutes writing a teardown: what is the strategy? Who is the user? What are the metrics that matter? What would you change? After 12 weeks, you will have built a pattern library in your head that no course provides.
The Feynman technique. When you learn something new, try to explain it to someone who knows nothing about the topic. If you cannot explain it simply, you do not understand it. This is especially valuable for technical PMs learning business skills or non-technical PMs learning data concepts.
The plateau trap
Every PM hits a plateau around years three to five. The initial learning curve flattens. The work becomes routine. You start optimising within your comfort zone instead of pushing beyond it.
The plateau feels like mastery. It is not. It is the point at which you have learned enough to be competent and stopped learning enough to be exceptional.
The way out is to change the difficulty level. If you are comfortable running a product team of four, volunteer to lead a cross-functional initiative with fifteen people. If you are comfortable with B2C consumer products, take on a B2B enterprise product. If you are comfortable with Indian markets, push for the international expansion project.
Discomfort is the leading indicator of growth. If your current role feels comfortable, your skills are not growing — they are maintaining.
Test yourself
You are a PM with four years of experience at a Series C edtech startup in Bangalore. Your annual review just happened. Your manager said: 'You are strong on execution — the team loves working with you. But your strategic thinking needs work. Your roadmap presentations to leadership are tactical, not strategic.' You have a quarter to address this.
You have a full plate of feature work. The next quarter has two major launches. Your manager's feedback is clear but you need to decide how to act on it. What is your first move?
your path
You are a PM at Lenskart with 2.5 years of experience. Your last two performance reviews both flagged the same gap: 'strong at execution, weak at strategic thinking — tends to wait for direction rather than shape it.' Your manager has offered to sponsor you for a 6-month leadership program at IIM Bangalore (paid, evenings + weekends). Meanwhile, there is an internal opening on the Vision Pro launch team that your manager thinks is too senior for you, but says you can apply anyway.
The call: Do you prioritize the IIM program, the stretch assignment, or both?
You are a PM at Lenskart with 2.5 years of experience. Your last two performance reviews both flagged the same gap: 'strong at execution, weak at strategic thinking — tends to wait for direction rather than shape it.' Your manager has offered to sponsor you for a 6-month leadership program at IIM Bangalore (paid, evenings + weekends). Meanwhile, there is an internal opening on the Vision Pro launch team that your manager thinks is too senior for you, but says you can apply anyway.
The call: Do you prioritize the IIM program, the stretch assignment, or both?
Where to go next
- Understand the full PM competency model: PM Competency Model
- Transitioning from IC to senior? IC to Senior PM
- Making the leap to director? Senior to Director
- Assess your current skill level: Career Ladder
- Build strategic thinking specifically: Product Vision & Strategy