Coaching Tools – The One on One

Marty Cagan argues that the weekly one-on-one is the foundation of coaching product managers, and that most managers either never run it well or treat it as optional. The 1:1 exists primarily to build a PM's competence and potential, relying on trust and honest feedback. He lays out ten principles, including frequency, sharing context, homework, and continuous improvement, then catalogs common anti-patterns that stop managers from developing their people. The piece matters because weak manager coaching is a leading reason PMs fail to reach competence, and it gives managers, PMs, and job candidates a concrete standard to hold against.

01Key takeaways

• Treat the weekly 1:1 as a sacred, non-cancellable session focused on the PM's growth, not your status updates.
• Share mission, yearly objectives, product vision and quarterly goals so PMs can make decisions with the right intent.
• Talk less and listen more; the session is primarily for the product manager, and people learn in different ways.
• Give frequent, specific constructive feedback, praising in public and criticizing in private, so reviews hold no surprises.
• If a PM cannot reach competence within roughly 3-6 months, help them move to a role where they can succeed.

02Key sections

Purpose and relationship

The 1:1 is first about developing the PM toward competence and potential, and it depends on trust that the manager is sincerely invested in that growth. Honest, frank conversation is essential for both parties to succeed.

Onboarding, frequency and context

New PMs need an intense 2-3 month onboarding with close oversight, and 1:1s should be at least 30 minutes weekly, ideally in person. Managers must also share the company mission, product vision and quarterly objectives so PMs can act with intent.

Homework and thinking like a PM

PMs own their homework, learning the product, users, data, technology, industry and business dimensions. Coaching builds an outcome-focused mindset that weighs value, usability, feasibility and viability, along with collaborative behaviors.

Feedback and continuous improvement

Feedback should be frequent and timely, praised publicly and criticized privately, and not saved for annual reviews. Strong PM development is a continuous journey, and the best managers measure success by the growth and promotions of their people.

Anti-patterns

Common failures include managers who don't care, micro-manage, talk more than they listen, avoid difficult feedback, or feel insecure. When a PM still can't reach competence after 3-6 months, the manager should help them find a more suitable role.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.