Turn a Sideways Move Into a Promotion Case

A sideways move is a scope reset

You are ready for the next level, but the seat above you is empty. The org chart makes that look like a dead end, so the promotion case never gets written. A lateral move can fix that when it changes who you are accountable to, what you can decide, and which outcomes you own.

The manager who writes the case needs evidence that the role has grown, not that the person has worked harder. If the new seat only changes the label, it is a transfer. If it opens a larger decision in a strategic domain, it becomes a promotion case.

Build the evidence for the new scope

A public artifact can make the domain known. Google Cloud's Office of the CISO published a second Cloud CISO Perspectives edition in March 2025. What matters is the name, the cadence, and the audience. A timeline does the same work. Google Cloud said its Europe-focused digital sovereignty work began in 2020. A long-running effort is easier to frame as a promotion case when the employee can show they are entering a domain with history, not a project with a deadline.

Scope needs a number. In security leadership, scope is often shown with revenue, risk, or customers. Rittenhouse headed a $3.3 billion Cisco security business unit starting in 2016. Shailaja Shankar was the first female leader of Cisco's security business, a unit with more than 300,000 customers. If your role touches revenue, cost, risk, or customers, put the size of the scope in the case. If it does not, use the size of the decision, the number of teams, or the number of outcomes you now own.

A cross-company promotion can be clear when the prior role is senior enough. Cisco brought Dev Stahlkopf from Microsoft after she had held general-counsel roles there for more than 14 years. A visible level can help too. Wright departed Cisco in May for a senior vice presidency at Bishop Fox. The same logic applies inside a company: the move is stronger when the old role already had seniority, and the new role adds a larger decision.

Run the sequence that protects the case

• Write the departure note before you accept the new seat. Make it a short internal memo that names the scope you are leaving, the scope you are taking, the strategic domain, and the decision rights that change. Frame it as a closure memo, not a resignation: the old role is closed, and the new role is opened with a clear limit. Keep it short enough to be forwarded, and do not ask for sympathy. The note gives the next manager a clear starting point for the promotion case.
• Make the new boss introduction the opening external signal. A short welcome names the role, the scope, and the reason for the move. Make the welcome sound like a deliberate decision, not a fallback. Keep the message short enough that a senior leader can repeat it without adding an explanation, and name the scope in plain language, not job-code language.
• Update the profile as a scope reset. Give it a title, a scope line, and a single sentence that connects the new role to the strategic domain. The profile makes the move clear to someone who has never seen the org chart. If it says only the new title, the case has lost its argument. In every conversation, say what you stopped owning and what you started owning.

The case fails when the announcement arrives before the scope is defined. Keep the order: scope, domain, announcement. If the new seat is clearly larger and easier to defend, the case can be written. It is ready when the scope can be stated in a promotion review without apology.