Career lattice / career path frameworks

1. What Is the Career Lattice / Career Path Framework?

A career lattice (sometimes called a career path framework or career architecture for progression) is a structured approach for enabling non‑linear career growth—up, across, and diagonally—through a combination of role changes, capability building, and curated experiences. Unlike a traditional “ladder,” which implies a single vertical promotion path, a lattice recognizes multiple ways to grow: deepening expertise, broadening scope, shifting domains, leading projects, or managing people—often in alternating sequences over time.

Within Talent, HR & People‑Systems frameworks, a career lattice provides the common language and mechanisms for internal mobility, development planning, and transparent progression criteria. It sits on top of your job family architecture and compensation structure, linking roles and levels to capabilities, experiences, and learning so employees and managers can make informed moves that build both individual careers and enterprise capability.

In plain terms: the lattice shows people the many directions they can grow, the skills and experiences required, and the moves that matter—then makes those moves practical with programs, marketplaces, and pay rules that support mobility.

2. Origin and Background

Origin: While the idea of non‑linear careers predates it, the “career lattice” concept was popularized in the late 2000s and early 2010s by Deloitte’s research and publications (e.g., Cathy Benko and Molly Anderson’s “The Corporate Lattice,” 2010), which contrasted rigid ladders with flexible, multidimensional growth models. The approach has since been adopted widely as talent markets tightened, organizations flattened, and skills cycles accelerated.

Why it emerged: to reflect how work and careers actually evolve in modern organizations—cross‑functional projects, agile teams, dual career tracks, skill adjacencies, and frequent re‑skilling. Ladders alone couldn’t absorb demand for growth when promotion slots were scarce or when capability breadth was strategically critical.

3. How Career Lattice Frameworks Work

Effective lattice designs integrate three building blocks—structure, capability, and movement—into a coherent system.

Structural backbone (roles, levels, and streams)

• Job family architecture: A clean catalog of families, career streams (e.g., Individual Contributor, People Manager, Expert/Principal, Project/Program), and levels (e.g., IC1–IC7; M1–M4) with consistent leveling criteria (scope, autonomy, influence, knowledge, people leadership).
• Dual/tri‑track options: Parallel tracks for expert/IC and manager roles with equivalent status and pay bands, plus project/program leadership for those who lead through delivery rather than line management.
• Transparent progression criteria: Clearly articulated expectations per level/track (outcomes, behaviors, scope) so employees can see what “ready for next” looks like.

Capability and experience model (what to build and how)

• Capabilities and skills: A concise set of capabilities and priority skills per family+level, aligned to strategy (e.g., cloud architecture, regulatory fluency, stakeholder influence). Modern designs plug into a skills taxonomy and learning ecosystem.
• Experience pathways: Curated experiences (70‑20‑10) that accelerate readiness—rotations, cross‑functional projects, acting roles, customer exposure, turnaround assignments, scale transitions.
• Progression portfolios: A “mix of proof” (outcomes delivered, scope handled, capabilities demonstrated) that substitutes for time‑in‑role as the primary progression signal.

Movement mechanisms (how people actually move)

• Internal job marketplace: A platform/process advertising internal roles and gigs aligned to the architecture; candidates are matched by skills and aspiration; managers are accountable to release talent.
• Career maps: Visual lattice maps that show adjacent roles (upward, lateral, diagonal) with typical time/experience bridges.
• Compensation rules: Broad bands, clear guidelines for lateral moves (with/without pay adjustments), promotion criteria, and market‑premium policies—so moves are financially predictable and fair.
• Support infrastructure: Mentors/sponsors, career coaching, development stipends, and manager toolkits for career conversations.

Together, these elements make non‑linear growth real: people know the options, what it takes, where to find opportunities, and how moves affect pay; managers know how to develop and release talent; HR can measure movement and capability uplift.

4. When to Use Career Lattice Frameworks

Most helpful when:

