Career development and growth paths

Career development means understanding where a person wants to go and creating the experiences that get them there, which takes more than conversations. Its instrument is the one-on-one, the recurring, protected meeting that belongs to the report and is kept free of status updates. It is where blockers, frustrations and the earliest signs of disengagement come up, provided someone is listening. Its structure is the growth path: levels and tracks that make "what does the next level look like?" concrete and comparable. That includes the senior individual-contributor track, which lets strong engineers grow without leaving the work, and the honest choice between that track and management. The competency matters because retention is largely decided here, months before anyone resigns. A growth path that exists only in the manager's head gets handed out according to the manager's attention, which is a different thing from handing it out fairly. The examinations test it through the early promotion request, the strong engineer who is bored, the ambitious manager who wants your job, and the succession call with one seat and two ready people.

1. The one-on-one belongs to the report. Status can go through other channels. This meeting is for what does not come up any other way: what is in the way, what they want, what has changed. Cancelling it whenever things get busy signals exactly the wrong priority.
2. Growth is built from experiences. Conversations set the direction. What moves a career is stretch assignments, real responsibility and visible work, and a development plan with no experiences in it is a wish.
3. Make the next level concrete and comparable. Ladders or competency matrices describe what each level looks like. A promotion then becomes a judgment against a shared description, instead of a measure of how assertive the manager is in the calibration room.
4. Promotion follows demonstrated judgment, not tenure or desire. The evidence is that the person already exercises the next level's judgment on real stakes. Promoting someone to keep them, or as a reward for waiting, teaches the wrong lesson to everyone watching.
5. The senior individual-contributor track is a real path, and management is not a prize. The choice between them turns on the work the person wants to do. A manager's job is to help them make it honestly, which includes describing what management involves day to day.
6. Watch for disengagement early. People seldom leave suddenly. Withdrawal, cynicism and a stopped flow of ideas show up first, in one-on-ones, to a manager who is paying attention.

Career development is practitioner territory. The models below are widely adopted and clearly attributed. None is a controlled finding, so the unit grades them all as practice.

The one-on-one as the report's meeting practice

In Andrew S. Grove, High Output Management (1983), Grove treats the one-on-one as the recurring activity that does the most for a manager's output. Its agenda belongs to the subordinate, and its purpose is for both people to learn about the work and the person. The practical consequences have held for four decades. The meeting is protected and regular, the report sets much of the agenda, and the manager listens more than they talk. The familiar failure has held for just as long: it turns into a status meeting the moment the manager needs one.

Growth ladders and competency matrices practice

These are explicit descriptions of what each level looks like for each competency. They make progression concrete and let promotion decisions be compared across people and teams. Camille Fournier, The Manager's Path: A Guide for Tech Leaders Navigating Growth and Change (2017) sets out the engineering-management version, walking through the arc level by level. A ladder describes what is expected and sets no timetable. It decays into collecting checkboxes when levels are treated as tenure milestones instead of demonstrated judgment, and it is only as fair as the calibration that applies it.

The Staff+ track practice

This is the senior individual-contributor path (staff, principal and beyond), treated as a career of equal standing with management. Will Larson, Staff Engineer: Leadership Beyond the Management Track (2021) and Tanya Reilly, The Staff Engineer's Path: A Guide for Individual Contributors Navigating Growth and Change (2022) describe it from the inside. Two ideas from that literature matter to managers. The track has several distinct archetypes, so "senior engineer but more so" does not describe it. And the invisible coordinating work that holds teams together, which Reilly calls glue work, tends to be done by people who then go unpromoted for it. A manager who cannot describe the track cannot offer it honestly.

Readiness practice

This is a rule this standard adopts from the literature above and from practice, with no single named model behind it. Someone is ready for a larger scope when they already exercise that scope's judgment on real stakes, before they hold the title. Tenure, ambition and how badly the person wants it do not count as readiness. The rule matters most at succession, where the pull toward whoever has waited longest or asked loudest is strongest.

The protected one-on-one

It runs weekly or fortnightly, is never cancelled for a status need, and takes the report's items first. The manager keeps a running note for each person (what they said they wanted, what they said was in the way, what changed) and reads it before each meeting. The note is what makes a pattern visible. Three meetings in a row with no ideas offered is a signal that no single meeting would show.

The growth conversation, quarterly

This is separate from the weekly one-on-one and from the review cycle. It asks where the person wants to be in two years, what the next level would require of them, and which experience in the coming quarter moves them toward it. It produces one concrete assignment, and no plan document.

Answering a promotion request

The manager answers with evidence against the level description: where the person already shows the next level's judgment, where they do not yet, and what would show it. A yes given to keep someone is wrong, and so is a no without reasons. If the answer is not yet, the path is specific enough for the person to watch the gap closing.

