For most of the last century, “career growth” meant one thing: up. You joined at the bottom, put in your years, and climbed. Every rung was a title. Every title was proof you were winning.
That model still exists on paper in a lot of organizations. In practice, it’s breaking down. Promotion slots haven’t kept pace with flatter org charts. Skills go stale faster than job descriptions get rewritten. And employees – especially the ones you most want to keep – are asking a question the ladder was never built to answer: what if the next step isn’t up?
That’s the real story behind the career lattices vs career ladders debate. It isn’t a branding exercise. It’s a structural response to how work actually moves now.
What a Career Ladder Actually Is
A career ladder is a single-track, vertical progression system. Analyst to senior analyst to manager to director to VP. One path, one direction, clearly ranked.
Ladders work well when three things are true: the organization is growing fast enough to keep creating room at the top, roles are stable enough to define years in advance, and success genuinely means “more people reporting to you.” For a lot of 20th-century manufacturing and corporate hierarchies, all three held.
None of them hold as consistently today. Organizations have de-layered. A senior individual contributor at many tech and professional-services firms now earns more and holds more influence than a first-line manager two levels below a VP. And an entire generation of specialists – engineers, designers, data scientists, clinicians – never wanted to manage people in the first place. They wanted to get better at the work.
The ladder doesn’t have a rung for that. So people leave to find one somewhere else.
What a Career Lattice Actually Is
A career lattice replaces the single vertical track with a grid. Growth can move up, sideways, or diagonally – a marketing manager moving into product, an engineer stepping into a technical leadership track without ever managing headcount, a finance analyst rotating through operations before returning to a bigger finance role with sharper judgment.
The term comes from Deloitte’s Cathy Benko, who argued that the industrial-era ladder metaphor no longer matched how careers or organizations actually function. In her original framing for Harvard Business Review, she described the corporate ladder as a metaphor suited to the industrial world of the last century – one giving way to a more adaptive model she called the corporate lattice. Fifteen years later, that argument reads less like a prediction and more like a description of where most companies already are, whether they’ve named it or not.
A lattice isn’t the absence of structure. It’s a different structure – one that treats depth, breadth, and lateral experience as legitimate forms of progress, not consolation prizes for people who “didn’t make it” into management.
Career Lattice vs Career Ladder: The Core Differences
| Career Ladder | Career Lattice | |
| Direction of growth | Vertical only | Vertical, lateral, and diagonal |
| Definition of “success” | Title and headcount managed | Skill depth, scope, and impact |
| Path visibility | One predictable track | Multiple valid tracks |
| Best suited for | Stable, hierarchical, slow-changing roles | Skills-based, project-driven, fast-changing roles |
| Risk if unmanaged | Bottlenecks, attrition when promotions stall | Confusion without clear skill and level criteria |
| Manager’s role | Approve the next rung | Broker moves across the business |
Neither model is inherently better in the abstract. A ladder still makes sense in functions where progression genuinely is linear – regulated professions with defined seniority tiers, for instance. But for most knowledge work, the lattice describes what’s already happening; the ladder just hasn’t caught up to it on the org chart.
Why This Shift Is Showing Up on HR’s Agenda Right Now
Three forces are pushing lattices from theory into practice.
Skills are turning over faster than job titles: A role written two years ago may already require capabilities that didn’t exist when the job description was drafted. A ladder assumes the destination is fixed. A lattice assumes the destination will move, and builds the ability to adapt into the structure itself.
Promotion math doesn’t work in flat organizations: When there are five managers for every fifty individual contributors, “climb to the next level” isn’t a plan – it’s a bottleneck. Lattices give people somewhere to grow that doesn’t depend on someone else’s job opening up.
Retention now runs through visible growth, not just pay: Internal mobility has become one of the clearest signals HR leaders track for whether people plan to stay. LinkedIn’s most recent workplace learning research found that internal mobility has become a higher priority for roughly half of HR and L&D professionals over the year ahead – a sign that “grow here or leave” is no longer a fringe concern for talent teams, it’s a mainstream retention lever. Our own look at workforce data on career development found much the same thing: employees increasingly judge an employer by whether growth paths exist, not by whether a title changes every eighteen months.
What a Lattice Looks Like Day to Day
It’s easy to talk about lattices in the abstract and harder to picture them operating inside a real team. A few patterns show up consistently in organizations that have made the shift work:
- Dual career tracks: A technical or specialist track that runs parallel to the management track, with comparable pay ceilings, so senior engineers, designers, or scientists don’t have to become managers to keep advancing.
- Structured lateral moves: Formal rotation programs, internal gigs, or short-term project assignments that let someone build breadth without changing their formal level.
- Skills-based leveling: Career frameworks defined by demonstrated capability and scope of impact rather than years of tenure or headcount managed.
- Manager incentives that reward “exporting” talent: Without this, lattices collapse quietly – managers who lose their best people to a lateral move elsewhere in the company have no reason to encourage it, and they won’t.
That last point is where most lattice initiatives quietly die. A framework on the intranet doesn’t change behavior if managers are still evaluated purely on whether their own team stays intact. The organizations getting this right treat internal transfers as a retention win for the company, not a loss for the manager who let someone go. It’s a point we’ve dug into in more detail in our piece on workforce redeployment and internal mobility strategy – the mechanics of moving talent inside a company are surprisingly similar whether the goal is redeployment during a downturn or growth during expansion.
The Honest Objections – and Where They Hold Up
Lattices aren’t a fix-all, and it’s worth naming where the skepticism is fair.
Some employees genuinely want the clarity of a ladder. “Do X for two years, get promoted to Y” is reassuring, and a poorly implemented lattice can feel like the company simply removed the promotion path and called it flexibility. If lateral moves aren’t tied to pay progression, skill recognition, or a documented growth story, they start to look like busywork dressed up as opportunity.
There’s also a real coordination cost. Ladders are cheap to administer – one track, one set of criteria. Lattices require HR to maintain a skills taxonomy, a way to match people to open roles across departments, and managers who are willing to let talent move. Smaller organizations without dedicated HR capacity can struggle to build this without it becoming informal and inconsistent – visible mobility for people with the right relationships, invisible for everyone else.
The fix isn’t abandoning the lattice. It’s pairing it with the same rigor a ladder has: clear levels, transparent criteria for what counts as growth, and pay structures that recognize lateral and depth moves as real progress, not a consolation prize.
Building a Lattice Without Losing Structure
For HR and people leaders weighing this shift, a few starting points matter more than a full framework rebuild on day one:
- Map skills before you map titles: Define what capability and impact look like at each level, separate from any specific job title. This becomes the backbone that makes lateral moves legible.
- Publish the lattice, not just the ladder: If employees can only see the vertical path in a performance review, they’ll assume it’s the only one that counts.
- Track internal mobility as a retention metric: Time-to-fill from internal candidates, percentage of open roles filled internally, and mobility-adjacent attrition are more revealing than engagement scores alone.
- Fix the manager incentive problem first: Talent hoarding will quietly kill every other part of this list if managers are still rewarded for headcount retention over talent development.
None of this requires abandoning hierarchy altogether. It requires being honest that hierarchy alone no longer describes how most careers – or most organizations – actually grow.
FAQs
Is a career lattice the same as “no career path”?
No. A lattice still has defined levels and criteria; it just allows more than one direction to reach them. The structure is the same amount of rigor applied to more than one axis of movement.
Does a career lattice mean employees never get promoted vertically?
No. Vertical promotion remains part of a lattice. It simply stops being the only recognized form of growth, alongside lateral moves and deepening expertise.
Which model is better for a small or early-stage company?
Often a hybrid. Small organizations may not have the headcount to support formal dual tracks yet, but can still recognize skill growth and lateral contribution informally while a ladder handles the core reporting structure.
