Turn a Sideways Move Into a Promotion Case

Start with the org chart, not the job title

When the rung above you is full, a sideways move becomes a promotion case only when it names a target level, an adjacent role, and evidence you already operate at that level. Say your team has no opening above you, but a neighboring function needs someone who can run a process, manage a vendor, and explain a decision to a skeptical stakeholder. Your first task is to make that need visible in the language your company uses for levels.

The move stays sideways when the adjacent team has no budget, no level gap, or no owner who can defend the case. Across LHH's outplacement-supported layoff population of over 418,000 people, 58 percent ended up in a different role or career, and that share has stayed flat since 2022. The move is common; the level gap is the part you must prove.

Map skills the adjacent function already pays for

Choose a few skills the adjacent function pays for, not skills you admire. For support moving into operations, that might be escalation handling, vendor follow-through, and a clean handoff record. For finance moving into program management, it might be variance explanation, stakeholder reporting, and deadline tracking. Write each skill as a result you produced, not a duty you performed.

A finished table has three columns: the skill, the adjacent function’s need, and the proof you can point to. The proof should be specific enough that a hiring manager can verify it without asking you to repeat your story. A skill you cannot prove is decoration.

Software developers had the highest role continuity, with 65 percent staying in the field after transition, followed by corporate attorneys at 61 percent, HR coordinators at 60 percent, accounting professionals at 57 percent, and digital designers at 57 percent. Use that pattern as a check, not a rule. Some functions absorb adjacent talent easily; others keep their own hiring tight. Your job is to find the function where your proof fits the opening.

Read the displacement table before you choose a function

Before you pitch a move, look at role displacement data for your function. Customer operations had the highest share moving into other functions at 90 percent, logistics coordinators at 87 percent, and office assistants at 86 percent. That ranking is a warning about which jobs are treated as interchangeable and which are treated as specialized. Roles on the high-displacement side need stronger proof of level, not just proof of effort.

A title can look like a step up while the level stays the same. Check the level code, the pay band, and the reporting line before you spend months building the case. The note should say the adjacent role carries a higher level, or that it carries the same level with a clear path to the next review.

In 2024, 58 percent of career-transition candidates changed into new occupations, even though roughly 74 percent had initially wanted a similar role. Plans change. The question is whether your plan changes because the evidence changed, or because you got bored with an earlier option.

Ask for a written lateral case, not a promise

Take the case to your manager before you ask the adjacent team. Ask for a written lateral case that includes your target level, the skills that transfer, the adjacent function’s demand, and the manager’s commitment to support the move. A verbal endorsement is useful, but it disappears when the organization changes. The document should read like a short case your manager can forward, with a date and a target level attached.

Only 15 to 20 percent of workers knew about redeployment options, training, coaching, or mentoring. That gap is where good moves stall. Ask what support exists, who owns it, and what the next checkpoint is. When your manager cannot name the checkpoint, the case is still a conversation.

Individualized career-transition support was associated with candidates finding their next job an average of 32 days sooner. You are asking for the structure that makes the move legible: a named sponsor, a skill check, a level review, and a date when the case gets judged. The written case is the thing you bring to the adjacent function.