What I Learned Coaching 150 Product Managers

I have coached product managers at General Assembly classrooms in Atlanta, inside a $350M digital portfolio at a healthcare enterprise, at defense software factories building mission-critical applications, and in 1:1 sessions with career changers who were not sure if PM was the right path.

The environments are wildly different. The patterns are not.

After 150+ PMs coached, 1,150+ workshop attendees, and more retros than I can count, here is what I have learned about what actually moves people forward.

The three things that matter most

1. Precision in language changes everything

The single highest-leverage coaching intervention I have found is teaching people to be precise with words.

A PM writes a user story that says "As a user, I want to be able to view my dashboard so that I can track my progress." I ask: which user? What does "view" mean, specifically? What progress? Track it against what? The story is not wrong. It is vague. And vague stories produce vague software.

At the enterprise healthcare org, I created a Quick Start Guide called "How to Write a Great User Story." It walks through vertical slicing, Given/When/Then acceptance criteria, and user-focused titles. The guide is two pages. It changed how entire squads wrote their backlogs.

When I coached Rawan Serna through her career transition from hospitality to product management, the feedback I gave most often was about language. "Words REALLY matter here." Cut "to be able to." Make the impact clear to engineers. Simplify. She heard it so many times it became her own instinct. She went on to manage eight products.

Precision is not perfectionism. It is clarity. And clarity is the PM's primary deliverable.

2. Coaching the person, not the process

Early in my coaching career, I taught frameworks. RICE scoring. OKR cascades. Jobs to Be Done. Now/Next/Later roadmaps. The frameworks are useful. They are also the easy part.

The hard part is the human underneath. The PM who avoids stakeholder conversations because they got burned last time. The PM who over-indexes on data because they do not trust their own judgment. The PM who writes detailed specs for every feature because they are afraid of being blamed if something goes wrong.

No framework fixes those problems. Coaching does.

At the healthcare enterprise, I coached 28 squads across 9 experience groups. The squads that improved fastest were not the ones that adopted the best framework. They were the ones where the PM felt safe enough to admit what they did not know.

One PM was struggling with prioritization. The surface problem looked like a skills gap, so I taught her 2x2 prioritization. She understood it immediately. Nothing changed. The real problem was that her stakeholders overrode every prioritization decision she made, and she did not know how to push back. The coaching conversation shifted from "how to prioritize" to "how to hold your ground." She started bringing data to stakeholder meetings. She framed tradeoffs explicitly. Within a quarter, her team was shipping against their own roadmap instead of reacting to the loudest voice.

3. Learning by doing, never by studying

Every PM training program I have built follows the same principle: apply the concept to a real product within the same session.

At General Assembly, students did not study user personas in the abstract. They picked a real product and built personas for it. At the healthcare enterprise, I designed 12 interactive workshops using Rise 360. Each one included lectures, but the core was hands-on practice: build the OKR, map the journey, write the story. Do the thing. Then get feedback on the thing you did.

When I coached teams at a defense software factory through their first Discovery & Framing process, we did not start with a slide deck about discovery methodology. We started with a wall and sticky notes. Map the users. Map their pain. Prioritize. Now go talk to one of them.

The PMs who grow fastest are the ones who build their first artifact badly, get feedback, and build it again. The ones who stall are the ones who read three books about roadmapping before attempting their first roadmap.

The patterns that sound good but do not work

"Let's start with a maturity assessment"

I have built and facilitated maturity assessments. They can be useful for organizational diagnosis. But for individual PM coaching, they are a trap. They give people a score when what they need is a direction.

A PM who scores "Level 2" on stakeholder management does not need to know they are Level 2. They need a specific next conversation to have and a coach who will debrief it with them afterward.

"We need to align on the framework first"

Teams that spend weeks debating whether to use OKRs or NCTs or V2MOM before writing a single goal are avoiding the hard work of choosing what matters. Pick a framework. Use it. Iterate. The framework is a container for your thinking, not a substitute for it.

"Let's train everyone at once"

Workshops scale reach. They do not scale depth. I have run workshops for 300+ people at the healthcare enterprise. Those events built awareness and shared vocabulary. They did not, by themselves, change behavior.

What changed behavior: 1:1 coaching, embedded in the team's actual work, over weeks. The PM who learned to write better OKRs did not learn it in the workshop. She learned it when I sat with her team and rewrote their OKRs together, explaining every edit.

What good coaching infrastructure looks like

The organizations that get the most out of PM coaching do three things:

They embed coaches in teams, not in a training department. Coaching works when the coach sees the real work. Not a sanitized version presented in a workshop. The real backlog. The real stakeholder dynamics. The real retro where people actually say what is going wrong.

They give coaching time to compound. One session does not change a PM. Eight sessions over two months does. The PM needs time to try something, fail at it, come back, and try again. Organizations that treat coaching as an event instead of a practice get event-level results.

They measure behavior change, not satisfaction. Coaching CSAT is easy to track and mostly meaningless. A PM can love a workshop and learn nothing. The real measure: did the team's delivery change? Did the PM start making different decisions? Did stakeholder feedback improve?

The through-line

The best PMs I have coached share one trait: they are willing to be specific. Specific about the problem. Specific about the user. Specific about what success looks like. Specific about what they do not know.

Coaching does not make people smarter. It makes them more precise. And precision, applied consistently, compounds into craft.