Most teams run without a career ladder. They have job descriptions that explain the role and job titles that signal seniority, but nothing that explains what excellent looks like at each level or what it actually takes to move from one to the next. The result is promotion conversations that feel arbitrary, career conversations that go in circles, and talented people who leave because they cannot see a path forward on your team.
When someone asks “what do I need to do to get to the next level?” you should be able to give them a concrete answer. A career ladder makes that possible.
Why most teams skip it
Writing a career ladder sounds like an HR project rather than a management priority. Most managers file it under important-but-not-urgent and it never gets done. Instead, promotion decisions rely on gut feel, internal comparison, or criteria borrowed loosely from another company. The standards shift depending on who is asking and who is deciding. People notice, and trust erodes quietly over time.
Without a career ladder
Criteria unclear. Decisions feel personal.
With a career ladder
Clear expectations. Honest conversations.
- Clarity for everyoneA career ladder removes ambiguity about what each level means. Everyone can read the same document, compare it honestly against where they are today, and have an informed conversation about the gap. No more guessing what the manager actually wants to see.
- Fairer promotionsDecisions made against defined criteria are harder to challenge and easier to defend. When the same standard applies to everyone, the conversation moves from opinion to evidence. People may still disagree with an outcome, but the basis is shared and transparent.
- Sharper developmentWhen you can point to specific expectations for the next level, development conversations become concrete. Instead of vague encouragement, you can identify exactly which behaviours and skills need work and build a plan around them.
- Better retentionPeople leave when they feel stuck or overlooked. A clear ladder shows that progression is possible, the path is visible, and the manager is invested in helping them get there. That visibility alone changes how people think about their future on the team.
What a career ladder should contain
A career ladder is not a job description. Job descriptions define the responsibilities of a role. A career ladder defines the levels within it and what distinguishes each from the next. The most useful ladders cover a small number of dimensions and describe each one at every level in observable, specific terms rather than a list of virtues.
Example: Engineering Career Ladder
Simplified example. Adapt dimensions and labels to your context.
- ScopeWhat is the size and complexity of the problems this person owns independently? A junior handles well-defined tasks with close guidance. A senior works across a whole problem space without needing their boundaries set for them.
- ImpactWhere does the work have effect? A junior improves their own output. A senior improves the team. A lead shapes outcomes across teams or the wider organisation. This dimension scales naturally and makes the differences between levels easy to see.
- BehavioursHow does the person work with others? What does communication, collaboration, and leadership look like at this level? Behaviours are often the hardest dimension to write, but the most important - they are visible every day and do not require a specific project milestone to assess.
- Technical depthFor technical roles, add a dimension for the expected expertise at each level. Keep the description at the right altitude. You are capturing what is expected of someone operating well at the level, not listing every possible skill they might need.
Aim for three or four dimensions, not ten. More dimensions dilute the signal and make the document unwieldy to use. If a section is not usefully distinguishing between levels, remove it.
Writing levels that make sense
The hardest part of writing a career ladder is making each level distinct without resorting to vague language. “Demonstrates strong communication skills” appears at every level of every career ladder ever written, and it means nothing. The goal is to describe what each level looks like in practice, not to list desirable qualities. Use observable behaviours and real-world examples wherever you can.
Vague vs specific
Vague
“Good communicator who collaborates well with others.”
Specific
“Flags blockers to the team before they cause delay. Initiates a short sync when async is not moving fast enough.”
Vague
“Takes ownership and shows leadership.”
Specific
“Scopes projects end-to-end, surfaces trade-offs before they become blockers, and drives delivery without the manager tracking progress.”
- Describe behavioursAvoid adjectives like "proactive", "driven", or "collaborative". Describe what a person at that level actually does. "Communicates proactively" is vague. "Sends a weekly update without being asked and flags risks before they escalate" is something you can observe and evidence.
- Focus on impactDo not list specific tasks - those belong in a job description. Describe the scale and nature of the impact expected at each level. Impact scales naturally across levels and stays relevant even as the day-to-day work changes over time.
- Distinguish levelsRead across the levels in one dimension and ask: could someone mistake a mid for a senior? If the descriptions blur together, sharpen the differences. Each step up should represent a meaningful increase in scope, autonomy, or influence - not just more of the same.
- Test against peopleBefore sharing widely, apply the draft to people you know well. For each person, read the ladder and ask: does it correctly identify their level? If it consistently places people in the wrong band, the writing needs adjustment rather than the people.
Putting the ladder to work
A career ladder is only as useful as the conversations it enables. Publishing a document and filing it away changes nothing. The goal is to weave it into the work you are already doing: one-to-ones, development plans, and promotion cases.
Where the career ladder shows up
Use the Targets feature in Manager Toolkit to set development milestones tied to next-level criteria and review them alongside other goals in your regular catchups. When a target is met, it becomes a piece of evidence in a future promotion case.
- Use it in 1:1sPick one dimension per fortnight and ask the person for a recent example of where they are operating at that level. This keeps the ladder alive without turning every catchup into a formal review. The examples accumulate into a bank of evidence over time.
- Ground promotionsWhen writing a promotion case, map evidence directly to the criteria in the ladder. Evidence that lands cleanly on the relevant criteria is far more persuasive than a general account of contribution or tenure, and it is much easier to defend in calibration.
- Share it openlyMake the ladder available to the whole team, not just to people who ask. When everyone can see the same document, levels stop being a mystery and start being a shared reference. This reduces the politics around promotion and helps quieter team members advocate for themselves.
- Revisit it annuallyLadders go stale as the organisation evolves. Review the document once a year and update descriptions to reflect how the team and its context have changed. Involve the team in the review so it remains a shared artefact rather than something imposed from above.
Frequently asked questions
Set clear development targets for every level
Track progress against your career ladder in regular catchups. Free to start.