For most of my career, your impact grew as you increased your team’s headcount.
If you wanted to do more, you had to manage more. Senior meant managing people who managed people. The org chart was the impact multiplier — the bigger your team, the bigger your potential contribution. Individual contributors who didn’t want to manage hit a ceiling early, and either made peace with it or left.
Nobody designed this. It emerged from a simple constraint: execution bandwidth. One person, however talented, can only build, test, and ship so much. If you wanted to multiply that, you added people. If you added people, you had to manage them. If you managed them, you got promoted.
The management ladder was never a career philosophy. It was a workaround for limited execution capacity.
AI is removing that constraint.
The High-Impact IC
Senior individual contributors (ICs) can now do what used to require a team. Not in every context — complex systems and high-stakes decisions still need human judgment at scale. But for a real category of product and engineering work — building, testing, iterating, shipping — a skilled individual with the right tools can operate at a throughput that was previously impossible without reports.
Elena Verna, who has held senior product roles at Amplitude, Miro, and Dropbox, calls this the “High-Impact IC”: an archetype that is now structurally viable, not just exceptional. The HI-C doesn’t manage a team. They use AI as execution infrastructure, shipping end-to-end on work that previously required coordination across four people.
The problem is that most organisations haven’t updated their mental model.
The ceiling that shouldn’t exist
The career ladder still points up. Senior ICs who don’t want to manage face the same ceiling they always did — not because the economics have changed, but because the system hasn’t. “Principal PM” or “Staff Engineer” are titles that often carry less pay, less status, and less organisational weight than “Director” or “VP.” The IC track is still coded as the consolation prize for people who weren’t quite right for management.
This was always a poor design. AI is making it a dangerous one.
The organisations that thrive in an AI-native world will be the ones with genuinely skilled people who are deeply good at their craft. Many of those people don’t want to manage. Many of them have tried it, concluded it wasn’t the best use of what they’re capable of, and been quietly penalised ever since.
If the IC track is still a holding pattern, those people leave. Not in protest — just quietly, to somewhere that treats their contribution as primary.
I’ve watched this from both sides. Exceptional product managers accepting Director titles they didn’t want because it was the only way to stay relevant — and spending the next two years doing less of the work they were genuinely good at. Organisations promoting their best builders into people management and getting two bad outcomes at once: a mediocre manager and an empty seat where a great IC used to be.
Putt’s Law puts it plainly: technical competence and the desire to manage are inversely correlated. If your career system forces people to choose, you systematically drain the technical ranks of the people most capable of filling them.
AI doesn’t fix Putt’s Law. But it changes the options. The HI-C who doesn’t want to manage now has a credible answer to “how do you scale your impact?” It used to be “I can’t.” Now it’s “I ship more.”
What the redesign actually looks like
What this requires is a redesign, not a rebrand.
Calling an IC track “Principal” or “Distinguished” without changing the compensation, the status, or the organisational weight behind it is decorative. The redesign that works treats the IC path as genuinely parallel to management: same pay bands, same visibility with senior leadership, same access to strategic work.
It also means being deliberate about who does what. Not every important contribution requires management. Some of the most important product work — deep customer insight, architectural decisions, the judgment about what not to build — is individual work. Routing it to managers by default, because managers are the only people senior enough to handle it, is a structural mistake.
The Renaissance Professional I wrote about earlier this year — someone with deep expertise in one domain and real capability across adjacent ones — is exactly the profile of the emerging HI-C. That person doesn’t need a team. They need the right tools, real autonomy, and an organisation that values what they produce.
The shift that was always coming
AI didn’t create this. It enabled it.
The senior IC who could drive outsized impact was always there. What they lacked was execution bandwidth, and a career structure that treated their path as legitimate rather than lateral.
Both of those are changing. The organisations that recognise it early will compound an advantage. The ones that keep treating management as the only real path to seniority will keep losing the people who don’t want to manage — and keep wondering why their best builders leave.
Leave a Reply