The CEO of the Product Mindset
Own your product's success completely—no excuses, no dependencies
The CEO of the Product Mindset reframes the product manager role from coordinator and project manager into the role of chief executive of the product. A good product manager takes full responsibility for the product's success and measures themselves by outcomes, not activity. They know the market, the product, the product line, and the competition extremely well and operate from a strong basis of knowledge and confidence. They understand the context going in—company strategy, revenue, funding, competitive landscape—and take responsibility for devising and executing a winning plan. There are no excuses. Bad product managers, by contrast, have lots of excuses: not enough funding, the engineering manager is incompetent, the competitor has ten times the resources, they are overworked, they lack direction. The framework draws a sharp line: if a CEO would not make those excuses, neither should the CEO of a product. This mindset shift transforms how you prioritize, communicate, and ultimately whether your product wins.
- A good product manager is the CEO of the product—they take full responsibility and measure themselves by the product's success
- There are no valid excuses for product failure; if a CEO would not make the excuse, neither should a PM
- Product managers define the 'what,' not the 'how'—they are the marketing counterpart of the engineering manager
- Knowledge is the foundation of confidence: know the market, product, product line, and competition extremely well
- Good PMs manage the product team; they are not part of it, and they are not gophers for engineering
- Build Deep Market and Product KnowledgeInvest heavily in understanding your market, product, product line, and competition before making any decisions. This means talking to customers regularly, studying competitive products firsthand, understanding pricing dynamics, and knowing your company's strategic context including revenue, funding, and positioning. Good product managers operate from a strong basis of knowledge and confidence—this is not optional background work, it is the foundation everything else rests on.Pro tipSpend at least 20% of your time with customers and in competitive analysis. PMs who lose touch with the market start making decisions based on internal politics rather than external reality.
- Define the 'What' With Written ClarityCrisply define the target and what the product must deliver, as opposed to how it should be built. Communicate this in writing—not informally, not verbally in hallway conversations. Good product managers take written positions on important issues: competitive responses, architectural choices, product decisions, markets to attack or yield. Written positions create accountability, enable asynchronous alignment, and force the clarity that verbal communication allows you to dodge.WarningBad product managers feel best about themselves when they figure out the 'how.' Resist this temptation. Your job is the what and the why.
- Anticipate Problems and Build Solutions ProactivelyGood product managers anticipate serious product flaws and build real solutions before they become crises. Bad product managers put out fires all day. The difference is proactive analysis versus reactive scrambling. This requires maintaining a running assessment of your product's vulnerabilities—technical, competitive, and market-related—and addressing them before they explode into emergencies that consume your entire team's bandwidth.Pro tipKeep a living document of your product's top five risks and review it weekly. If you are surprised by a product crisis, your risk radar needs recalibration.
- Create Leverageable CollateralBuild FAQs, presentations, white papers, and other materials that scale your knowledge beyond one-on-one conversations. Bad product managers complain they spend all day answering questions for the sales force and are swamped. Good product managers create resources that answer those questions systematically, freeing their time for strategic work. Every repeated question is a signal that you need to create a document, not have another conversation.Pro tipTrack the questions you answer most frequently for one week. The top five recurring questions become your first five FAQ documents.
- Focus the Team on Revenue and CustomersGood product managers focus the team on revenue and customers. Bad product managers focus the team on how many features the competitor is building. This distinction is critical because competitive feature-matching is a losing strategy that cedes your product roadmap to the competitor's decisions. Instead, orient every prioritization conversation around: what do customers need, and what drives revenue? Define products that can be executed with strong effort, not theoretical perfection that engineering cannot actually build.
Horowitz wrote this document while at Netscape, competing against Microsoft's Internet Explorer team that had orders of magnitude more engineers and resources. The bad PM mindset would say 'Microsoft has ten times as many engineers working on it' as an excuse for losing. The good PM mindset—which Horowitz demanded—was to take full responsibility for devising and executing a winning plan regardless of competitive resource disparities.
Horowitz contrasts how good and bad PMs handle press and analyst relations. Bad product managers try to cover every feature and be technically accurate, assuming press and analysts are dumb when they do not understand technical distinctions like 'push' versus 'simulated push.' Good product managers think about the story they want written, ask the press questions rather than just answering them, and assume press and analysts are smart people who need compelling narratives rather than technical specifications.
Ben Horowitz wrote this document as an internal training guide while at Netscape in the late 1990s, where he managed product teams competing against Microsoft's Internet Explorer. The pressure of competing against a company with vastly superior resources forced clarity about what separated effective product managers from ineffective ones. The document was originally a practical tool to train new PMs, not a public manifesto. Horowitz later published it through Andreessen Horowitz as an example of a useful training document, noting it was fifteen years old, but its core insights about ownership, accountability, and clarity have made it one of the most widely cited product management documents in technology history.