What I learned coaching a PM into the role
At one point in my career I worked as a Product Lead with one job that mattered more than any roadmap: coaching someone into product management.
The person I was coaching had about 10 years of deep business expertise and had transitioned into product only a few months earlier. That combination is more common than people think, and it is usually a good bet. The business knowledge was there. The product craft was not, at least not yet at the level the role demanded.
Here is how I approached it, and the three things I took away.
Start with trust, not with a plan
My first goal was to understand strengths and weaknesses in the product field. But I did not start with an assessment or a skills test. I started with daily meetings and a lot of questions.
What matters most to the business right now? What are the priorities, and why those? What does the short term look like, and the long term? What would you change if you could?
Those conversations had two objectives. The obvious one was diagnostic: I was mapping where the gaps were. The less obvious one mattered more. I was building a bond.
Nobody wants to look weak. Nobody wants to admit out loud that they are missing something, especially someone with a decade of credibility in the business who has just moved into a role where they are suddenly a beginner again. If that person does not trust you, they will hide the gaps, and you will end up coaching a version of them that does not exist.
Without trust it is impossible to teach. Everything else in this article depends on getting that part right first.
Do not only fix weaknesses
Once I had a real picture, I built a matrix of learnings to work through the weak spots. That part is standard.
The mistake I see people make is stopping there. Coaching becomes a repair job: find what is broken, fix what is broken. But every PM has a unique talent, and if you spend all your energy on the gaps, you flatten the person into a generic, average version of the role.
In this case I found a real gap in hard skills, specifically data. So we moved on that right away: building dashboards and visualizations, and tying metrics to objectives until the connection was second nature.
But I put just as much effort into the strengths. This PM was excellent at stakeholder management and had genuine influence across the company. Great with people, with a presence that spoke for itself. That is not a soft bonus, it is a superpower in product, and it is much harder to teach than SQL.
So we worked on both: lift the floor on data, raise the ceiling on influence.
Only teach what can be used now
This is the one I would tell every coach.
We worked exclusively on things the job actually required at that moment. It made no sense to spend time on prioritization frameworks when the objectives for the next three months were already defined. It made no sense to drill ideation when we did not have the time or the resources to act on new ideas anyway.
Product management has an enormous surface area. You could spend a year teaching frameworks that sound essential and are useless in the current context. Skills that cannot be applied in the short term do not stick. They become trivia.
If the person can use it this week, teach it. If not, it can wait.
The takeaways
- Build trust before you build a plan. People hide their gaps from anyone they do not trust, and you cannot coach what you cannot see.
- Strengthen the strengths. Fixing weaknesses makes someone adequate. Sharpening a real talent makes them exceptional.
- Teach what is applicable now. Learning sticks when it gets used immediately. Everything else is theory.
Coaching someone into product management is not about transferring a curriculum. It is about finding what is already there, filling in what the job needs next, and getting out of the way.