• Your strategy requires faster skill evolution (digital, data, AI, regulatory) and broader enterprise perspective.
• Promotion slots are limited due to flatter structures, yet demand for growth and retention pressure are high.
• Internal mobility is sluggish; external hiring fills too many roles; re‑skilling costs are rising.
• DEI objectives include expanding access to pivotal experiences and reducing reliance on “tap on the shoulder.”
• M&A or operating model shifts require harmonized careers and movement across legacy organizations.

Especially powerful: Coupled with an internal talent marketplace, skills platform, and outcome‑linked learning that make lateral/diagonal moves visible and valuable.

Less suitable or potentially misleading: In very small organizations where role variety is limited; where compensation structures can’t support lateral progression; or if leaders won’t release talent. A lattice without enabling systems and cultural sponsorship becomes “career theater.”

5. How to Apply a Career Lattice: Step‑by‑Step

1. Anchor on outcomes and principles.

   Define what success looks like (e.g., internal fill rate for critical roles to 60%; pivotal moves per high‑potential talent 40% annually; time‑to‑productivity down 30%; representation in successor pools up 8 points). Agree principles: transparency, dual tracks, outcome‑based progression, market‑informed pay, manager accountability for exporting talent.

2. Confirm or build the structural backbone.

   Ensure you have a job family architecture with streams/levels and leveling criteria. If not, build a lightweight version for priority functions first. Map roles to grades/bands (job evaluation + market pricing) to enable predictable pay across moves.

3. Define capabilities, skills, and progression criteria.

   For each family+level:

   • List 5–7 capabilities and 3–5 priority skills aligned to strategy.
   • Write clear, outcome‑oriented progression criteria (“consistently delivers X outcomes at Y scope; demonstrates Z behaviors”), not tenure requirements.
   • Identify 3–5 high‑value experiences that accelerate readiness (e.g., customer P&L exposure, cross‑region launch, platform migration).
4. Design the lattice maps.

   Create visual career maps showing typical moves:

   • Upward within a stream (IC3 → IC4).
   • Lateral across families (Data Analyst IC3 ↔ Product Analyst IC3) with bridging experiences.
   • Diagonal (IC4 → M1 or IC4 Engineer → IC3 Product Manager) with bridging learning and coaches.

   Include pay guidance for each move type (e.g., lateral within band; diagonal with targeted adjustment if market‑priced differently).

5. Stand up movement mechanisms.

   Launch or strengthen:

   • An internal job/gig marketplace with skills‑based matching.
   • Rotations and secondments tied to succession and capability priorities.
   • Acting roles and coverage opportunities for leadership exposure.
   • Mentorship/sponsorship programs (especially for underrepresented talent) with clear expectations.
6. Align compensation and policies.

   Codify:

   • Promotion criteria and typical pay adjustments.
   • Rules for lateral moves (within‑band adjustments when scope/market differs; location differentials).
   • Premiums for scarce skills (e.g., cybersecurity) applied consistently to roles, not individuals.

   Publish a manager guide; avoid opaque exceptions.

7. Enable managers and employees.

   Provide:

   • Career conversation toolkits (assess strengths, aspirations, next move; agree experiences and learning).
   • Development planning templates that link capabilities to experiences and learning (70‑20‑10).
   • Access to curated learning paths aligned to lattice moves.
8. Pilot and iterate.

   Start with 2–3 functions (e.g., Engineering, Sales, Operations). Run a 12‑week pilot: publish maps, activate marketplace roles/gigs, track moves and satisfaction. Collect feedback; refine progression criteria, pay rules, and manager support.

9. Institutionalize governance and accountability.

   Create a Talent & Careers Council (CHRO, COEs, HRBPs, business leaders) that:

   • Prioritizes rotations/gigs tied to enterprise capability needs.
   • Monitors mobility, equity, and retention metrics.
   • Holds executives accountable for exporting talent (part of performance goals).
