Photo by Mert Kahveci on Unsplash

A few weeks ago, I had the first genuine career conversation of my professional life.

I told my director that I intended to keep developing toward the most senior individual contributor levels, and that I had been politely declining recruiter interest in director roles for some time. He didn’t push back. Instead, he gave the choice a name: “Path B.” And he noted, correctly, that I had chosen it on purpose.

The label stayed with me. Not because it was wrong – I’ve come to learn it’s the standard language – but because of everything packed inside it.

Path B. The alternate route.

The designation implies a Path A, and it implies which one is which. In the corporate imagination, the primary road runs through management: you do the work, then you lead the people who do the work, and you keep climbing until the work itself is a rumor several floors below you. Path B is what’s left over. The road for people who declined, or stalled, or never quite wanted it.

I want to explain why that framing is wrong, though structurally more than defensively. The misunderstanding isn’t really about job titles. It’s about a deeper assumption most organizations never examine: that professional growth must eventually become authority over people.

First, though, I should be honest about where my own choice comes from.

Years ago, at a former employer, I stood at the front of a large room, flanked by other managers and senior managers, and helped deliver a mass-layoff notice (under the WARN Act) to a couple hundred people at a time. We did it in groups. The reasons the layoffs became necessary don’t matter anymore; the reasons never reach the people in the chairs anyway. At the time, I directly led a small team of analysts and supported several others across the region.

I walked into that room feeling numb, and I walked out feeling guilty.

The business logic of the decision was sound in the way business logic usually is, and it answered none of the questions the people in that room were actually asking. The main one was simple: What do we do now? I had no answer that mattered.

It would be easy, and possibly flattering, to say I chose the individual contributor path solely to escape that kind of moment; that I saw the moral weight of managing people and set it down. But that’s not what happened, and it’s not a claim that survives scrutiny.

I didn’t choose a path without responsibility. I chose a different form of it.

The Ladder We’re Shown

We’ll begin with the path that everyone already knows.

You are hired to perform a task. You become reliable at it. Reliability earns you supervision of others performing the same task, and supervision matures into management: hiring, evaluating, developing, and sometimes exiting the people responsible for execution. Perform well there, and you reach the director tier, where the job changes character.

You are no longer managing the work or even the workers, and instead, you are translating strategy into coordinated execution, entrusting your managers to ensure completion by their teams.

From there, the pattern is consistent all the way up. The organization beneath you grows in strong correlation with your distance from any task your success will be measured on. Your performance becomes aggregate: output, cost, retention, risk, or growth – all ultimately some expression of return on investment, whatever name it wears locally. Are you completing enough of the right things, well enough, to justify the budget entrusted to you?

Beyond that, the work becomes shaping strategy itself, and then perception, both inside the company and outside it.

It’s fashionable to mock this progression, to joke about executives who “don’t do anything” – but I find that response lazy, and think it misses the point. Senior managers absolutely do something; what they do is design and direct collective action. Their craft is the organization itself, evident in its priorities, resource allocation, and accountability structures. It is real work, and when it is done badly, everyone beneath it pays.

The problem is not the ladder. The problem is that we usually present it as the only ladder; as though the natural fate of every capable person is to eventually stop doing the thing they were good at and start owning the people who do it. That presentation is so universal that most professionals cannot describe what senior growth looks like anywhere else.

Which brings us to the ladder nobody draws.

The Ladder Nobody Draws

The individual contributor path begins, deceptively, in the same place: you are hired to complete a specific set of tasks and serve a specific function. For the first few years, the two paths are indistinguishable. Then the IC path changes shape, and it does so quickly, in a way almost no onboarding deck, career framework, or mentorship conversation ever prepares people for.

The unit of your value changes.

Early on, you complete the work. Then you become the person others find when the work turns difficult. Then you begin improving the way the work itself is performed. Not just your work, the work.

Do you support a system that supports order entry? Do you write the queries that underlie a company’s reports? Then somewhere along the line, your fingerprints start appearing on processes you’ve never personally touched, in departments you’ve never visited. Eventually you are establishing patterns, standards, and architectural decisions that shape work done by people you will never meet, on systems that will outlive your tenure.

The progression, compressed: task, then workflow, then team, then function, then enterprise. At each stage, the question your organization is implicitly asking of you changes. It stops being “how much can you complete?” and becomes “how far does your judgment reach, and how long does it hold?”

Here is the version I give people when they ask what senior IC growth actually means. A junior contributor solves a problem. A strong senior contributor solves recurring classes of problems. The most senior contributors change the environment so that entire categories of problems become easier to solve, or simply cease to exist.

Nobody throws a party for the outage that never happened or the integration that didn’t need six months of rework, which is part of why this path stays invisible. Its best outcomes are non-events.

What makes this growth difficult, and what makes it growth at all, is that it must be accomplished without the instruments of hierarchy. Which is where the two paths stop being variations of each other and become genuinely different disciplines.

The Radius of Judgment

Both paths, followed far enough, pose the same question: as your ability grows, through what mechanism will you allow it to affect the world around you?

