Most newly-promoted VPs do not make SVP. The pattern is not random. The senior leadership selection at the SVP layer reads a different operator than the one the VP promotion selected for. The two roles look similar from the org chart and operate very differently inside the room.
VP-level success rewards cross-functional reach within a function area. Operating a substantial team. Delivering on the standing operational outcomes the function is responsible for. Coordinating with peer VPs across functions. Building the relationships with the executive layer above that signal you are seriously in the room. The VP seat is the altitude where operational ownership at scale, combined with executive presence, is the operating profile.
SVP-level promotions look at something different. The SVP layer is where the room is reading whether the operator can hold a portfolio that spans functions, not just one. Whether they can be trusted with the kind of cross-portfolio decision-making that is not just a coordination problem but an actual prioritization decision against scarce resources. Whether their judgment under pressure has been demonstrated on the moves that did not work out as well as the ones that did. Whether their relationship with the executive team above is one of partnership rather than reporting.
Most newly-promoted VPs do not deliberately build for this shift in the first eighteen months at the VP level. They continue operating at high competence within the functional VP profile. The room reads them as operating at the VP level. Three years in, when the SVP seat comes open, the read the room has already written is that this person is a strong VP, not a likely SVP. The promotion goes to the peer VP who carried themselves as a portfolio operator from month four onward.
The structural moves that separate the VPs who make SVP are knowable. The first is portfolio thinking from month one. Read your role as part of a larger portfolio the SVP layer above you is responsible for. Operate in front of your peers like you are jointly accountable for the portfolio outcomes, not just for your function's piece. Bring portfolio-level observations into the executive team meetings, even when they fall outside the strict scope of your function.
The second move is the executive partnership over reporting. The relationship with your SVP, your COO, or your CEO is the relationship that the next promotion is decided in. Operate in that relationship as a partner who is informing the executive's thinking, not as a reporting line waiting for direction. The signal you are sending is whether the executive layer can imagine you sitting at their altitude, or whether the role you are filling is the ceiling.
The third move is the demonstrated read on the moves that did not work. The SVP selection process is unconsciously calibrated against operators who have only the cleanly-successful stories to tell. The VPs who make SVP have learned to bring forward the calls that did not land cleanly, with the structural read on what was missed, in a way that signals the kind of judgment SVP-level decisions actually require. Vulnerability is not the same thing as weakness. The SVP layer is looking for the kind of self-aware operator who can hold a portfolio in front of a board.
The window is roughly eighteen to twenty-four months. The VP-to-SVP timing is not a calendar function. It is a signal function. The room writes whether you are SVP-track or VP-ceiling somewhere between month twelve and month twenty-four of your VP tenure. The work is to do it deliberately, early, and with the operating model the SVP altitude actually requires.