SVPG · Free post · Product strategy & vision · Discovery & customer research

What Product Management Is Not

Marty CaganMar 7, 20084 min
SourceSVPG
KindFree post
PublishedMar 7, 2008
Originalsvpg.com ↗
N:

Cagan argues that many companies remain stuck in failed models of product management because they misdefine the role. Rather than restating what the job is, he lists common misconceptions and explains why each one fails. He contends that product managers are not business-case writers, requirements collectors, project managers, or product marketers. The core responsibility is discovery: finding a product that is useful, usable and feasible. Without that focus, companies waste time and money building the wrong things. Understanding this distinction matters because role confusion undermines both team effectiveness and product outcomes.

01Key takeaways

  • Treat the business case as a input to investment decisions, not as the core product manager deliverable.
  • Talk directly with users and customers to uncover real needs rather than relying on documented market requirements.
  • Distinguish customer requests from product requirements before committing engineering time to them.
  • Keep discovery separate from project delivery, since they demand different processes and different skills.
  • Staff dedicated product marketing roles instead of loading marketing activities onto the product manager.
  • Measure product management success by whether discovery yields a useful, usable and feasible product.

02Key sections

Business case is not the job
A business case helps leadership decide where to invest, but writing it does not create the product. The product manager may contribute to it without it defining the role.
Market requirements are a fallacy
Markets do not have requirements, people do, so the person defining the product must speak directly with users. Market needs and technical capabilities must be discovered together.
Requirements gathering is not product management
Collecting and documenting customer requests for delivery on sales-promised dates is project management for custom software. Customer requests should not be mistaken for product requirements.
Project management is a different discipline
Discovery is its own process, distinct from delivery, and people who excel at one rarely excel at the other.
Product marketing is separate
Pricing, positioning, launches and promotions are critical but require dedicated marketing skill, unlike the discovery work at the heart of product management.

03From the post

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

“Markets don’t have requirements. People do.”Marty Cagan · SVPG
“This is not product management. This is project management for custom software solutions.”Marty Cagan · SVPG
“the product manager is responsible for discovering a product that is useful, usable and feasible.”Marty Cagan · SVPG

04Frameworks mentioned

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