Product Management Then and Now

Marty Cagan contrasts the traditional PC-era product manager with the modern Internet-era product manager. He argues that many organizations still operate with the older model, which was often ineffective and poorly respected, and that the role has shifted substantially. Using a deliberately exaggerated side-by-side list, he highlights differences in background, daily work, how customers are understood, how funding and decisions are justified, and what the role optimizes for. The piece matters because it frames a shift from output-focused, opinion-driven business administration toward discovery-driven, customer-centric product leadership that creates value.

01Key takeaways

• Audit whether your product role still follows a legacy, requirements-and-stakeholder model or a discovery-driven one.
• Ground decisions in customer evidence from testing and experiments rather than opinions or business-case spreadsheets.
• Communicate ideas with working prototypes instead of slide decks to get faster, more concrete feedback.
• Expect that at least half of your ideas won't work and design small experiments to find out early.
• Take ownership when things go wrong instead of blaming engineers or other teams.
• Optimize for creating customer value, since sustained profit follows from it.

02Key sections

Why old-style product management persists

Cagan notes that some teams still practice the legacy role, possibly because leaders repeat what they learned long ago, outside training was misapplied, or the old model got locked into formal processes.

Organization and background

The product function moves from a marketing-led role with MBA training to a peer of engineering and marketing staffed by people with computer science or UX design backgrounds.

Daily work and learning about customers

Instead of writing requirements documents and relying on focus groups and business cases, the modern product manager pursues discovery, minimum viable products, user testing, and A/B testing.

Decisions, accountability and communication

Decisions shift from opinions to data, prototypes replace PowerPoint, and when things fail the modern PM looks at himself rather than blaming developers.

Goals and what the role optimizes for

The modern PM aims to create value for customers as the best path to sustained profit, rather than chasing killer features, competitors, or pleasing stakeholders.

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.