Lateral Moves and Internal Mobility at Small Companies: A Practical Guide
By Career Ladder Builder
A strong performer with nowhere to go
Priya has been a senior customer success manager for three years. Her ratings are strong, her accounts renew, and she has told her manager twice that she wants to grow. The next level up, Customer Success Lead, is held by someone who is not leaving, and the company has no second lead seat. Her manager says "we'll figure something out." Two quarters later, a recruiter figures it out for her.
Meanwhile, the implementation team two desks over has an open role that rewards exactly what Priya does well: she knows customers' setup problems better than anyone, and she has been quietly fixing onboarding gaps on her own time. Nobody has ever suggested she apply, because nothing on paper says a customer success manager can become an implementation specialist, and nobody knows what level she would land at if she did.
At a 30–200 person company, this is the ordinary shape of the problem. There are few rungs above any given seat, so growth often has to run sideways first. This guide shows how to define lateral career moves so they are an evaluated, level-mapped option rather than an awkward favor, with fit-gap criteria, level mapping across job families, and a manager handoff you can run this quarter.
Why lateral career moves matter more at 30–200 employees
A large company can promote people up a deep ladder. A small one cannot. With a handful of managers and a few levels per function, upward openings come rarely and unpredictably, and a strong employee's growth cannot depend on someone else leaving.
Lateral career moves fill the gap, and they carry a retention signal worth knowing. LinkedIn's 2023 Workplace Learning Report found that employees who make an internal move have a 75% likelihood of staying at the two-year mark, versus 56% for those who don't. That is a correlation, not proof that moves cause retention, but it is a reasonable argument for making internal moves easy to see and easy to take. For the broader link between visible paths and attrition, see how career paths affect retention.
The obstacle is rarely willingness. It is that the move has no definition. Without one, every lateral move is a negotiation, managers treat it as losing a good performer, and the employee cannot tell whether it counts as progress.
What makes a lateral move count as progress
A lateral move reads as a consolation prize when it is vague about three things: the level, the expectations, and the next step afterward. Fix those three and the move becomes legitimate.
Same level, new scope. The employee keeps their level number. A Level 3 customer success manager who moves to implementation arrives as a Level 3 implementation specialist, not a Level 2 on probation. The framework states this rule once, so it does not get relitigated per person.
Different competency mix. A real lateral move changes which competencies carry the most weight. Customer success leans on relationship management and renewal judgment. Implementation leans on technical troubleshooting and project delivery. The move is growth because the employee is being measured on a broader set of skills.
A defined route onward. The employee should be able to see what the next level looks like in the new function. If the implementation ladder tops out two levels above where she lands, the move has headroom. If it does not, say so honestly before the move, not after.
Build the map: job families and level equivalence
Lateral career moves only work when levels mean roughly the same thing across functions. That requires job families with a shared level structure. If you have not grouped your roles yet, start with job families explained, then return here.
A minimal equivalence map has one row per level and one column per job family. Describe each cell by scope, not by tenure:
- Level 2: Works independently on defined tasks. Asks for help on ambiguous problems.
- Level 3: Owns a whole area of work end to end. Handles ambiguity without escalation.
- Level 4: Sets direction for others in the area. Resolves cross-team problems.
The cell text differs by family (a Level 3 in finance owns a close process; a Level 3 in implementation owns a customer rollout), but the scope test is the same. If you can say "a Level 3 owns a whole area end to end" across every family, a Level 3 can move across families without a demotion argument.
Two cautions. First, some moves cross the individual-contributor and manager boundary, which is a different decision with different risks; the IC vs. manager track guide covers it separately. Second, equivalence is a claim about scope, not pay. Compensation decisions belong in their own process.
Score fit gaps with internal transfer criteria
Equivalence tells you where someone lands. Fit-gap scoring tells you whether they are ready to land there. Use the same 1–5 scale and evidence notes you use in evaluations, applied to the target role's competencies instead of the current one's.
A worked example, using round numbers for illustration. Priya is a Level 3 moving to Level 3 implementation. The target role's expectations for five competencies, against her current evidenced scores:
| Competency | Target role expects | Priya's evidenced score | Gap |
|---|---|---|---|
| Technical troubleshooting | 3 | 2 | −1 |
| Project delivery | 3 | 3 | 0 |
| Customer communication | 3 | 5 | +2 |
| Process documentation | 3 | 3 | 0 |
| Cross-team coordination | 3 | 4 | +1 |
The gap is target minus current, so a negative number means development is needed. She has one real gap, in technical troubleshooting, and two strengths that exceed what the role requires. That is a movable profile: a one-point gap on a single competency is closable with a short, specific development plan, and the strengths are a reason the receiving team should want her.
Set transfer criteria in advance so they are not invented per case. A workable rule is: no competency more than one point below target, no more than two competencies below target in total, and every score supported by an evidence note rather than a recollection. The numbers are yours to tune. What matters is that they are written down before the first request arrives. The mechanics of turning scores into gaps are the same ones described in how a skill gap report works.
Run the move: manager handoff and the first 90 days
Most lateral moves fail at the handoff, not the decision. Three steps keep them clean.
- Agree the timing with both managers. The sending manager names a transition date and a backfill or coverage plan. The receiving manager commits to the gap-closing plan. Neither should learn the date from the employee.
- Transfer the evidence. Send the employee's evaluation history, evidence notes, and open development actions to the receiving manager. Starting from a blank file wastes the evidence you already collected and invites a fresh round of subjective impressions.
- Re-baseline at 90 days. Re-score the target competencies using the same scale. If the troubleshooting gap has closed from −1 to 0, the move worked and the record shows it. If it has not, you have a dated, specific conversation instead of a vague one.
Also decide, in writing, what happens if the move does not work out. A defined return path makes people willing to try.
Where to track lateral options for each person
Everything above can be done by hand: an equivalence table, a fit-gap grid per candidate, and a transfer checklist. The weak point is consistency. Fit-gap grids drift when each manager builds their own, and moves that live in email threads leave no record.
CareerEvaluations is built around this closed loop: career frameworks, 1–5 evaluations with evidence notes, auto-generated gap reports, and tracked development actions. If you prefer to start in a spreadsheet, the Career Pathing & Lateral-Move Options Workbook lets you list a person's next moves — up, lateral, cross-track, stretch — and computes a fit gap against each target level's expectations.
Whichever route you take, begin with a single pair of functions that already trade people informally, write the equivalence rule and transfer criteria for that pair, and test them on the next real request. For more guides like this one, subscribe to the newsletter below.
Enjoying this? Get more HR development guides in your inbox.
