the vp/cpo path

Most Directors think the VP role is a bigger version of what they already do. More PMs to manage. Bigger roadmap. Harder prioritisation conversations. They are wrong.

The transition from Director to VP is a category change, not a scale change. The job description changes completely. The skills that got you to Director — deep product judgment, execution discipline, cross-functional influence on specific features — become table stakes, not differentiators. What gets you to VP and keeps you there is something else entirely.

This page is about that something else.

What actually changes at the VP level

There is a clean way to think about the product management career stack:

• PMs and Senior PMs live in execution — shipping features, managing backlogs, running sprints.
• Group PMs and Directors live in business planning and program — roadmaps, team coordination, quarterly goals.
• VPs, SVPs, and CPOs live in market focus and business — portfolio strategy, org design, company-level decisions.

The move from Director to VP is crossing from the second band into the third. You stop being primarily an operator and start being primarily a strategist. The key word is primarily. You still need to understand operations — you just cannot live there.

Here is what that shift looks like in practice:

The unit of your work becomes the organisation, not the product. A Director owns a product area and is accountable for its outcomes. A VP owns the product organisation and is accountable for its capability to produce outcomes — across all product areas, current and future.

Your calendar becomes a resource allocation instrument. Every meeting you take, every team you fund, every role you create or cut — these are bets about where the company is going. A Director optimises for current quarter. A VP is constantly arbitrating between current quarter and next year.

You are now a company spokesperson, not a product spokesperson. In customer meetings, board discussions, investor calls, and analyst briefings, you are not explaining your product. You are explaining the company’s strategic direction. The product is the evidence. The argument is about market position, competitive moat, and where the business will be in three years.

You are responsible for the quality of thinking in your org, not just your own thinking. The ceiling on your impact is no longer your individual product judgment. It is the aggregate quality of every PM in your organisation. Your job is to make them better.

The identity shift most Directors are not prepared for

The hardest part of the VP transition is not the strategy work. It is the identity work.

You built your career on being the expert. You knew the product better than anyone. You had opinions. When someone said something wrong in a meeting, you corrected them with data. When a roadmap decision was contentious, you were the one with the analysis. Your value was in being right, specifically and demonstrably right.

At the VP level, that identity becomes a liability.

The first sign you have not made the transition: you are still the smartest person in your product reviews. If every major product decision runs through your judgment, you have not built a product organisation — you have built a hub-and-spoke where you are the hub. That does not scale, and it signals to every strong PM in your org that their judgment does not matter.

The second sign: you still define your success by the quality of your individual contributions. A well-crafted strategy doc. A sharp insight in a meeting. A problem you personally solved. These feel like wins because they always were. But at the VP level, what matters is whether the organisation solved the problem without you. If it needed you, you failed.

The third sign: you protect your time for “real product work” instead of the work that looks like meetings, hiring, and internal communication. There is a version of VP who is still doing IC work on the side because that is where they feel competent and get validated. This person is usually popular with their immediate team and ineffective at the organisational level.

The transition requires a genuine identity shift: from “the person with the best product answers” to “the person who builds an organisation with great product answers.” These are not the same skill set. Some very talented Directors never make this shift. They get promoted, get frustrated, and eventually go back to an IC-track role — which is the right call. Not everyone should become VP, and that is fine.

Board communication: a different language

Before VP, you probably had limited board exposure. Maybe a section in a board deck, maybe a product demo. You prepared something polished, presented it, answered a few questions, and left.

At VP and especially CPO, you are a standing voice in board discussions. This requires a different communication model.

Board members are not your users. Your users care about the feature. Board members care about the market. When you talk to a board, you are not explaining what you built. You are explaining why the market will reward it, and why your current bets are defensible against the alternatives.

Lead with the strategic narrative, not the product update. Bad board communication sounds like: “In Q1 we shipped X, Y, and Z. In Q2 we plan to ship A, B, and C.” This is a changelog. It tells the board nothing about whether your strategy is working. Good board communication sounds like: “The thesis we entered Q1 with was that SME customers would convert at higher rates if we reduced onboarding friction. Here is whether that thesis held, and what we learned that changes our Q2 bets.”

Name the risks. Board members are sophisticated. If you present only the positive, they stop trusting you. Every strategic presentation should explicitly name the two or three things that could make your strategy wrong. This is not weakness — it is judgment. Boards allocate capital. They need to know where the uncertainty is, not just where the confidence is.

