How to Make the VP Title Catch Up With Your Work

 

One of my clients had a problem that sounds flattering until you are the one living it: Everyone treated her like a VP except the org chart. She was doing the work, but she didn’t get the title.   Rachel was a Senior Director, but she was already sitting in the same meetings as the VPs, making similar decisions, and carrying work with comparable scope.   Other executives trusted her judgment. She was included in strategic conversations. She had already demonstrated that she could operate at the next level.   So she assumed the title would eventually catch up. It didn’t.   Her company was already getting the benefit of her VP-level leadership. There was no automatic reason for them to redesign the role, find the budget, and make the title official.   The turning point was not another big win.   Rachel stopped waiting for senior leaders to connect the dots and “award” her the recognition.   She became more deliberate about communicating the business impact of her work. She built advocacy with other VPs and members of the C-suite. And she told them she wanted the VP role.   Eventually, she had a direct conversation with the CEO.   She explained that she was already operating at the next level, showed what she could accomplish with a broader mandate, and asked what needed to happen for the title to follow.   They agreed on a roadmap and a timeline. Just months later, she was promoted to VP.   Her performance made her qualified. Her promotion strategy made the decision possible.   Doing VP-Level Work and Creating a VP Promotion Are Two Different Jobs This might be where you get stuck. You take on broader scope, solve increasingly complex problems, and become the person everyone relies on when the stakes are high.   Then you assume the work will speak for itself. It rarely does.   Your company can benefit from your VP-level contribution for a long time without changing your title, authority, or compensation.   Your work is the evidence, but you still need to build the bridge between that evidence and a promotion decision. That is what no one tells you upfront.   Here’s the good news: following this strategy is how you turn all of your effort into a promotion without waiting in line.   Think of it like turning great ingredients into a five-star meal. You already have the raw material. The strategy makes it something senior leaders want to order.