Describing management honestly

When an engineer is weighing management, the manager describes the job as it is (the meetings, the ambiguity, the distance from the code, the accountability for other people's work) and asks what the person wants to spend their days doing. The strongest engineer, having said they do not want to manage, is not pushed into it. A reluctant manager is worse for everyone than an empty seat.

Promotion fairness across teams

Where several teams share a ladder, promotions go through shared criteria, written evidence and a calibration that compares people against the description and keeps their managers out of the comparison. The check is easy. If one team's promotions are consistently faster, either its people are consistently stronger or its manager is consistently more assertive, and the second is more common.

At team scope the object is one person's growth and next step, and it happens in the one-on-one. At organisational scope it becomes the growth paths available across several teams and who is getting them: promotion mechanics that are fair across managers, moves between teams, and stretch roles that exist only at department scale. At executive scope the object is the career architecture itself (levels, tracks and the leadership pipeline) and succession as a property of the structure. Every key role, the executive's own included, has a ready or nearly ready successor, and readiness is judged on demonstrated next-level judgment. Developing the managers who report to you is a competency of its own, PL-6 Leading through leaders; the pattern is in How Judgment Scales.

• Holds one-on-ones consistently, lets the report set much of the agenda, and listens more than they talk. team
• Builds growth from real experiences: the stretch assignment, the visible piece of work, the responsibility not yet held. team
• Answers a promotion request with evidence, a named gap and a path. team
• Describes the senior individual-contributor track and management honestly, and lets the person choose the work they want. team
• Recognises withdrawal, cynicism and a stopped flow of ideas as early signals. team
• Failure mode: cancelling one-on-ones under pressure. team
• Failure mode: hijacking the one-on-one for status. team
• Failure mode: discussing growth only at promotion time. team
• Failure mode: promoting to retain, or promoting for waiting.
• Failure mode: drafting a reluctant engineer into management because it is the only visible path to more pay or status.
• Creates growth paths across teams (moves, stretch roles, the senior track) and sees who is and is not getting them. org
• Runs promotion fairness across teams with shared criteria, evidence and calibration. org
• Decides compensation on value and fairness. Fixes an underpaid engineer's pay because it is wrong, whether or not they threatened to leave, and corrects a package that inverts a tenured colleague's through the compensation process, honestly. org
• Failure mode: letting each team invent its own promotion bar, so that each team's ceiling is set by its manager's assertiveness. org
• Failure mode: the reactive counter-offer, which teaches everyone that threats work and seldom keeps anyone for long. org
• Failure mode: a director who hoards strong engineers and blocks internal moves to protect local output, when talent belongs to the organisation. org exec
• Designs the career architecture (levels, tracks, the leadership pipeline) and reads it by what it produces. exec
• Makes succession an explicit, non-optional expectation of every senior role, including their own. exec
• Judges readiness by demonstrated next-level judgment on real stakes, not tenure or ambition. exec
• Tells the runner-up for a senior seat the truth about their path, invests in it in earnest, and accepts they may leave. exec
• Failure mode: inventing a title to avoid the succession conversation. exec
• Failure mode: a pipeline one name deep, and critical initiatives that wobble when one leader is courted by another company. exec
• Failure mode: equating readiness with tenure, or with how much someone wants the role. exec
• Failure mode: counter-bidding for a leader whose growth was neglected for years. exec

The person's ambition versus the evidence. A talented person wants the next level before they consistently show its judgment. Saying no risks losing them, and saying yes teaches the team that asking works. The way through is a specific path: a no that names exactly what would turn it into a yes, and an assignment that lets them show it.

Retention versus fairness. The counter-offer keeps one person this quarter and distorts equity for everyone who did not threaten to leave. The only version that holds up is fixing real underpayment because it is wrong, before anyone uses it as a bargaining chip.

Local output versus organisational growth. A manager loses their strongest engineer to an internal move and the team's delivery dips. The organisation gains someone who grows and stays. Talent belongs to the organisation, and a manager who blocks the move is optimising for the wrong thing. The dip is still real, and the judgment lies in how the team absorbs it.

Ladders versus judgment. A detailed ladder makes promotion fair and comparable, and it also invites people to tick its boxes. The answer is to treat the ladder as a description of judgment to be demonstrated, never as a list of activities to complete, and to say so in every promotion conversation.

Honesty versus hope. The runner-up for a senior seat, the engineer who will not reach the next level on this team, the manager who wants a role that is not coming: each is owed the truth, and the truth may cost the relationship or the person. Manufactured hope costs more later, and everyone notices it.

An engineer who has been on the team for ten months asks their manager for promotion to senior. They are talented and fast, and have shipped two features that mattered. The manager's honest reading is that the engineer does not yet consistently show senior judgment. They still need scope handed to them, they have not led anything involving another team, and in design reviews they are sharp about their own code and quiet about everyone else's. Twice, the engineer has mentioned a friend at another company who was promoted at the one-year mark.

There are two easy answers. One is to approve the promotion to keep a talented person. The other is to decline with "not yet" and a vague reference to time. The first teaches the team that promotion follows asking and tenure. The second teaches this engineer nothing and leaves them concluding that the manager is the obstacle.

The manager answers with the level description. In the one-on-one they acknowledge the growth in specific terms (the two features, the pace, the quality of the engineer's own work) and then go through the senior description next to the evidence. Senior engineers define their own scope, lead work that crosses a team boundary, and raise the quality of other people's work through review. On the first two there is no evidence yet, because the engineer has not had the opportunity. On the third the evidence points the other way. The manager says plainly that the answer is not yet, and that the reason is the evidence and has nothing to do with time served.

The manager then builds the path out of experiences instead of advice. The engineer gets the lead on an upcoming change that touches a neighbouring team's service, with the manager's support at the boundary and a clear expectation that the engineer defines the scope. They are asked to review two pull requests a week from outside their own area and to put the feedback in the review itself instead of giving it privately. The two agree a date three months out to look at the evidence again, and the manager says what would make the answer yes.

The engineer may still leave for the company where the friend was promoted. The manager has judged that a promotion the engineer cannot yet sustain would cost them more than the risk of their leaving costs the team, and has given them an honest path and the chance to walk it. The manager neither promotes to retain nor declines without giving the engineer something to act on.

• PL-1 Delegation, ownership, and decision rights: the stretch assignment as delegation, with scope matched to capability plus a deliberate stretch.
• PL-6 Leading through leaders: developing the managers who report to you, and the leadership pipeline as a system.
• CC-2 Coaching versus directing: coaching as the form growth takes when the goal is judgment.
• CC-4 Motivation, recognition, and sustainable pace: motivation, and the early signals of disengagement the one-on-one exists to catch.
• CC-3 Inclusive practices and equitable opportunity distribution: who gets the stretch work and the visibility, and distributing growth paths fairly.

1. Why should the one-on-one belong to the report, and where do the earliest attrition signals appear?
   Answer

   Status can go through other channels. What cannot (blockers, frustration, disengagement) only comes up in a meeting the report controls. The earliest signals are withdrawal, cynicism and a stopped flow of ideas, which show across several one-on-ones to a manager who keeps notes.
2. A talented engineer asks for promotion before consistently showing the next level's judgment. What is the response, and what are the two failures?
   Answer

   Acknowledge the growth, go through the level description against the evidence, name the gap specifically, and build a path from real experiences with a date to look again. The two failures are promoting to retain and declining without giving the person anything they can act on.
3. What distinguishes a real senior individual-contributor track from "senior engineer but more so"?
   Answer

   Distinct archetypes with their own scope and influence, equal standing with management, and recognition for the coordinating and quality-raising work that otherwise goes unrewarded. A manager who cannot describe the track cannot offer it honestly.
4. An engineer holds a competing offer and your manager wants to match it. What should the decision turn on? org
   Answer

   Value and fairness. If the person is underpaid, fix it because it is wrong. If they are not, a reactive match teaches everyone that threats work and distorts equity for those who did not threaten. Retention bought under duress seldom lasts.
5. One team's promotions are consistently faster than the others'. What are the two explanations, and which is more common? org
   Answer

   Either its people are consistently stronger or its manager is consistently more assertive in calibration. The second is more common, and shared criteria with written evidence are the check.
6. What is the strongest signal that someone is ready for a larger scope, and what are two signals that are often mistaken for it? exec
   Answer

   That they already exercise the larger scope's judgment on real stakes. Tenure and ambition are the usual substitutes, and neither is evidence.
7. Two directors are ready for one vice-president seat. What do you owe the one who does not get it? exec
   Answer

   The truth about their path, real investment in it, and acceptance that they may leave. Inventing a title to avoid the conversation weakens the organisation and deceives nobody.
8. What is the quiet measure that an executive's leadership development is working? exec
   Answer

   Decisions that used to need the executive are made well without them, and the leaders they developed are developing leaders of their own.

• Andrew S. Grove, High Output Management (1983): the one-on-one as the report's meeting; managerial leverage.
• Camille Fournier, The Manager's Path: A Guide for Tech Leaders Navigating Growth and Change (2017): the management career arc, level by level; ladders.
• Will Larson, Staff Engineer: Leadership Beyond the Management Track (2021): the senior individual-contributor track and its archetypes.
• Tanya Reilly, The Staff Engineer's Path: A Guide for Individual Contributors Navigating Growth and Change (2022): senior individual-contributor leadership; glue work.