Know when you are speaking for the function versus the company. Sometimes you are in the room as the “product person” — and your job is to represent the product organisation’s perspective. Sometimes you are in the room as a company leader — and your job is to support the company’s decision, even if it is not what your organisation would have chosen. Know which mode you are in. Conflating them creates confusion and erodes your credibility with the CEO.

In Indian startups specifically: Board communication at high-growth Indian startups often happens in a context where the founders are still deeply operational and the board includes international VCs who have a different mental model of what a CPO does. The CPO in a US Series C company has significant strategic authority. The CPO in an Indian startup is often navigating founder-led decision-making where they are influential but rarely final. This is not a reason to defer everything — it is a reason to be explicit about what decisions you own versus what you recommend.

Org design is a product problem

Most new VPs treat org design as HR work. It is not. It is the most consequential product decision you make.

The structure of your product organisation determines what problems get worked on, which teams have leverage, how fast decisions get made, and where conflicts accumulate. Bad org design produces bad product outcomes regardless of individual talent.

There is no universally correct structure. But there are a set of decisions you need to make explicitly rather than letting them happen by default.

Align teams to outcomes, not outputs. If your org is structured around features (“the notifications team,” “the onboarding team”), teams will produce features. If it is structured around outcomes (“the activation team,” “the monetisation team”), teams will produce results. The difference is not semantic — it changes how teams set goals, how they measure success, and what they escalate.

The two-pizza rule is not enough. Keeping teams small is necessary but not sufficient. What matters is whether the team has end-to-end ownership of something with a clear success metric. A small team working on a feature without clear ownership of the outcome is still a dysfunctional team, just a small one.

Design for your weakest seam, not your strongest team. The failures in product orgs almost always happen at the boundaries — between the platform team and the product teams, between the India product team and the US product leadership, between product and data. Your job as VP is to watch these seams. Where does work fall through? Where do decisions get stuck because no single team owns them? Where do two teams solve the same problem independently because neither knows the other is doing it?

In India: the dual-team problem. Many Indian product organisations have a “core product team” in India and product leadership in the US or Europe. This creates a structural tension. The India team often owns execution but not strategy. The offshore leadership team often owns strategy but not ground truth. The VP/CPO who is based in India has a specific and important role: bridging this gap, not just managing it. That means making sure the India team has genuine input into strategic decisions, not just roadmap review slots.

Headcount decisions are strategy. Every time you create a new PM role, you are saying this problem is worth dedicated product thinking. Every time you eliminate a role or move it, you are saying something has changed about the problem’s priority. Treat headcount planning the way you treat product prioritisation — with explicit trade-offs, not just budget math.

The company strategy question

At Director level, you consume company strategy. At VP level, you contribute to it. At CPO level, you co-own it.

This is the shift that many product leaders never fully make. They do excellent work inside the product organisation but are passive in company-level strategy discussions. This is a missed opportunity — and eventually a career ceiling, because the most influential CPOs are the ones whose fingerprints are on the company’s market bets, not just on the product execution.

Product insight should inform company strategy. You talk to customers. You watch where users drop off and where they keep coming back. You see which features get used and which get ignored. This is a continuous signal about where the market is going — and it is information that your CFO and your sales leadership do not have. If you are not translating that signal into strategic input at the executive level, you are leaving value on the table.

Own a company-level thesis, not just a product roadmap. The CPOs who have the most strategic influence are the ones who walk into executive discussions with a view on the market, the competition, and where the company should be in 18 months — informed by product data. Not a roadmap. A thesis. “Here is what I believe is true about the market. Here is the evidence. Here is what it means for our bets.”

When product and business conflict, say so explicitly. One of the most common failure modes for CPOs is silently absorbing business requirements that contradict good product strategy — building features for sales, adding SKUs for a specific deal, changing the product to match a competitor rather than to serve customers. You will sometimes have to do these things. But do not do them silently. Name the trade-off. “We are doing this for the enterprise deal. Here is what it costs us in the consumer product. I want us to decide explicitly, not by default.”

Test yourself

Where to go next

• Leadership styles for PMs: Leadership Styles
• Building and structuring a PM team: Building a PM Team
• Managing through organisational change: Change Management
• The strategy work that precedes the CPO role: Product Strategy
• Communicating at the executive level: Stakeholder Management