High Output Management
Source: https://www.penguinrandomhouse.com/books/72464/high-output-management-by-andrew-s-grove/ ↗
Grove ran Intel during its most consequential decades and the book is his operational manual for management — written not as theory but as a description of what he actually did.
The book covers one-on-ones, performance reviews, decision-making, production principles applied to knowledge work, and the concept of managerial leverage (the output of a manager is the output of the organisation under them).
For product direction it is the single most cited management book in Silicon Valley for a reason: it treats management as a craft with specific techniques, not as a soft-skill overlay on top of the real work.
Doerr's Measure What Matters descends directly from Grove's OKR practice. Read it early and reread it often — it improves with experience.
Central argument
Grove's central argument is that management is an engineering discipline: a manager's output is not their own work but the aggregate output of the people and teams they influence, a principle he calls managerial leverage. From this premise he derives a systematic practice — one-on-ones as information-transfer mechanisms, meetings as decision-production processes, performance reviews as the primary tool for raising long-term output — treating each as a production problem with measurable yield. The book insists that applying manufacturing logic (throughput, bottlenecks, limiting steps) to knowledge work is not a metaphor but a rigorous method.
Critique
The framework assumes a relatively stable organizational unit with clear reporting lines and legible output — conditions that describe Intel's division structure but fit less cleanly in cross-functional product organizations where a CPO's leverage runs through influence, coalition, and embedded teams rather than direct managerial authority. Grove's production analogy also risks over-indexing on throughput and measurable indicators, which can crowd out the exploratory, ambiguous work — early discovery, strategic reframing, cultural change — that resists being cast as a process with a defined yield. A thoughtful reader will note the model is most powerful when goals are known and execution is the constraint, and somewhat silent on the harder problem of finding the right goals in the first place.
Why it matters for product
The concept of managerial leverage directly reframes how a product leader should allocate time: a CPO who spends hours in individual delivery decisions is operating at low leverage, while investing that same time in a well-structured one-on-one cadence, a clear OKR architecture, or a decision-rights framework propagates through every team simultaneously. Grove's insistence on treating the one-on-one as the subordinate's meeting — not the manager's reporting mechanism — is a precise corrective to the common failure mode where PMs are managed by status update rather than by genuine obstacle-removal and context-transfer. For organizational design, his distinction between mission-oriented and functional structures maps directly onto the recurring tension between product squads and platform or discipline guilds, giving leaders a principled vocabulary for when to centralize and when to federate.