Coach. Builder. Donut Bringer.
The man who wrote the PM bible before anyone knew PMs needed one.
The person you call when running a three-billion-user product team starts to feel small.
In 2020, Ken Norton walked away from one of the most coveted seats in tech - Product Partner at GV, Google's venture arm - and decided to coach the people who sit in seats like that. Not because he ran out of runway. Because he wanted more altitude.
The transition sounds quiet. It wasn't. Norton spent 14 years inside Google, leading product on Docs, Calendar, Maps for Android, and Google+. Combined reach: somewhere north of three billion users. Before that, he co-founded Grand Central Communications in 2000 - a company that became Google Voice when Google acquired it. Before that, he was Founding CTO at Snap/NBC Internet, built on top of his early-employee days at CNET. He arrived at GV in 2014 and ran Startup Lab, the quantitative research team, and the kind of product coaching that portfolio companies paid dearly for.
Then he went independent. Certified as a Professional Co-Active Coach. Launched Bring the Donuts as a full-time practice. And promptly got ranked the #1 product leadership coach in the world by Reforge, Outpace, On Deck, and Products By Women - a combination that covers most of the serious PM credentialing universe.
What Norton does now is the hardest version of product: he builds people. CPOs wrestling with scope. VPs of Product newly promoted and quietly terrified. Founder/CEOs who've scaled their teams but haven't yet scaled themselves. His three lenses are emotional intelligence, conscious leadership, and 10x thinking - not as buzzwords but as diagnostic tools. "The best leaders," he says, "aren't just strategic thinkers and execution machines. Great leaders are self-aware, emotionally intelligent, and can navigate complexity with clarity and courage."
The coaching practice is built on a foundation of writing. In 2005, Norton published "How to Hire a Product Manager" because - as he put it - he couldn't find anything on the web that described what a great PM actually looked like in an empowered, user-centric tech company. So he wrote it himself. Twenty years later, the essay still circulates through Slack channels and onboarding docs at companies that didn't exist when it was written. In 2025, he published a 20-year retrospective. The original still holds up better than most frameworks invented after it.
Norton is careful with his irony. He holds more than 40 issued U.S. patents - a number that puts him in elite inventor territory - and he is on record arguing for the abolition of software patents, calling his own filings a "defensive maneuver." This is the kind of intellectual honesty that defines his approach. He doesn't pretend the game doesn't have rules. He just refuses to pretend those rules are correct.
Too many smart leaders get stuck tweaking instead of transforming. What would be possible if you stopped playing small?- Ken Norton, Bring the Donuts
Norton started writing in 2005 because the PM canon didn't exist. Now it does, partly because of him. These are the pieces that keep circulating.
The essay that defined the PM profession. Still the first link shared in any serious PM hiring conversation. Written when there was nothing else like it.
What held up, what changed, and what 2005 Norton missed. A rare public reckoning with your own foundational work.
The case for exponential ambition over incremental tweaking. His challenge to every client who's playing it safe: what would you do if you stopped playing small?
Product design should follow users, not internal reporting lines. A rule that sounds obvious until you're inside an org that violates it daily.
Improvisation, collaboration, and the courage to play something you haven't rehearsed. The best PM essay that isn't technically about product management.
Written by a man who holds 40+ of them. The argument that the system is broken even when you're one of its beneficiaries.
The name of Norton's practice is deliberately uncomfortable. "Bring the Donuts" is a provocation. In a world where PMs were branding themselves as "CEOs of the product" - a phrase Norton finds both flattering and deeply misleading - he insisted on the opposite image: the person who shows up early, sets up the room, and brings breakfast because nobody else thought to.
The idea crystallized at a talk at Berkeley's Haas School of Business. Norton asked the audience: who, on launch day, makes sure the team has donuts? Not metaphorical donuts. Actual donuts. The answer, he argued, should be the PM. Not because it's their job, but because great PMs put their teams first and do whatever needs to be done - unglamorous or otherwise.
This philosophy runs counter to the dominant PM mythology. The PM-as-visionary-CEO narrative assigns glamour to the role. Norton assigns accountability. Two very different things. His clients - CPOs and VPs of Product who've already earned the title - hire him precisely because they've discovered the gap between having the authority and knowing what to do with it.
His coaching framework operates on three simultaneous planes: emotional intelligence (knowing yourself and reading others accurately), conscious leadership (moving from reactive to creative operating mode), and 10x thinking (asking not "how do I improve this by 20%?" but "what would make this unrecognizable in a year?"). These aren't sequential steps. They run in parallel, and the work is in integrating them.
Norton is particularly sharp on the leadership transition that happens around the VP level - the moment when your job stops being about doing great product work and starts being about creating conditions for others to do great product work. Most leaders know the transition is coming. Few know what it actually looks like from the inside. Norton has seen it hundreds of times, from CNET to GV to his coaching roster. He speaks about it with the specificity of someone who has watched the exact moment people realize they're managing the job they used to love.
PMs serve the team. Not the other way around. The "CEO of the product" framing inverts the accountability structure. Show up, set up the room, do the unglamorous work that makes everyone else better.
Incremental thinking is a trap dressed as pragmatism. Norton challenges every client: what would be possible if you stopped optimizing and started reinventing? The goal isn't a better version of the same thing.
Most leaders are running on reactive mode - responding to inbound, managing crises, playing defense. Conscious leadership means shifting to creative mode: setting the agenda, not inheriting it.
The PM canon is full of frameworks, metrics, and tools. Norton's recurring argument: the science is table stakes. The art - storytelling, empathy, intuition, presence - is what separates great from good.
The best product managers are willing to do whatever it takes to help their teams succeed - even if it's low-key and non-self-serving.- Ken Norton, "How to Hire a Product Manager" (2005)
These human-centric leadership skills are even more essential in a world dominated by AI.
PMs put their teams first, they do what needs to be done, and they demonstrate that every day.
The best leaders aren't just strategic thinkers and execution machines. Great leaders are self-aware, emotionally intelligent, and can navigate complexity with clarity and courage.
I couldn't find anything on the web about what it meant to be a product manager. So I wrote it myself.
Our companies filed them as a defensive maneuver. That doesn't mean the system isn't broken.
When I was at GV, so much of the conversation was about the tactics. But it is soft skills that people actually want to talk about.
Norton works with a narrow, specific cohort: senior product leaders who have earned their titles but find themselves unexpectedly stuck. CPOs who've scaled to a hundred-person team and aren't sure if they're still the right person in the chair. VPs of Product freshly promoted who keep waiting for imposter syndrome to pass. Founder/CEOs who built the product but aren't sure they've built the product organization.
His coaching isn't a framework delivery. It's a conversation practice built around surfacing what the client already knows but hasn't made explicit. Norton draws on 20+ years of watching where product organizations fail - not from the outside as a consultant, but from the inside as someone who shipped the product, defended the roadmap, and inherited the org chart.
The CPCC certification from the Co-Active Training Institute isn't a credential for Norton's bio. It's the vocabulary for a different kind of rigor than what product management typically trains. Most PM coaching focuses on output: better roadmaps, better stakeholder management, better hiring. Norton focuses on input: who you're being when you walk into a room, what you're actually hearing when someone talks to you, and whether your operating mode is creating or reacting.
The results his clients describe have a recurring shape: they come in with a tactical crisis and leave understanding a structural pattern. A VP struggling with a CEO relationship discovers they've been seeking permission they already have. A CPO feeling underutilized realizes they've been solving for visibility rather than impact. Norton's gift is pointing at the thing behind the thing - the 2005 PM essay skill, applied to people instead of products.
Google Voice has his fingerprints on it. Grand Central Communications, which Norton co-founded in 2000, was acquired by Google and became Google Voice. Every time someone uses a Google Voice number, they're using infrastructure he helped build.
He holds 40+ patents and wants to abolish software patents. Filed them as a defensive maneuver. Argues publicly that the system is broken. Both things are true simultaneously.
The "Bring the Donuts" idea came from a Berkeley Haas talk. He used it to flip the "CEO of the product" narrative. The image stuck. The essay stuck. The company name stuck.
He wrote the PM canon because there wasn't one. In 2005, there was almost nothing written about what great product management looked like. Norton wrote it because he needed it to exist. The essay is still the first result when senior PMs search for PM hiring guidance.
Jazz teaches him product management. He uses jazz improvisation as a metaphor in talks - collaboration, risk, listening, playing off others. The essay is called "Please Make Yourself Uncomfortable: Jazz and PMs."