“The future belongs to individual contributors who can build everything themselves. Hierarchy is dead. Become AI-native or get automated away.”

That’s the message going around product leadership right now. It’s coming from the biggest names in the space. Growth leaders at vibe-coding companies are writing posts about how “IC work is the new career flex.” The biggest PM newsletter says you need to build or get left behind. LinkedIn replaced its Associate Product Manager program with something called “Associate Product Builder.”

If you’re a Director or VP who spent 10-15 years earning your seat through judgment, org-navigation, and shipping through teams — this message is telling you that was the wrong career path. That you should go back. That your experience is the problem.

I disagree. Strongly.

The bottleneck in AI isn’t building. Building is the easy part now. A weekend with Claude Code and any motivated person can ship a prototype.

The bottleneck is knowing what to build and why.

Which of the 50 things your team COULD build are actually worth building? Which ones will get killed in the next reorg? Which ones will scale past a demo? Which ones will earn engineering’s trust instead of eye-rolls?

That takes a decade of scar tissue. Not a vibe-coding session.

One growth leader recently wrote that there’s a “short window — measured in months, not years” to become AI-native, and her prescription was: block a few hours, vibe-code a rough version of your company’s product, start a side project, ask the AI-native person near you for help.

That’s an IC’s to-do list. Not one for a Director+ leader.

A Director’s AI moment isn’t vibe-coding a prototype on a Saturday. It’s walking into Monday’s meeting with that prototype, using it to pressure-test three competing directions with the team, and helping the room converge on the one worth building — all before lunch.

But what really gets me about the super-IC gospel is the blind spot so big you could drive a reorg through it.

Teamwork doesn’t stop existing because AI showed up.

The super-IC fantasy is built on hyper-independence. One person, one team of AI agents, shipping everything end-to-end. And I get the appeal — it’s clean, it’s fast, it’s controllable. But AI, as a whole, has an over-fixation on individual output. Maybe because the people building these tools optimized for solo productivity rather than organizational reality. Whatever the reason, the super-IC model treats collaboration as overhead rather than the actual mechanism through which work gets done at scale.

The wave after “I built this myself” is always “How do I get my team working this way?” How do we develop more people to think like this? How do we show instead of tell? How do we move from one person’s prototype to an organization that ships AI products as a matter of course?

That’s the adoption problem stalling AI at most companies right now. Not a lack of tools. Not a lack of tutorials. A lack of leaders who can bridge the gap between what’s possible and what the team can actually execute - *together*.

The super-IC ships a prototype and posts about it. The player-coach ships a prototype, earns engineering’s respect, develops three people on their team to do the same thing, and redirects the product strategy.

The super-IC is impressive. The player-coach is indispensable.

Your experience isn’t a liability in the AI era. It’s the scarce resource.The judgment, the org-navigation, the ability to smell a bad bet from three meetings away, the ability to bring a team along instead of running ahead alone — AI can’t replicate any of that. It took you years to develop and it’s worth more now than it was five years ago.

The move isn’t to go back to being an IC. The move is to become the leader who can ALSO play — who can prototype, evaluate, and ship — without giving up everything that made them a leader in the first place. AND who can develop a team that works this way, not just a personal workflow.

That’s what a player-coach is.

And if you’ve been reading those hot takes, feeling that knot in your stomach, wondering if you missed a window — you didn’t. The window for super-ICs-as-laeders is closing. The window for player-coaches is just opening.

If you want to go deeper on what a player-coach actually looks like in practice — the real examples, the real moves, the moments where it clicks — I wrote a longer piece with stories from eight product leaders who are living it here: “What Is an AI Player-Coach?”.

If you believe teamwork still needs a guiding hand — that AI amplifies teams, not replaces them — you’re in the right room. Forward this to someone who might need to hear it today.

Talk soon,

Polly Allen
AI Career Boost

New to The AI Player-Coach? This newsletter is for Director+ product leaders becoming indispensable AI leaders. Subscribe & get notified 🔔 first of new editions at aicareerboost.com/interested.

Let me paint you a picture.

A Week in the Life of a Player-Coach

A VP of Product I know noticed her team was drowning in repetitive admin work. Status updates, ticket triage, weekly summaries — the kind of work that quietly eats 10 hours a week and nobody questions because “that’s just how it works.”

A ‘pure manager’ might commission a process audit. Maybe bring in a consultant. Maybe add it to next quarter’s roadmap under “operational efficiency.” Check the box, move on.