The BRIDGE Framework If you are already operating beyond your title, or if you want to be, use this six-part framework:   B: Benchmark the VP role Define what VP-level leadership actually means inside your company.   R: Reframe your work Translate responsibilities and achievements into executive-level business impact.   I: Illustrate the future value Show what the broader VP mandate would allow you to own, change, or accelerate.   D: Develop senior advocates Build support with the leaders whose opinions influence the decision.   G: Gain agreement on the path Get clear on the criteria, decision-makers, and realistic timeline.   E: Execute against the roadmap Keep building evidence, visibility, and advocacy until the decision is made.   The goal is not to create six separate steps. It is to build one clear story that senior leaders can understand, believe, and repeat.   1. Benchmark the VP Role in Your Company Before you say you are already operating at VP level, you need to know how your company defines it. Titles vary dramatically. A VP in one organization may have less responsibility than a Director somewhere else.   More work is not automatically higher-level work either.   You can manage a larger team, inherit more projects, and stay deeply involved in execution without demonstrating the judgment or organizational reach expected from a VP.   Start with three things: Scope: What business outcome, function, or strategic priority does a VP own? Decision-making: What tradeoffs, investments, and resource decisions are they trusted to make? Organizational reach: How far beyond their immediate team does their influence extend?   Use your company’s level guides or executive competencies if they exist. You can also study two or three current VPs. If your manager is at that level, compare the altitude of their role with yours.   A useful definition might sound like this: In our company, a VP owns an enterprise-level outcome, makes tradeoffs across several functions, owns budget and headcount decisions, contributes to SLT planning, and shapes the operating strategy rather than only executing it.   Now compare your current work with that mandate.   Where are you already operating at that level? Where do you still need more experience, authority, or exposure?   This is not an exercise in convincing yourself that everything you do is VP-level. It is an honest assessment of what is already true and what still needs to change.   Your output: Write a clear definition of VP-level leadership in your company. Then create two columns: what you are already demonstrating and what you still need to develop or make visible. You are not looking for 100% overlap, aim for 30-40% of your work being at or impacting the next level.   2. Reframe Your Work as Executive-Level Impact Most promotion cases read like annual performance reviews.   They list projects, responsibilities, and achievements: Launched a new program. Improved a process. Inherited another team. Delivered against the plan.   All useful. But a longer list of accomplishments does not automatically demonstrate executive readiness.   Senior leaders need to understand the pattern behind the work: What kind of problems are you trusted to solve? What judgment are you already exercising? What changes for the business because of your leadership?   Use this structure: Scope → Judgment → Business impact   What did you take ownership of? What important decision, tradeoff, or change did you lead? What happened for the business as a result?   For example: We completed the new customer onboarding program.   That explains the activity.   A stronger version is: I aligned product, sales, and customer success around a new onboarding model, which reduced friction for customers and created a more scalable path to enterprise adoption.   The second version shows cross-functional leadership, decision-making, and business value.   Same work. Different altitude.   This translation should not happen once, six weeks before your promotion conversation. It should show up in your executive updates, presentations, Slack conversations, one-on-ones, and the way you explain your recommendations.   Your promotion document should not be the first time senior leaders understand the value of your work. By then, the story should already feel familiar.   Your output: Practice communicating your impact in everyday situations. Then build an evidence bank with three to five examples using Scope → Judgment → Business impact.   3. Illustrate What the VP Role Will Unlock This is the step that surprised me the most when I was doing this work. I assumed my past experience is the way to prove myself for the future VP role.   It’s not.   Your future impact, once you are in the role, is what makes the promotion inevitable. Let me explain the logic behind it.   A promotion is a bet on future value, not a lifetime-achievement award.   Many leaders spend most of their promotion case documenting the past, then expect senior leadership to reach the obvious conclusion: I have already done all of this, so it is obvious I will succeed at the next level.   That argument asks senior leaders to trust something they can’t imagine.   A stronger case shows what you have done up until now, and what you will do once promoted.   What would move faster if you had the broader authority? What business outcome could you own more fully? What disconnected priorities could you bring under one strategy? What executive bottleneck could you remove? What capability does the company need that you could build?   For example: Over the past year, I have expanded my scope across customer acquisition, retention, and product adoption. Today, those areas sit across three teams with different priorities and no single owner for the full customer journey. In the VP role, I would own the end-to-end growth mandate, control the tradeoffs across budget, product priorities, and team resources, and be accountable for increasing net revenue retention from X% to Y%, worth $Z million in recurring revenue.   That is more than a request for recognition. It is a business case for the role.   It also creates healthy FOMO. Senior leaders can see what the organization may be leaving on the table by keeping your mandate fragmented or unnecessarily narrow.   Your output: Identify the three most important outcomes the broader VP mandate would allow you to own, improve, or accelerate.   4. Develop Senior-Level Advocates Your manager’s support matters. For a VP promotion, it is rarely the only support you need.   Senior-level promotions usually involve several people. Some approve the decision formally. Others influence the conversation before it ever reaches that stage.   Rachel’s case became stronger because other VPs and C-level executives had already seen her operate at the VP level, and heard from her directly, that she is pursuing that promotion.   They trusted her judgment. They understood her impact. When her name came up, the CEO was not hearing an ambitious proposal from one employee. He was hearing a case that other senior leaders already believed.   Your advocacy map should include three types of people: The process owner: Usually your manager or another leader responsible for initiating the promotion. The validators: Senior peers or cross-functional executives who can confirm that you already operate credibly at their level. The decision-maker or executive sponsor: Someone with enough influence to support the business case and move the decision forward. Could be your skip level manager or C-suite exec.   Do not wait until promotion season and ask someone to advocate for you out of nowhere. Advocacy is built through repeated exposure to how you think, decide, communicate, and lead.   Create opportunities for the right executives to see you work on meaningful problems. Bring them recommendations, not only updates. Ask for their perspective on strategic decisions. Build shared wins that allow them to experience your leadership directly.   By the time the formal conversation happens, your name should not feel like a new proposal. It should feel like the logical conclusion. I have a full guide to building executive sponsors here   Your output: Create a simple map showing who owns the process, who can validate your readiness, and who can influence the final decision.   5. Gain Agreement on the Promotion Path This is where many promotion conversations quietly die.   You tell your manager that you want to become a VP. They say you are doing an excellent job. They tell you that you are on the right path. You leave encouraged, but nothing has actually changed, and now you feel weird to bring it up again.   A compliment is not a promotion roadmap. A stronger conversation might sound like this: I am interested in moving into a VP role to continue growing my impact and helping the company [achieve goal]. Based on the scope I am already leading and the impact I have delivered, I believe I am operating at that level in several important areas. I would like to align on what still needs to be true, who needs to support the decision, and what a realistic timeline could look like.   You are not asking for a guarantee. You are asking the company, and your manager, to define the path.   By the end of the conversation, you should understand three things: What must be true: The remaining evidence, outcomes, or development required. Who must agree: The leaders involved in recommending, validating, and approving the promotion. When the decision can happen: The checkpoints and realistic decision window.   Inside Success Builders, I teach clients to begin the promotion conversation six to twelve months before they expect the promotion.   Senior-level decisions take time. The organization may need to consider compensation, budget, succession planning, organizational design, and the effect on other roles.   Rachel’s promotion took eight months after she raised the conversation directly.   That did not mean the strategy was failing. It meant there was finally a real process, with an actual decision at the end of it. Without it she might have waited three more years.   Your output: Document the agreed criteria, decision-makers, checkpoints, and target decision window. Check in with your manager every 2-3 months to make sure you and the process are on track.   6. Execute Against the Roadmap A promotion case is not a just a document you unveil during your annual review. It is a story you build over time.   Once you have a roadmap, your job is to keep producing the evidence and making it visible to the right people.   Each month, reinforce one important proof point, create one meaningful moment of senior-level exposure, and move one advocate closer to confidently supporting your case.   Then use your checkpoints to assess progress.   What has changed? What evidence is now stronger? Who has become more supportive? What remains unresolved? Has the company taken concrete action, or are you still receiving vague encouragement?   This matters because a roadmap should help you move toward a decision. It should not become a more sophisticated way to wait indefinitely.   If the company keeps changing the criteria, delaying the conversation, or benefiting from your expanded scope without creating a credible path, that is a sign to consider your options.   You may still decide to stay. But you should make that decision with your eyes open.   Your output: Create a monthly plan for the evidence you will build, the leaders who need exposure to it, and the checkpoints where you will reassess the path.   Your Six-Month BRIDGE Plan The exact timeline will depend on your company, but the work usually follows this sequence:   Months 1 and 2: Build the foundation Benchmark the VP mandate and create your evidence bank. You should know how your company defines the role, where you already meet the standard, and which gaps are real.   Months 2 through 4: Socialize the case Start communicating your impact and your desire to grow more deliberately. Develop the future mandate and create stronger exposure with potential advocates. The goal is for senior leaders to understand both what you are already doing and what the company gains by expanding your role.   Months 4 through 6: Formalize the path Raise the direct promotion conversation. Align on criteria, decision-makers, checkpoints, and timing. Then execute against the roadmap and keep testing whether the company is genuinely moving toward a decision. Some organizations might need more time than others. Don’t focus on the timeline, focus on the process.   Copy-and-Paste Template: Your VP Case in Five Sentences Use this as the foundation for a conversation with your manager or another senior leader: Over the past [time period], my scope has expanded from [previous scope] to [current responsibilities]. In that scope, I have led [important decisions or cross-functional work] and delivered [meaningful business outcomes that demonstrate VP level work]. Based on how our company defines VP-level leadership, I believe these examples already demonstrate [relevant scope, judgment, and organizational influence]. In the VP role, I would use the broader mandate to [future outcomes the role would unlock]. I would like to align on what still needs to be true, who needs to support the decision, and a realistic timeline for moving forward.   Do not deliver this word for word like a speech.   Use it to make sure your case includes the five things senior leaders need to understand: Your scope. Your impact. Your readiness. The future value. The decision path.

Your Next Steps If your company already trusts you with VP-level work, do not assume the title will eventually catch up. Start building the decision now.   Use the BRIDGE framework to define the role, make your impact visible, show what the company gains, build the right advocacy, and agree on a real path forward.