ic to senior pm
It is not necessarily a promotion that you are waiting for. You are assigned to lead a major project. There is an increased reliance on your decision making by peers. They have started looking to you — 'can you suggest what should we do?' They value your opinions. Your input is sought out.
Here is the most common way PMs get stuck at mid-level: they keep doing the same job better.
They ship faster. They write tighter PRDs. They run cleaner sprints. They become the best IC PM on the team. And then they wonder why the promotion does not come.
The IC-to-Senior transition is not about doing the IC job at a higher quality. It is about doing a fundamentally different job. The skills that made you a good IC PM — execution speed, attention to detail, reliable delivery — become table stakes. They no longer differentiate you. What differentiates a Senior PM is a set of capabilities that most IC PMs have never practised, because nobody asked them to.
After watching hundreds of PMs navigate this transition at Pragmatic Leaders, the ones who get stuck at the IC level almost always have the same profile: technically competent, hard-working, well-liked by engineering — and completely invisible to leadership. They are doing excellent work that nobody above their skip-level knows about. That is not a performance problem. It is a positioning problem.
What actually changes
The shift from IC to Senior PM is a transition along three axes. Most PMs focus on the first and ignore the other two.
From feature work to strategy work. As an IC, you own features. You take a well-defined problem, break it down, work with engineering and design, and ship it. As a Senior PM, you own outcomes. Nobody tells you which features to build. You identify the problems worth solving, frame the opportunity, make the case for investment, and then decide the approach. The feature is an output. The outcome is what you are measured on.
From personal execution to team enablement. This is where most IC PMs resist. You are good at doing things yourself. It is faster, it is more reliable, and you know it will be done right. But a Senior PM who executes everything personally is a bottleneck, not a leader. The transition requires you to shift from “I will do this” to “I will make sure this gets done well” — which means teaching others, delegating, and accepting that someone else’s B+ work that ships on time is better than your A+ work that ships late because you are a single point of failure.
From influencing your squad to influencing the organisation. As an IC, your primary relationships are with your engineering team and your direct manager. As a Senior PM, you need to influence across functions — design, data, sales, marketing, customer success, leadership. You need people who do not report to you and have no obligation to listen to you to align on your direction. This is the skill that separates Senior PMs from perpetual ICs, and it is the hardest to develop because nobody teaches it explicitly.
Annual review calibration at a B2B SaaS company in Bangalore. The Head of Product is explaining why two PMs with similar tenure are being levelled differently.
Head of Product: “Meera and Saurabh both joined two years ago. Both ship on time. Both have strong engineering relationships. But I am putting Meera up for Senior and not Saurabh.”
VP Engineering: “That surprises me. Saurabh is incredibly reliable. The team loves working with him.”
Head of Product: “Saurabh is the best executor on the team. But every quarter, I have to tell him what to work on. Meera comes to me with a point of view. She identified the enterprise onboarding drop-off problem before anyone asked her to. She pulled the data, talked to five churned accounts, built the business case, and proposed three approaches. I just had to say yes.”
VP Engineering: “So the difference is not output quality.”
Head of Product: “The difference is who is generating the work versus who is waiting for it.”
Saurabh found out through his manager. He was devastated — he had shipped more features than Meera that year. Nobody had told him that shipping more features was not the promotion criteria.
The best IC on the team is not automatically the best candidate for Senior PM.
This is the scene that plays out every appraisal cycle at every product organisation I have worked with. The Saurabhs outnumber the Meeras three to one. And the tragedy is that Saurabh is not less capable — he is just optimising for the wrong thing.
The SCOPE framework: five shifts from IC to Senior
The transition from IC to Senior PM comes down to five shifts. I call this the SCOPE framework — because the job is literally about expanding the scope of what you own, who you influence, and what you are accountable for.
| Letter | Shift | From → To |
|---|---|---|
| S | Seek problems | Waiting for the roadmap → shaping the roadmap |
| C | Communicate to influence | Status updates → narratives that change decisions |
| O | Own your area | Owning a backlog → owning business outcomes |
| P | Partner across functions | Engineering trust → cross-functional credibility |
| E | Engage conflict | Deferring disagreements → resolving them directly |
S — From taking problems to finding problems
As an IC, the roadmap exists and you execute against it. As a Senior PM, you are expected to shape the roadmap. This means developing a point of view about where the product should go — not based on what stakeholders are requesting, but based on your own analysis of market, user behaviour, competitive landscape, and business goals.
In India’s startup ecosystem, this shift is particularly difficult because most mid-stage companies do not have clean product strategy. The CEO has a vision, sales has a wishlist, and the PM is expected to navigate between them. A Senior PM does not just navigate — they propose a direction and defend it.
C — From communication as information transfer to communication as influence
IC PMs write status updates and specs. Senior PMs write narratives that change decisions. The difference is not writing quality — it is intent. Every document you write as a Senior PM should answer: “What do I need the reader to do after reading this, and what framing will make them want to do it?”
Neha described what she wants to build. Priya described why it matters to the business. Both are competent PMs. But only one of them is speaking the language that leadership uses to allocate resources. This is not politics — it is communication at the right altitude.
O — From owning your backlog to owning your area
An IC PM owns a backlog. A Senior PM owns a problem space. This means you are responsible not just for what gets built, but for the outcomes in your area — activation rates, retention, revenue, whatever the metrics are. If the metrics are not moving, it is your problem even if the features shipped on time.
This shift requires you to develop business acumen that most IC PMs lack. You need to understand unit economics, revenue models, cost structures, and competitive positioning. You need to read the company’s financial reports, understand the board’s concerns, and connect your product work to the company’s strategic priorities.
P — From being liked by engineering to being respected across functions
IC PMs live in the engineering world. The best IC PMs have deep trust with their developers, run clean sprints, and are considered reliable partners. This is necessary but not sufficient for Senior PM.
At Senior level, you need relationships with sales leadership, customer success, marketing, and the executive team. Each function has different incentives, different timelines, and different definitions of success. A Senior PM who only has engineering credibility cannot drive cross-functional outcomes.
In Indian companies, this is especially true because functional silos tend to be deeper. Sales and product often operate as adversaries — sales wants customisation for key accounts, product wants scalable features. A Senior PM bridges this gap not by compromising, but by reframing the conversation around shared outcomes.
E — From avoiding conflict to managing it
IC PMs can defer most conflicts upward. “Let me check with my lead” is an acceptable response. Senior PMs cannot defer. You are the person in the room who is expected to make the call — even when the call is unpopular.
This means saying no to the VP of Sales who wants a custom feature for a key account. It means telling the CEO that the pet project does not align with the product strategy. It means pushing back on engineering estimates when the data does not support them. It means having the conversation rather than avoiding it.
Rate yourself honestly on each of these five dimensions. Use a 1-5 scale where 1 means “I have never done this” and 5 means “I do this consistently and well.”
- Problem finding: In the last quarter, how many problems did you identify and propose solutions for that were NOT on the existing roadmap or requested by stakeholders?
- Strategic communication: Can you explain your product area’s impact on the company’s revenue and strategic priorities in two sentences? Try it now. If you struggle, you are operating at the wrong altitude.
- Area ownership: Do you track business metrics for your area weekly, or only when someone asks? Do you know your area’s NRR, activation rate, or conversion rate off the top of your head?
- Cross-functional influence: List the five most senior people outside of product and engineering who know your name and your work. If you cannot name five, your influence radius is too small.
- Conflict management: Think of the last time you disagreed with a senior stakeholder. Did you voice the disagreement directly, or did you defer? If you deferred, what was the cost?
Score yourself. Any dimension below 3 is a gap that will block your promotion — regardless of how well you execute features.
The scope expansion trap
There is a common failure mode among PMs who are actively trying to get promoted: they ask for more scope. “Give me another product area. Let me own more features. I will prove I can handle it.”
This is backwards. More scope at the same altitude is not a promotion — it is just more work. If you own three feature areas but you are still executing against someone else’s roadmap in all three, you have not demonstrated Senior PM capability. You have demonstrated that you are a reliable IC who can juggle more balls.
The correct move is to go deeper and higher in your existing area. Go deeper by understanding the business context, the competitive landscape, and the user segments you do not currently serve. Go higher by proposing strategic direction rather than waiting for it.
Talvinder’s rule: Depth of impact beats breadth of ownership every time. One area where you drove measurable business outcomes is worth more than five areas where you shipped features on schedule.
The promotion is not the goal
Here is what I tell every PM in my programmes who asks me “how do I get promoted to Senior PM”: you are asking the wrong question.
If you focus on getting promoted, you will optimise for visibility, for appearing strategic, for collecting the right keywords on your self-review. And your manager will see through it. Every experienced product leader can tell the difference between a PM who is genuinely operating at Senior level and a PM who is performing Senior-level behaviours for an audience.
The right question is: “What capabilities do I need to develop to be effective at the next level?” Develop the capabilities. The promotion follows. It may follow at your current company or at the next one — and it does not matter which. The capabilities travel with you. The title does not.
As I always say: it doesn’t matter whether you will be promoted within the company or in the next company. The point is you will have something that you have built — either way, you will be a far better person and a better professional after the project.
Test yourself
You are a PM at a Series C edtech company in Hyderabad. You have been in the role for two years, shipping reliably. Your manager tells you in your 1:1 that you are being considered for Senior PM, but the leadership team wants to see 'more strategic impact' before the next cycle. You have three months. What do you do?
Your first instinct is to figure out what 'more strategic impact' means. You have a few options for how to spend the next three months.
your path
The single most powerful artefact for your promotion is a one-page document that answers these four questions about your current product area:
-
What is the biggest unsolved problem in my area? Not a feature gap — a business problem. “Our activation rate is 34% which means we lose two-thirds of signups before they experience the core value” is a business problem. “We need a better onboarding flow” is a feature request. Find the problem.
-
What is it costing the company? Quantify in revenue, retention, or growth terms. Talk to finance if you have to. “Each 1% improvement in activation is worth X ARR” is the kind of sentence that gets leadership attention.
-
What are three approaches to solving it? At three different investment levels — small (2-week experiment), medium (one-quarter initiative), large (multi-quarter platform change). Show that you can think in terms of trade-offs and risk, not just solutions.
-
What would you recommend and why? Take a position. Do not present three options and say “what do you think?” Say “I recommend option B because it has the best ratio of expected impact to investment, and here is the data that supports it.”
Write this document. Then show it to your manager. If they are surprised by the depth of your business understanding, you have been operating at the wrong altitude — and now you know it.
You are a PM at a Series B consumer payments company in Bengaluru (Razorpay-adjacent, 400K SME merchants). You have been in the IC PM role for 2.5 years and are actively working toward a Senior PM promotion. Your Head of Product asks you to own a week-long internal hackathon — organizing 12 teams, setting up judging, and running the demo day. The work is entirely operational and will consume roughly 60% of your week. It is not visible to the product leadership team above your manager. Your Q3 OKR work — a merchant churn reduction initiative that is already showing early signal — will stall for the week.
The call: Do you take on the hackathon ownership, or push back? And if you push back, how do you do it without damaging the relationship with your manager?
You are a PM at a Series B consumer payments company in Bengaluru (Razorpay-adjacent, 400K SME merchants). You have been in the IC PM role for 2.5 years and are actively working toward a Senior PM promotion. Your Head of Product asks you to own a week-long internal hackathon — organizing 12 teams, setting up judging, and running the demo day. The work is entirely operational and will consume roughly 60% of your week. It is not visible to the product leadership team above your manager. Your Q3 OKR work — a merchant churn reduction initiative that is already showing early signal — will stall for the week.
The call: Do you take on the hackathon ownership, or push back? And if you push back, how do you do it without damaging the relationship with your manager?
Where to go next
- Ready for the next transition? From Senior PM to Director
- Build the skills that matter most at Senior level: Influence Without Authority
- Learn to speak leadership’s language: Presenting to Leadership
- Understand the full PM career ladder: The PM Career Ladder
- Sharpen your strategic thinking: Product Vision and Strategy