The management path answers primarily through people. Managers scale execution. Their instruments are coordination, prioritization, budgets, accountability, and formal organizational authority. When a director gets better at their job, more people do more of the right things, more coherently.

The senior IC path answers through reusable judgment. ICs scale the quality and durability of decisions. Their instruments are systems, standards, reusable architecture, institutional knowledge, and earned influence. When a principal-level contributor gets better at their job, decisions made once begin to hold across more teams, more time, and more circumstances they may never personally observe.

I’ve come to think of the IC’s measure as a radius of judgment: how many decisions, made by how many people, across how much of the enterprise, for how long, depend on thinking you did once and did well.

A manager’s advancement is visible: the pyramid beneath them grows. An IC’s advancement is structural: the load-bearing surface of their judgment expands, even though the org chart never changes shape around them.

Notice what this framing refuses to do: it refuses to make either path the support function of the other. These are complementary mechanisms of enterprise leverage, and each fails without its counterpart. An architect without organizational partnership can design an immaculate system that nobody adopts; I have watched brilliant technical work die of political starvation. A director without deep IC counsel can produce a beautifully coordinated effort pointed precisely at the wrong technical answer; I have watched that too, and it is often more expensive.

Both paths also share a hazard that neither likes to admit: abstraction. The executive who has not touched the work in fifteen years and the architect who designs from a whiteboard without ever sitting with the people who live inside the system are making the same mistake from opposite directions.

Distance is a tax both ladders collect. The difference is only in the currency.

Leadership Without Ownership

Here is the objection I hear most, sometimes said aloud and sometimes just implied by the phrase “Path B”: but don’t you want to develop people?

I do develop people. Regularly, and by design. Code reviews that teach rather than gatekeep. Architecture discussions where the goal is that the other person can make the next call without me. Active mentoring on new skills, and then handing over real projects to reinforce them. I arbitrate between competing technical approaches. I translate between specialists and executives who are, functionally, not speaking the same language. I say the uncomfortable thing in the meeting where easy agreement would be personally safer.

Every bit of that is leadership.

What I don’t hold – what I have deliberately chosen not to pursue – is formal ownership of anyone’s employment relationship. I cannot assign work by fiat, rate performance, approve time, hire, promote, or terminate. I cannot compel compliance with anything. Every ounce of my influence has to be re-earned, continuously, through credibility, clarity, and usefulness.

If my judgment stops being good, nothing holds anyone to it but momentum – and momentum is a short-term loan. Influence on this path has to survive contact with the work, over and over.

That constraint is not a limitation of the path; I consider it the discipline of it. Management concentrates authority so that coordination becomes possible; senior IC work embeds judgment into systems and standards so that it remains useful beyond the person who supplied it.

The organization needs both. But only one of them shows up in the photograph of the org chart, and so only one of them gets treated as ambition.

Responsibility, Relocated

Choosing Path B did not make me innocent.

A senior IC does not escape the human consequences of organizational life; we relocate them. A platform I architect can determine how many people a process requires. An automation I build eliminates repetitive work and reshapes someone’s role in the same motion. A standard I establish can create pressure in departments I’ll never see. A recommendation I make may help determine which initiative gets funded and which team spends the next year justifying its existence.

None of that is neutral. Distance from direct reports is not the same as distance from people.

So the honest version of my choice is not I refused responsibility for people. It is closer to this: I am willing to carry responsibility for the systems people depend upon, but I do not wish to hold formal authority over the people themselves.

That room, years ago, did not teach me that leadership was undesirable. It taught me that one particular form of authority – the kind where the organization’s decisions about human beings arrive through your mouth – carried a weight I was not willing to seek voluntarily. Someone must carry it, and I hold real respect for those who carry it well. I chose to carry a different weight instead: the one where, if the system fails, the failure traces back to my judgment, my architecture, my name on the decision record.

Both paths can be practiced with courage or with cowardice. Either can serve people or consume them. Both offer abstraction as an anesthetic to anyone who wants it. The choice between them is not a choice between moral exposure and moral safety.

It is a choice about where you are willing to be answerable.

The Other Answer

Which returns us, finally, to the name: “Path B” is useful shorthand, and I don’t resent my director for using it; he was more precise about my career in one phrase than most frameworks manage in forty slides.

But the letter is doing quiet damage across the industry. It tells capable people that the senior IC path is the alternate route: the refuge of the socially reluctant, the consolation for those who never made director. And so thousands of engineers, analysts, and architects who would flourish there never seriously consider it, because nobody ever drew them the ladder.

Both paths begin with doing the work. Both end somewhere abstract. Both ask the same closing question: as your ability grows, through what mechanism will you allow it to touch the world? One answers through people, priorities, and coordinated action. The other answers through judgment, systems, and the multiplication of capability. Neither answer is secondary. They are two mechanisms pointed at the same outcome, and an organization missing either one is running on half its leverage.

As for me, I chose the path where leadership would not require a team beneath me.

I did not choose to build a larger team. I chose to build things strong enough for larger teams to stand on.