Marty Cagan

Most people who reshape an industry do it from within - by building a billion-dollar company, running a fund, or landing on a magazine cover. Marty Cagan did it by refusing all of that. He walked away from a seat at the table at eBay, one of the defining companies of the early internet era, to write, teach, and argue. Loudly. For two decades and counting, he has been the industry's most inconvenient voice: the person who shows up at your conference, looks at how you're building products, and says "that's not product management."

He founded the Silicon Valley Product Group (SVPG) in 2001 with a deceptively simple premise - that there was a better way to build technology products than the way almost everyone was doing it. His three books, INSPIRED, EMPOWERED, and TRANSFORMED, have become the closest thing the field has to canonical texts. Product managers receive them as onboarding gifts. Engineering leaders dog-ear them. CEOs quote them in all-hands meetings without quite understanding the implications.

The irony is that Cagan never set out to be a product manager. He was a software engineer. He spent ten years at HP Labs in Palo Alto building tools for other developers, acquiring the kind of deep technical fluency that most modern PMs lack and he argues most should have. Then the internet happened. He went to Netscape, where he worked directly under Marc Andreessen and alongside Ben Horowitz during what he has called his favorite job, because at Netscape in the early nineties, the web was being invented in real time. Every week brought something that had never existed before.

From Netscape, he moved to eBay as Senior Vice President of Product and Design, overseeing the product definition for a global e-commerce platform at the height of its growth. He was at the center of things. Then, instead of following the conventional script - staying in the C-suite, getting a board seat, starting a fund - he left to start SVPG. Not to consult in the usual sense, but to codify what he had learned and share it with everyone who would listen.

What Cagan Actually Believes

The through-line in everything he has written and said for twenty years is a distinction that sounds obvious until you realize almost no organization actually acts on it. There is a difference between a team that is given a list of features to build (a feature team, or in his more pointed framing, a team of mercenaries) and a team that is given a problem to solve and the authority to figure out how (an empowered product team, a team of missionaries). Most companies operate with the former while telling themselves they have the latter.

This matters because, as Cagan argues relentlessly, if your product team is just executing a roadmap handed down from stakeholders, then all the Agile ceremonies and OKR frameworks and product operations tooling in the world are theater. He literally coined the phrase "Product Management Theater" to describe organizations where people hold PM titles without genuine product ownership - and the essay he wrote on this topic, amplified by Lenny Rachitsky's newsletter, generated some of the most intense debate the PM community had seen in years.

His framework for what makes products succeed centers on four risks that must be addressed before a team commits to building anything. Value risk - will customers actually want this? Usability risk - can they figure out how to use it? Feasibility risk - can the engineering team actually build it? Business viability risk - does it work for the business, legally, financially, operationally? Product discovery, in his model, is the work of de-risking all four before writing a single line of production code.

The Books That Changed the Game

INSPIRED came out in 2008. The first edition was a slim, practical handbook written for individual product managers. Cagan rewrote it almost entirely for the second edition in 2017, expanding it to address how the field had matured and the mistakes he saw companies making as product management scaled from startups to enterprises. It has been described, without obvious exaggeration, as the foundational textbook for the discipline. New PMs at companies worldwide are handed it on their first day. It is the book that defined what product management should mean in technology.

EMPOWERED, published in 2020 with co-author Chris Jones, shifted the focus upward - to product leadership. If INSPIRED was for individual contributors, EMPOWERED was for the people managing them. It argued that most product leaders underinvest in coaching and developing their teams, and that the gap between ordinary product organizations and extraordinary ones is almost entirely a leadership and culture gap, not a process or tooling gap.

The third volume, TRANSFORMED, arrived in 2024 co-authored with four SVPG partners. It addresses the hardest problem in the portfolio: how do large, traditionally structured organizations actually change? Not just their product teams, but their entire operating model. How do you go from a company organized around projects and delivery to one organized around products and outcomes? TRANSFORMED is the manual for that transition, written for the CEOs, CTOs, and CPOs who have read the first two books and still can not figure out why their organizations have not changed.

