The reading room · Digna Legi
Good Product Manager, Bad Product Manager
/100
80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.
Evidence-reviewed score based on available publisher text. The text itself warns that it was written 15 years ago, so modern applicability is partly context-dependent.
Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.
How scoring works →This brief · about 2 min with detail
Why read this
Strong product management means accountable ownership of outcomes, not coordination, excuse-making, informal opinions, or unmanaged feature pressure.
AI brief · Checked against source text
The main idea
The piece argues that strong product managers own outcomes: market knowledge, product success, target definition, and a winning plan. Its core distinction is not effort versus laziness, but leverage versus absorption: good PMs clarify the “what,” write reusable materials, anticipate failures, and focus teams on customers and revenue; bad PMs drift into excuses, informal opinions, firefighting, and unmanaged feature pressure.
Go a little deeper
Ownership is defined by accountable choices
The memo ties ownership to a concrete constraint list: company context, revenue and funding, competition, and available resources. The good product manager uses that knowledge to devise and execute a plan. The contrasting bad-PM pattern substitutes complaints about funding, engineering capacity, competitors, or a busy workload for responsibility for the product’s success.
Leverage beats availability
A recurring mechanism is converting repeated demands into durable artifacts. The good PM does not become the sales team’s answer desk or engineering’s helper; they create written collateral, crisp decisions, and reusable explanations. That preserves attention for judgment while making the organization less dependent on ad hoc clarification.
How the case is made
The case is made as a sharp practitioner taxonomy contrasting repeated good and bad behaviors.
Where the idea has limits
The author introduces this as an old memo and questions how relevant it remains to the product-manager role.
A question to take away · from Digna Legi
Where are you acting as a product owner, and where are you merely absorbing organizational noise?
What the original adds
The original includes a fuller checklist of contrasts across engineering, sales support, press relations, discipline, planning, and competitive thinking.
Why return to this
Return to this when meetings, feature lists and firefighting start standing in for product outcomes. Its sharp contrasts give you concrete behaviours to examine: written decisions, customer value and responsibility for the result.
Product managers defining what they own.
Horowitz introduces this as an old training document and questions its relevance to modern PMs. Treat the CEO metaphor as a prompt about responsibility, not a literal description of authority.
About this brief
AI-written, then separately checked for source support, useful detail and clarity. The author’s claims and our editorial question are kept separate. The original remains the author’s work. How we select and summarise →
How was this brief?
Rate this summary, separately from the author’s article.
Optional. Saved in this browser; shared only if you allow analytics.
How was the original article?
Rate the author’s original after reading it.
Optional. Saved in this browser; shared only if you allow analytics.
Digna legi. Worth reading.