10. Measure and communicate impact.

    Publish quarterly metrics (internal fill rate, pivotal movement velocity, time‑to‑productivity, representation in successor pools, retention of pivotal talent, employee perception of career clarity). Share success stories to build momentum.

6. Example: Career Lattice in Action

Context: A 10,500‑employee global SaaS company faced rising attrition among mid‑career engineers and product managers. Internal fill for critical roles was 35%; promotion slots were scarce; managers hoarded talent. Strategy required more product/market breadth and cloud modernization skills.

Application:

• Backbone and capabilities: The company refined its job family architecture (IC1–IC7; M1–M4) and defined capability sets per family+level (cloud architecture, customer discovery, influencing across tribes).
• Lattice maps: Published maps showing common diagonal moves (e.g., IC4 Engineer → IC3 Product Manager; IC5 Engineer ↔ IC5 Architect) with bridging experiences (shadowing product discovery; customer immersion; platform migration leadership).
• Movement mechanisms: Launched an internal marketplace for 90‑day gigs (e.g., “lead SRE readiness for new region”; “customer discovery sprint”); created an 18‑month rotation (Engineering ↔ Product); instituted acting PM roles for IC5 engineers.
• Compensation rules: Codified lateral/diagonal pay guidance; introduced scarce‑skill premiums for SRE and security roles; clarified promotion criteria.
• Enablement: Manager toolkits; mentoring pairs for diagonal moves; learning paths on product discovery and cloud design.

Outcomes (nine months): Internal fill for critical roles rose to 58%; attrition among mid‑career engineers fell by 31%; 42% of high‑potential talent made a pivotal move; time‑to‑productivity for diagonals initially spiked then normalized after adding structured onboarding; representation of women in successor pools for product leadership increased by 7 points. Executive team made “exporting talent” a leadership KPI.

7. Strengths and Limitations

Strengths

• Retention and engagement: More avenues for growth without waiting for promotion.
• Capability agility: Accelerates re‑skilling and broadening through curated experiences and diagonal moves.
• Succession depth: Builds enterprise‑ready leaders with cross‑functional perspective.
• DEI impact: Transparent criteria and marketplaces reduce reliance on informal networks; sponsorship programs scale access to pivotal experiences.
• Business resilience: Internal mobility reduces time‑to‑fill and external hiring dependency for critical roles.

Limitations

• System complexity: Requires clean job architecture, clear pay rules, skills/learning infrastructure, and cultural shift.
• Manager resistance: Without incentives and norms, talent hoarding persists.
• Measurement and onboarding load: Diagonal moves need structured ramp‑up and coaching; otherwise productivity dips.
• Equity risk if poorly governed: Lateral moves without pay clarity can erode trust; unmanaged marketplaces can replicate bias.

8. Common Pitfalls (and How to Avoid Them)

• “Lattice theater.”
  What goes wrong: Nice maps; no actual movement.
  Avoid by: Launching an internal marketplace and rotations; setting movement targets; tracking pivotal moves and holding leaders accountable.
• Vague progression criteria.
  What goes wrong: Perception of favoritism; stalled progression.
  Avoid by: Outcome‑based criteria per level and family; portfolio of proof; cross‑functional calibration.
• Pay ambiguity on lateral/diagonal moves.
  What goes wrong: People avoid moves or feel penalized.
  Avoid by: Publishing clear pay rules (within‑band adjustments; market premiums; location differentials) and applying consistently.
• Manager hoarding.
  What goes wrong: Mobility stalls; cynicism grows.
  Avoid by: CEO‑backed norms, movement KPIs in leader goals, and monthly talent brokerage forums.
• Over‑indexing on moves vs. mastery.
  What goes wrong: Churn without depth; weakened expert pipelines.
  Avoid by: Valuing expert tracks equally; recognition and pay parity; mastery badges and communities of practice.
• Unstructured diagonal transitions.
  What goes wrong: Performance dips; rework.
  Avoid by: 90‑day plans, mentors/sponsors, and targeted learning before and during the move; staged scope increases.
