Loading...
hr

Career Lattice Design Guide

A multi-page guide for designing a career lattice with vertical, lateral, and cross-functional growth paths. Use it to define role families, progression criteria, and manager guidance in one place.

See it in MangoApps

Trusted by frontline teams 15 years of frontline software

Built for: Technology · Professional Services · Healthcare · Financial Services · Education

Overview

This Career Lattice Design Guide template is a multi-page internal site for documenting how people grow across your organization. It is designed for HR and People teams that need to explain role families, leveling, promotion criteria, lateral moves, and cross-functional transitions in a way employees can actually use.

Use it when your company wants more than a simple ladder. A lattice is useful when employees can grow by deepening expertise, taking on broader scope, moving into management, or shifting into adjacent functions without starting over. The template helps you organize that model into pages that are easy to browse: an overview page, role family pages, progression criteria, transition guidance, manager notes, and supporting resources.

Do not use this template as a vague culture statement or a one-page policy memo. It is not meant to replace compensation bands, performance review forms, or job descriptions. It works best when those systems already exist and you need a clear internal guide that connects them. If your leveling model is still unsettled, use the template to draft and compare options before publishing company-wide. If your organization is very small and growth paths are still informal, a lighter guide may be enough until roles stabilize. The goal is to make growth visible, consistent, and easier to discuss without forcing every employee into the same upward path.

Standards & compliance context

  • If the lattice influences promotion or pay decisions, keep the criteria documented and consistently applied to reduce the risk of subjective or uneven treatment.
  • For audience-restricted internal pages, make the site accessible under WCAG 2.1 AA so employees using assistive technology can navigate the guide.
  • If role requirements differ by location, include local policy notes so the guide does not conflict with jurisdiction-specific employment rules.
  • Avoid using the lattice as a substitute for formal job descriptions when legal or compensation processes require separate documentation.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

How to use this template

  1. 1. Start with the overview page and define the purpose of the lattice, the audiences it serves, and the role families it covers.
  2. 2. Add one page per role family or function and write the progression criteria, scope changes, and examples of expected work at each level.
  3. 3. Create dedicated pages for vertical, lateral, and cross-functional moves so employees can see how transitions work in practice.
  4. 4. Assign HR, functional leaders, and manager reviewers to each page so ownership is clear and updates do not stall.
  5. 5. Publish manager guidance, calibration notes, and related policy links so the lattice connects to promotion and performance processes.
  6. 6. Review the guide after promotion cycles or org changes and revise any criteria that managers are interpreting inconsistently.

Best practices

  • Write progression criteria as observable behaviors and scope changes, not as vague traits like leadership potential or strong communication.
  • Separate individual contributor and manager paths clearly so employees can compare growth options without assuming management is the only next step.
  • Use role family pages to show what changes at each level in autonomy, complexity, decision-making, and cross-functional influence.
  • Include examples of lateral moves that preserve seniority where appropriate so employees do not feel forced to restart when changing functions.
  • Keep manager guidance on the same site as the lattice so leaders can explain decisions using the same language employees see.
  • Link the lattice to performance review and promotion workflows so the guide reflects how decisions are actually made.
  • Review the language for consistency across pages so one function does not use a stricter or looser standard than another without explanation.

What this template typically catches

Issues teams running this template most often surface in practice:

Employees cannot tell the difference between a ladder and a lattice because lateral paths are mentioned but not explained.
Promotion criteria are written in abstract language that managers interpret differently across teams.
Manager expectations are missing, so employees know the framework exists but not how to use it in career conversations.
Role families overlap without clear boundaries, which creates confusion about which page applies to a given employee.
Cross-functional moves are described as exceptions instead of normal growth paths, so employees assume they are discouraged.
The guide is published once and never updated, causing it to drift away from actual leveling and promotion practice.
The lattice is disconnected from performance review forms, so employees cannot see how development work maps to advancement.

Common use cases

Engineering and Product leveling guide
A People team uses the template to define how engineers and product managers progress across levels, including scope, autonomy, and cross-functional collaboration. The guide helps managers explain why two employees at the same title may be evaluated differently based on role family criteria.
Customer support to customer success transitions
An operations leader documents how support specialists can move into success, implementation, or enablement without losing visibility into their growth path. The lattice clarifies which skills transfer and what new expectations apply after the move.
Healthcare administrative career paths
An HR team in a healthcare organization maps progression for schedulers, coordinators, and supervisors while accounting for site-specific responsibilities. The guide gives employees a clearer path to grow without leaving the department.
Professional services manager development
A services firm uses the template to show both delivery and people-management tracks, plus lateral moves into solution design or client strategy. This helps reduce the assumption that advancement only means managing a larger team.

Frequently asked questions

What does this career lattice design guide template include?

This template is a multi-page internal guide for defining how employees can grow vertically, laterally, and across functions. It typically includes role family pages, progression criteria, examples of lateral moves, and guidance for managers and employees. It is meant to be edited into your company’s own structure, language, and leveling model.

Is this template for a company-wide career framework or a single department?

It can support either, but it works best when you start with one department or function and expand from there. A company-wide lattice usually needs shared principles plus function-specific pages for engineering, product, operations, sales, or support. If your organization is still early in leveling, this template helps you pilot the model before rolling it out broadly.

How often should a career lattice guide be reviewed?

Review it whenever role expectations, org structure, or promotion criteria change, and schedule a regular cadence so it does not drift from reality. Many teams tie review to annual planning, compensation cycles, or promotion calibration. If the guide is not maintained, it quickly becomes a stale reference that managers stop using.

Who should own and maintain this guide?

HR or People Operations usually owns the framework, but functional leaders and managers should review the role-specific details. The best version has clear ownership for each page so updates do not stall in one central queue. If you have a talent team, they should coordinate consistency across departments.

How does this template help with lateral and cross-functional moves?

It gives employees a visible path beyond promotion by showing how skills transfer between roles and teams. That reduces the common problem of treating growth as only upward movement. The guide can also clarify what changes in scope, autonomy, and expectations when someone moves sideways or changes functions.

What are the most common mistakes when building a career lattice?

A common mistake is making the guide too abstract, with vague values instead of observable criteria. Another is copying a ladder model and calling it a lattice without defining lateral paths or transition support. Teams also run into trouble when manager guidance is missing, because employees then interpret the framework inconsistently.

Can this template connect to performance reviews or promotion workflows?

Yes, and it should. The lattice guide works best when it links to performance review criteria, promotion packets, calibration notes, and manager coaching resources. If those systems are disconnected, employees may understand the framework but still not know how it affects day-to-day decisions.

How do we roll this out without confusing employees?

Start with a clear overview page, then publish the most-used role families first and add the rest in phases. Pair the guide with manager training and a short employee announcement that explains how to use it. A phased rollout is easier to absorb than releasing every page at once with no context.

How is a career lattice different from an ad-hoc growth conversation?

An ad-hoc conversation depends on the manager’s memory and personal style, which creates uneven guidance across the company. A career lattice guide standardizes the language for growth, makes expectations visible, and gives employees a reusable reference. It is especially useful when you want growth decisions to be explainable and consistent.

Go deeper on the topic

Related concepts
  • A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
  • Human resources (HR) — increasingly called people operations, people ops, or simply "people" — is the organizational function responsible for the systems and...
Related guides

Ready to use this template?

Get started with MangoApps and use Career Lattice Design Guide with your team — pricing built for small business.

Get Started