The Man Behind the Framework

Cagan is notably private about his personal life. There is almost no public information about his family, his hobbies, or what he does when he is not writing or speaking. His public identity is almost entirely professional - which is fitting, because he has described himself as someone who just loves products, who thinks about them constantly, and who believes that the work of building something people genuinely want to use is inherently interesting and inherently hard.

What does come through in interviews and writing is a certain impatience with pretense. He has been consistently willing to critique dominant frameworks - Agile, Scrum, SAFe - not because he is opposed to the underlying ideas, but because he watches organizations use the ceremonies as a substitute for actual product thinking. When everyone is running two-week sprints and writing user stories and doing retrospectives, it is easy to believe you are doing product management. Cagan's point is that none of that is the hard part. The hard part is figuring out what to build in the first place.

He left Twitter/X in October 2023 with a short farewell note to his 67,600 followers and has not looked back. He directs people to LinkedIn and to the SVPG website, where he and his partners publish new articles every week or two. In early 2026, he published something he described as a significant change to a position he had held for two decades - a reminder that he is still actively revising his own thinking, not just defending a body of work.

What Netscape Taught Him That No Business School Could

Cagan has a computer science degree from UC Santa Cruz and a management certificate from Stanford's executive program. But the education that shaped him most was his decade at HP Labs and then the experience of joining Netscape in the early nineties. At Netscape, he worked closely with Hugh Dubberly, who had come from Apple and brought a design sensibility that expanded Cagan's view beyond the classic engineer's perspective. He has credited that exposure with teaching him to think about products not just as technical systems but as human experiences.

Working alongside people like Marc Andreessen and Ben Horowitz during the birth of the commercial internet gave him a reference point that is hard to replicate. He has seen what real innovation looks like from the inside, at one of the most consequential moments in technology history. It is probably why he is so direct about what he sees as imitations of that energy. When companies talk about moving fast and building great products while actually doing something closer to managed project delivery, he notices.

The SVPG Operation

SVPG is unusual as an organization. It has never taken venture funding. It operates as a private partnership of former senior product executives - people with real operating experience at companies like Lookout, IBM, Macromedia, Adobe, and CareerBuilder - who advise, write, and speak. They have worked with companies at every stage and scale, from startups to Google and Amazon. Christian Idiodi, one of Cagan's partners, has advised over 200 companies since 2015 alone.

The SVPG website is where Cagan does most of his publishing now. The articles are substantive - not LinkedIn platitudes but actual arguments, with examples, about how product management should work. He writes about product discovery, product coaching, product leadership, the product operating model. Recent pieces have addressed Spotify's approach to the product operating model, the difference between internal and commercial product discovery, and what coaching looks like in the age of AI. There is no algorithm optimizing the content. There is no growth team. He just writes what he thinks is important.

His speaking fees - reportedly $30,000 to $50,000 for a live engagement - put him in the same tier as former heads of state and Fortune 500 CEOs. The market has a way of expressing what it thinks something is worth.

The Enduring Argument

The through-line in Cagan's work is an argument about what companies owe their customers and their employees. He believes companies should solve real problems for real people, and that the way to do that is to trust the people closest to the problems - product managers, designers, engineers working as a real team - to figure out how. Not to hand them a requirements document and measure them on delivery speed.

He also believes, and says plainly, that most product managers are not doing product management. They are managing backlogs, facilitating ceremonies, and writing ticket descriptions. The role he describes in his books is substantially harder and more substantive than what most people who hold the title actually do. He is not gentle about this. But the harshness comes from respect for what the role could be, not contempt for the people in it.

At a moment when the technology industry is arguing about whether AI will eliminate product managers, or transform them, or leave them unchanged, Cagan's framework offers a useful anchor. What AI cannot replace is the judgment required to identify a problem worth solving, the empathy required to understand why it matters to real people, and the courage required to advocate for a solution when stakeholders would rather just ship another feature. That, according to Cagan, is what product management actually is. Everything else is theater.