SVPG · Free post · Discovery & customer research · Leadership & management

Common PM Problem Areas

Marty CaganNov 30, 20185 min
SourceSVPG
KindFree post
PublishedNov 30, 2018
Originalsvpg.com ↗
N:

Marty Cagan describes the most common confusions he sees in product teams, drawn from a dinner conversation with product leaders who recognized the same patterns. He argues that product teams should discover solutions that work rather than act as gatekeepers validating stakeholder requests. He stresses that prototyping beats extended prioritization debates, that product managers need deep knowledge of users, data, industry and business operations to be credible, and that ethics has become a more prominent concern. He closes by placing responsibility for coaching and developing product managers squarely on their managers. The piece matters because it names recurring failure modes that teams can watch for and address deliberately.

01Key takeaways

  • Treat your job as discovering solutions that solve the underlying problem, not as approving or rejecting stakeholder requests.
  • Build quick prototypes early instead of spending excessive time debating priorities on paper.
  • Invest in understanding how your business works, including finance, sales, legal and partnerships, to gain team context and executive credibility.
  • Watch for ethical risks in your product and be ready to raise them with leadership using business-grounded arguments.
  • Avoid acting like the boss of the team; competence and respectful collaboration matter more than authority.
  • If you manage product managers, make coaching your highest priority and treat team competence as your accountability.

02Key sections

Validating ideas vs. discovering solutions
Teams have become good at testing stakeholder ideas, but rejecting ideas repeatedly frustrates executives. Cagan says the goal is to find solutions to the underlying problem, not to serve as a filter.
Planning vs. prototyping
Teams overspend time prioritizing and predicting which ideas will work. Cagan argues real learning comes from quickly building prototypes and testing them with users, engineers and stakeholders.
Product manager competence
Strong product teams depend on competent PMs with deep knowledge of users, data, industry and business. Many PMs lack understanding of functions like marketing, finance, partnerships, privacy and legal, which limits the context they give their teams.
Ethics and the product manager
Ethical issues are increasingly visible, and PMs often spot them first. Raising them effectively with senior leaders requires business credibility, especially around monetization.
PM as CEO of the product and coaching
The CEO-of-the-product metaphor fails when PMs act like bosses, and Cagan concludes that the real problem is abrasive behavior rather than the role. He argues directors must make coaching their top responsibility and be held accountable for team competence.

03From the post

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

“What I try to explain to the product teams is that their purpose is not to serve as gatekeeper and just validate the requests that…”Marty Cagan · SVPG
“I tell people they are wasting their time pretending they can predict how effective an idea or approach might be without actually fleshing that idea…”Marty Cagan · SVPG
“By my reasoning, this is the absolute top responsibility for every people manager of product managers, product designers, and engineers.”Marty Cagan · SVPG

04Frameworks mentioned

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