• Bias in opportunity access.
  What goes wrong: Underrepresented talent misses pivotal experiences.
  Avoid by: Transparent marketplaces, sponsorship programs, bias checks on applicant pools and selections, and outcome monitoring.

9. How Career Lattices Relate to Other Frameworks

• Job Family Architecture (JFA): The lattice rides on JFA’s families, streams, and levels; JFA provides the structural language, the lattice provides the movement and development logic.
• Job Evaluation (Hay/Mercer/WTW) & Compensation: Job evaluation and market pricing set grades/bands; lattice pay rules apply those structures consistently across lateral/diagonal moves.
• Skills‑Based Organization & Internal Marketplaces: Skills taxonomies and marketplaces operationalize lattice moves by matching people to gigs and roles based on capabilities and aspiration.
• 9‑Box (Performance × Potential): Identifies who is ready for pivotal moves; lattice provides the pathways and experiences to develop potential into readiness.
• Succession‑Planning Pipeline: Lattice rotations, acting roles, and cross‑functional moves are the development engine that advances successors across readiness horizons.
• Ulrich/Bersin High‑Impact HR Models: COEs design the lattice, HRBPs orchestrate moves with business leaders, Shared Services and digital platforms enable marketplaces and learning at scale.
• DEI Frameworks: Lattice transparency and sponsorship expand equitable access to high‑value experiences and roles; pair with metrics to prevent adverse impact.

10. Key Takeaways

• Career lattices turn growth from “promotion or nothing” into many routes—upward, lateral, and diagonal—anchored in outcomes, capabilities, and experiences.
• They require a clean job backbone (families, levels), transparent progression criteria, enabling mechanisms (marketplace, rotations, mentors), and clear pay rules.
• Done well, lattices lift retention, internal fill rates, capability agility, and DEI by democratizing access to pivotal experiences.
• Beware theater: measure movement and impact, hold leaders accountable for exporting talent, and support diagonal transitions with structured onboarding and learning.
• Treat the lattice as a living system tied to strategy—refresh capabilities and experiences as your business evolves.

11. FAQs About Career Lattice / Career Path Frameworks

How is a career lattice different from a career ladder?
A ladder is primarily vertical; the lattice adds lateral and diagonal moves across functions and tracks (expert, manager, project). It emphasizes capability and experience portfolios over tenure, expanding options for growth when promotion slots are limited.

Do lateral moves mean no pay growth?
Not necessarily. With broad bands and clear rules, lateral moves can include within‑band adjustments when scope or market differs. The key is consistency and transparency—avoid ad hoc exceptions that erode trust.

How do we measure success?
Track internal fill rates for critical roles, pivotal movement velocity (especially for high‑potential and underrepresented talent), time‑to‑productivity for moves, retention of pivotal talent, and employee perception of career clarity. Link moves to capability outcomes (e.g., cloud certifications, customer experience metrics).

Can small organizations use a lattice?
Lightly. Use a simplified architecture and focus on curated experiences (projects, acting roles) and transparent internal postings. As you scale, add a marketplace and more formal pay rules.

How do we avoid manager hoarding?
Set norms and incentives: require backfills to be posted; include “exported talent” in leader goals; run monthly talent brokerage forums; celebrate leaders who grow and export talent.

What about expert tracks—do they stall without people management?
Design expert/IC tracks with equivalent status and pay, clear mastery criteria, and recognition. Provide leadership opportunities through communities of practice, standards ownership, and strategic programs.

How long does implementation take?
You can pilot in 12–16 weeks in priority functions: refine architecture, publish maps, launch a marketplace for gigs, and codify pay rules. Enterprise rollout with learning integration and governance typically takes 2–3 quarters.

How do we ensure equity?
Use transparent criteria, open marketplaces, sponsorship programs, and bias checks on applicant pools and selections; monitor outcomes by demographic and intervene where disparities appear.