She did something different.

She engaged her team in an audit of where they were spending the most time on admin. She took the top scenario and tried a few tools herself. She weighed whether her team would prefer n8n or Cowork, and decided to prototype in n8n because it was more visual — better as a strawman to react to. She documented her understanding of the process as she went.

Then she brought it to the team’s weekly meeting. Not as a mandate. As a draft.

In the meeting, the team reviewed her prototype, adapted the prompt, discussed edge cases and success criteria together. The next day, someone on the team let her know they’d already whipped up a version in Cowork — including the evals and edge cases they’d discussed. She asked them to lead the demo and work it through with the team in next week’s meeting.

That’s an AI player-coach.

She wasn’t the best builder in the room. She wasn’t trying to be. She got close enough to the work to ask the right questions, modeled what it looks like to try, and created the conditions for her team to take ownership. She turned status meetings into hands-on sessions working together.

The player-coach move is rarely about skill. It’s about showing up differently.

It’s the willingness to prototype something imperfect and bring it to your team instead of waiting for a polished solution from someone else. It’s choosing to be a beginner at something new while being the most senior person in the room. It’s knowing that your team watches what you do more closely than what you say — and acting accordingly.

The Three Shifts That Matter

The leaders I’ve seen make this shift share three things:

• curiosity that overrides their ego,

• persistence through the discomfort of not knowing, and

• a genuine excitement about building — even when (especially when) they’re not the best at it.

If you missed Monday’s edition on the rise of the AI Player-Coach you can read it here: The Rise of the AI Player-Coach Leader →

I wrote a longer article on what an AI player-coach is and isn’t, with more scenarios like the one above with examples from real, on-the-ground player-coach leaders, who we’ve been interviewing for the past two years on our podcast, “The AI Product Leader”. Get the full version here: What Is an AI Player-Coach? →

Know someone leading AI from the field? Forward this to them.

See you next week,

— Polly

This is The AI Player-Coach — practical AI leadership for Director+ product leaders who lead from the field, not the sidelines.

Subscribe now

But this announcement held something new: a clear, if stark, message for leaders.

“- No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams.”
— Coinbase layoff announcement (delivered on x.com, because of course it was.)

That term - “player-coach” is one I’ve been circling for over a year. It started when I was talking to founders or CPOs/Heads of Product at small, agile companies in the Bay area about how they’re working. They were actually pushing code or fixing bugs themselves for the first time in decades. They were working with their CTOs to get their product team access to code bases or pipelines to push features to production, at least behind A/B tests. They were doggedly pushing how far AI CAN take you if you trust it - even when you shouldn’t - and purposely seeing where it breaks, then patching with guardrails and moving on until it breaks again. The goal: to move as fast as you’ll be able to some day, when reliability catches up.

And it IS catching up.

If you’ve had at least a passing glance at tech twitter, you’ll know that programming juggernauts like Andrej Karpathy (co-founder, OpenAI) have been screaming from the rooftops that software development has completely changed since December 2025.

“It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the “progress as usual” way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December and basically work since[…]imo, this is nowhere near “business as usual” time in software.”
— Andrej Karpathy on x.com, Feb 25 2026

The world’s top developers, the most skeptical, attention-to-detail pedants on the planet, are trusting LLMs for long-running and complex tasks. And if you’re not asking what that means for product and business leaders in the software development ecosystem - you should be.

The danger is waiting to understand the difference between the ‘pure manager’ and the ‘player-coach’ until it’s too late. And the answer is not simply loading up on tech skills to become the newly-vaunted ‘super-IC’, or to take on two jobs and 15+ reports until we burn out. There is another way. I know, because I’ve seen the leaders quietly making this shift: layering AI fluency and practice on top of the strategic judgment, organizational instinct, and discernment they’ve already built over their careers. It’s powerful, and it’s what is making them indispensable at their organizations right now - even amid the layoffs and chaos.

You’re not starting over. You’re adding depth. That’s a different path, and one I wanted to draw back the curtain on. It’s not a path that needs programming experience - it’s one that requires curiosity, persistence and an excitement to actually PLAY. Not to be the star player - but to show your team what it means to really love the game.

If you’re a Director+ product leader eager to see what ‘getting on the field’ looks like - from the skills needed at the leadership level to stories from player-coaches in the trenches - welcome to The AI Player Coach.

More soon. Pass it on.

Share The AI Player Coach