What Makes a Product Manager the CEO of Their Product? Lessons from Microsoft

This article presents a Microsoft product manager’s perspective on the role of product managers, noting that Microsoft treats a PM as a small‑business unit CEO who oversees organization, coordination, strategy, planning, design, marketing, and market responsibilities—a talent that is especially scarce in China.

In China, product managers often focus on user needs, experience, and micro‑innovation, and many are simply called PMs despite only a few truly fulfilling the comprehensive CEO‑like responsibilities; most are more akin to assistant product managers.

The author reflects on the elite product‑manager model used by foreign firms like Google, which demand high standards and often a technical background, versus the broader product‑team model common in Chinese internet companies, urging readers to view the PM as representing the entire product team rather than an individual.

Translation of the original article: A good product manager deeply understands the market, product, product line, and competition, and operates the product with confidence as its CEO, measuring personal success by product success. They are accountable for launching the right product at the right time and handling all related issues. Good PMs devise and execute successful plans without excuses. Bad product managers make excuses such as insufficient funding, incompetent development managers, or excessive engineering resources, and should avoid such rationalizations.

The commentary emphasizes that the product‑CEO concept sets the highest expectations for a PM, highlighting the importance of a positive mindset, self‑control, and refusing to blame others.

Product managers should not let their time be drained by other departments; they must organize time effectively, avoid taking meeting minutes, and not act as information retrieval tools for engineers. Instead, they manage the product team and serve as partners and liaisons between engineering and market.

Good PMs set clear goals (the "what") rather than focusing on how, communicate clearly with engineering teams, and gather informal information without providing informal direction.

Good PMs produce useful market collateral such as FAQs, demos, and whitepapers, whereas bad PMs spend all day answering sales questions.

Good PMs address serious product defects with real solutions; bad PMs merely put out fires.

On critical issues—competition, architecture choices, product decisions, market entry or exit—good PMs document their thoughts in writing; bad PMs speak verbally and complain about higher‑ups.

Good PMs focus on revenue and customers, defining achievable products; bad PMs chase feature lists that are often unrealistic and burden engineering teams.

Internally, good PMs plan how to deliver superior market value; externally, they strive for market share and revenue targets. Bad PMs lack clarity on value, competitive advantage, pricing, and scalability.

Good PMs categorize problems effectively, while bad PMs conflate them.

Good PMs avoid the trap of merely adding features without addressing true user needs, recognizing that feature bloat can slow performance and limit user growth.

When dealing with media, good PMs craft compelling stories, ask insightful questions, and respect analysts; bad PMs demand exhaustive coverage of every feature and dismiss media as uninformed.

Good PMs prioritize clear problem definition over explaining obvious phenomena, define their work and success metrics, and consistently send weekly status reports; bad PMs neglect reporting and discipline.

The commentary concludes that a product manager must maintain a positive attitude, self‑motivation, and even self‑mockery, as the product’s future ultimately lies in the hands of the PM.

Original author: Ben Horowitz, Director of Product Management, Summer 1996.