Career ladder
What you deliver. How you act. What you build.
Most career ladders are boxes nobody reads. What actually moves a career is obvious to everyone who works with you: the work you deliver, how you behave when it's hard, and what you build in other people.
The evidence test
If you're working at a level, you and your manager can both name three recent examples, without looking anything up. If you can't, you're not there yet. If you both can, it's time to talk.
Read this first
Three truths about promotion, for both sides of the desk.
Doing the job well isn't the promotion.
It's the entry ticket. Promotion is evidence that you're already working at the next level, consistently, across all three strands.
The weakest strand sets your level.
Brilliant delivery with no building doesn't make you level 4. Your level is the highest one where all three strands are true most weeks.
Some of it is outside both of you.
Budget, headcount and roles exist or they don't. A good manager will be honest about that, and won't promise what they can't deliver.
Ready, but the money isn't there? What to say, and what not to promise →
Three strands
Deliver
What do you deliver, and who benefits?
Act
How do you behave, especially when it's hard?
Build
What do you build in other people?
Five levels, and the gaps between them
Each level widens who benefits from your work. The gaps are where careers stall: read them as closely as the levels.
The gap to ShapingFrom running things well to changing what the organisation does.
The trapRunning a bigger version of the same thing. The step is changing direction and building what will outlast you.
If you're stepping upBring a point of view on where things should go, and the coalition to make it happen.
If you manage themInvolve them in strategy before it's decided, not after. Ask them to build their successor.
Shaping
What the organisation does next
In software: Principal engineer, head of or director
Changes the direction of the organisation, not just its output.
The person others go to when it's hard. Says what needs saying.
Builds teams and a culture that outlast them.
The gap to MultiplyingFrom delivering through yourself to delivering through others.
The trapBeing the expert everyone relies on. If the work stops when you're away, you've become a single point of failure, not a Multiplier.
If you're stepping upGive away your best work to someone else, and measure yourself by what they deliver.
If you manage themPut them on cross-team work where they can't do it alone. Watch who they lift.
Multiplying
Outcomes across teams, through others
In software: Staff engineer or engineering manager
Delivers through other people, across team boundaries.
Sets standards other people copy. Calm and fair under pressure.
Grows other leaders. Removes single points of failure, including themselves.
The gap to OwningFrom doing your work to owning an outcome.
The trapDoing more of the same, faster. Being a brilliant Doer isn't Owning: the step is caring whether the outcome landed, not just whether your tasks are done.
If you're stepping upAsk for an outcome, not a task list, and make the hard calls on it. Start helping one other person.
If you manage themGive them a problem, not a plan. Let them get it slightly wrong, and coach rather than rescue.
Owning
An outcome for the team
In software: Senior engineer
Owns an outcome, not just tasks, and gets it over the line.
Raises hard truths, challenges respectfully, holds the bar when it's inconvenient.
Mentors one or two people and improves how the team works.
The gap to DoingFrom needing help to needing no chasing.
The trapThinking speed is the step. It isn't: reliability is. Finishing what you start, without reminders, is what gets noticed.
If you're stepping upOwn one piece of work end to end, and flag problems before anyone asks.
If you manage themStop checking in daily on one well-defined piece of work, and see what happens.
Doing
Your own work, end to end
In software: Engineer
Delivers their own work reliably, from start to finish, without chasing.
Owns mistakes, flags problems early, does what they said they'd do.
Helps the people next to them when asked.
Learning
Your own tasks, with support
In software: Junior engineer
Finishes well-defined work to a good standard, with help.
Asks for help early, takes feedback well, keeps small promises.
Builds their own skills, fast.
The matrix: graduate to director
The same strands, as a practical grid. From Lead, careers split into a specialist track and a management track. Both are senior; neither is a consolation prize.
| Everyone · L1Graduate | Everyone · L2Associate | Everyone · L3Senior | Specialist · L4Lead / Staff | Specialist · L5Principal | Management · L4Manager | Management · L5Director | |
|---|---|---|---|---|---|---|---|
| Scope | Tasks | Features or pieces of work | A whole outcome for the team | Outcomes across teams | Technical direction for the organisation | A team, and its results | Several teams, a function, a budget |
| Autonomy | Guided daily | Guided weekly | Sets own approach | Sets approach for others | Sets direction others follow | Sets team priorities with their manager | Sets priorities for the function |
| Deliver | Finishes defined work well, with help | Delivers own work end to end without chasing | Owns an outcome and gets it over the line | Delivers through others, across teams | Changes what the organisation builds | The team delivers reliably, without heroes | The function delivers what the business needs |
| Act | Asks early, takes feedback well | Owns mistakes, flags problems early | Raises hard truths, holds the bar | Sets standards others copy | The person others go to when it's hard | Clear, fair and consistent under pressure | Shapes culture; makes the calls nobody else wants to |
| Build | Builds own skills, fast | Helps peers when asked | Mentors one or two people | Grows other leaders; removes single points of failure | Builds capability that outlasts them | Grows every person on the team; hires well | Builds managers, and the next leadership team |
| Typical evidence | Finished work, good feedback | Delivered work, few surprises | An outcome they owned and landed | Others delivering because of them | A direction the organisation took | Team results, retention, growth | Function results, successors in place |
Titles vary by organisation. Use this as a starting point: agree with your manager what each cell means in your team, with real examples.
In other industries
Titles change. The strands don't. Many ladders split into specialist and management tracks around level 3 or 4.
| 01 Learning | 02 Doing | 03 Owning | 04 Multiplying | 05 Shaping | |
|---|---|---|---|---|---|
| Healthcare | Healthcare assistant | Staff nurse | Senior staff nurse | Ward manager | Matron |
| Accountancy | Trainee | Senior associate | Manager | Senior manager | Partner |
| Manufacturing | Operator | Skilled technician | Team leader | Shift manager | Plant manager |
Use it
Your career is yours to drive. A good manager opens doors and pushes you through them. Nothing on this ladder comes for free.
Place yourself honestly
Read each strand from the bottom. Your level is the highest one where all three strands are true most weeks, not your best week.
Collect the evidence
Three recent examples per strand. Write them down. They're your case, and your manager's ammunition.
Managers: use the same page from the other side. If you can't name three examples for someone, either they're not there yet, or you're not looking. How to know you're a good manager →