Managing Other PMs, The Transition Nobody Prepares You For

The Job Nobody Describes Accurately

Here is how most promotions to Group PM or Head of Product get framed: you were excellent at the IC level, so now you will do the same work at a higher altitude. You will own a larger surface area. You will influence more decisions. You will bring your product judgment to bear across multiple workstreams.

None of that is wrong. All of it is misleading.

The altitude framing suggests the skills that made you effective before will continue to make you effective, just applied more broadly. The actual transition is not about altitude. It is about a complete change in what the job requires of you, what success looks like, and which instincts will actively work against you.

Most new PM managers figure this out somewhere between six and twelve months in. The organization around them rarely names it sooner.

What Gets You Promoted Is What Gets You Into Trouble

Strong IC PMs are promoted for three things more than any other: sharp product opinions, the ability to execute without much hand-holding, and the instinct to step in when something is going wrong before it becomes a problem. These are real skills. They are also, in a management context, traps.

Strong product opinions. As an IC PM, having a clear point of view on what the product should do is a feature. You make faster decisions, build alignment faster, and resist scope creep. As a manager, a strong product opinion expressed at the wrong moment communicates something your report hears clearly: their judgment is secondary to yours. The opinion does not even have to be wrong. The timing is enough to undermine ownership.

Comfort with direct execution. IC PMs are rewarded for getting things done. When a stakeholder meeting goes sideways, you step in. When a sprint is at risk, you find the fix. The reflex is fast, efficient, and high-quality. In a management context, that same reflex short-circuits your report's ability to learn how to handle the situation themselves. You solve the problem once. They never develop the skill.

The instinct to step in when things go wrong. This one feels the most virtuous. Of course you should prevent a bad outcome. The problem is that most "things going wrong" in product work are not catastrophic, they are instructive. A junior PM defending a weak prioritization call in front of a skeptical stakeholder will remember that moment and grow from it in a way they will not if you rescued the conversation before it got uncomfortable.

The Comparison That Most Organizations Never Make Explicit

The uncomfortable part of this table is not the right column. It is what happens when you keep optimizing for the left column after you have moved into a management role.

Output quality does not drop immediately. In fact, it often goes up in the short term, because you are still doing the work, just with a different job title. The damage shows up six months later, in an exit interview, when someone tells you they never felt like they owned anything.

The Specific Failure Pattern

Priya was the strongest IC PM on her team at a mid-size e-commerce company in Bengaluru. She was promoted to Group PM with three direct reports: one mid-level PM and two junior PMs. Her manager called her "the clearest product thinker on the floor." The promotion was well-deserved.

In the first two months, she rewrote two PRDs before they went to stakeholders. Not because her reports asked her to, because she saw gaps and it was faster to fix them herself than to explain what was wrong. She attended stakeholder meetings "to support," and in three of those meetings she ended up leading the conversation when her reports' arguments faltered. She redirected a prioritization call her most junior PM made on a feature sprint, not overriding it formally, but asking enough questions in the team meeting that the PM reversed course.

Her team hit every sprint commitment. Her manager called the team high-performing. Priya felt productive. The metrics looked right.

Six months later, one PM left. The exit interview was brief. "I never felt like I owned anything. Every time I made a decision, I was waiting to find out if Priya would change it."

Priya had not been a bad manager by any visible metric. She had optimized for output quality so effectively that she had eliminated the conditions under which her reports could develop their own judgment.

The Hardest Skill in This Job

There is a specific moment that separates PM managers who make the transition cleanly from those who do not. It is this: sitting in a meeting where your report is making a decision you disagree with, and staying silent.

Not silent forever. Silent in the room, in the moment, in front of the stakeholders, so that your report owns the decision they are defending. Then, after the meeting, in private, you tell them what you noticed and why you would have framed it differently.

This is harder than it sounds because the cost is immediate and visible, you watch something happen that you believe is suboptimal, and the benefit is delayed and invisible, your report builds the muscle to handle it themselves next time. Every instinct you built as an IC PM runs against this. You know the better answer. You are sitting three feet away from the person who needs to hear it. The stakeholder is right there.

The instinct says: help now. The job says: do not.

The distinction between a clarifying question that guides your report to a stronger argument and a correction that transfers the moment back to you is smaller than it looks. It comes down to who is doing the reasoning in the room. If your question is doing the work, you are still doing the work.

The Judgment Turn

Most new PM managers are bad at this job for six to twelve months. Not incompetent, bad at the specific thing the job requires. The organizations that promote them rarely say this explicitly, because naming it would require admitting that the promotion criteria (strong IC performance) do not directly predict success in the new role.

The implicit theory is: good PMs become good PM managers because product judgment transfers. It does, eventually. But what transfers first is the behavior pattern that made the IC PM successful, and that pattern is actively harmful in a management context for a significant portion of the transition period.

What makes this worse is that the damage is not visible in the metrics that organizations track. Output quality may be fine. Sprint velocity may be fine. Stakeholder satisfaction may be fine. The destruction of ownership happens beneath those metrics, in the daily experience of people who are doing work but not owning it.

By the time it surfaces, in a resignation, in a performance conversation about a report who "lacks initiative," in an engagement score, the new PM manager has had six months of reinforcement that their approach was working.

It was not working. It was delaying the failure.

What the Job Actually Requires

The job requires you to hold two uncomfortable truths simultaneously. First: you are almost certainly better at the product work than some of your reports, and acting on that advantage will make your team worse. Second: your reports will make decisions you disagree with, some of those decisions will be wrong, and the cost of letting them experience that consequence is lower than the cost of rescuing them from it.

Neither of these truths is comfortable. Neither resolves cleanly into a principle you can apply mechanically. They require you to make a judgment call, in the moment, about when the cost of silence is acceptable and when a decision is genuinely too consequential to let go uninterrupted.

That is the job. Not execution. Not product vision at higher altitude. The management of someone else's growth at a direct cost to your own output.

Key Takeaways

1. The skills that make you an effective IC PM, strong opinions, direct execution, early intervention, are the same skills that will undermine your reports' ownership if you do not actively suppress them at the right moments.
2. IC PM success is measured by your output quality. PM manager success is measured by whether your reports can produce quality output without you. These are not the same measurement, and optimizing for the first after you have changed roles is how you destroy the second.
3. Rewriting a report's PRD, leading a meeting you attended "to support," redirecting a prioritization call through questions, these all feel like good management and function as ownership transfer. The report's output improves; their judgment does not.
4. The hardest skill in PM management is staying silent in a meeting where your report is making a decision you disagree with. The benefit, your report builds judgment, is delayed. The cost, you watch something suboptimal happen, is immediate. Most new PM managers pay the wrong cost.
5. Most organizations do not warn new PM managers that they will be bad at this job for six to twelve months. The metrics that organizations track (sprint velocity, output quality, stakeholder satisfaction) do not capture the damage early enough to correct it.

Related Articles

• Building Credibility When You Are the New PM
• What Product Management Actually Is (and Is Not)
• Cross-Functional Conflict, How to Navigate It Without Spending Relationship Capital You Will Need