What is an AI Player-Coach?
The player-coach move is rarely about skills. It’s about showing up differently.
Earlier this week, I told you I’m renaming my newsletter ‘The AI Player Coach’. Across many organizations who are thinning out management layers and conducting lay-offs, the term has come up as the new bar for leaders and managers. A few of you wrote back asking the obvious question: What does the term ‘player coach’ actually mean? What does that look like in practice?
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.



Interesting framing. The “AI player-coach” idea feels much more realistic than the usual “AI replaces everyone” narrative.
What’s fascinating is how quickly AI is shifting from being a tool people occasionally use…
to becoming a system that continuously guides decisions, workflows, learning, and performance itself.
That changes workplace dynamics quietly.
Not through dramatic replacement.
But through optimization gradually becoming embedded into how institutions operate.
I explored a related idea here around AI, infrastructure, and optimization systems reshaping society:
https://www.lifeofqa.com/p/ai-vs-human-is-the-wrong-debate