Editorial take
Grove ran Intel through the most operationally consequential decade in computing and then wrote down how. The book treats management as production — inputs, outputs, leverage, throughput — which still feels radical because most management writing treats it as therapy. The chapters on one-on-ones, on the rhythm of operational meetings, and on the math of high-leverage activities are foundational. If you've ever wondered why one-on-ones at Stripe, Plaid, and Asana all look weirdly similar, it's because their founders all read this. Read it before you have direct reports; reread it the day you cross 20 of them.
Last hand-checked 2026-05-18, The 1995 revised edition is the canonical one — earlier printings are out of print.
Read if you …
- are about to start managing people, or just did
- want to understand management as a system rather than a personality test
- are responsible for any kind of operational throughput, not just engineering teams
Skip if you …
- you want recent case studies — examples are 80s manufacturing-shop coded
- you're looking for emotional / EQ-heavy leadership writing
If you only read one chapter
Managerial Leverage
The book's intellectual core. Once you internalize the leverage formula, you will never staff a meeting the same way again.
Key ideas
- A manager's output = the output of their organization + the output of neighboring organizations under their influence.
- Train and motivate — these are the only two reasons people fail to perform.
- The single most important task of a manager is to elicit peak performance from subordinates.
- Meetings are the medium of managerial work.
About the book
Andy Grove's distillation of how Intel actually ran in the 1980s. It opens with a metaphor — running a breakfast restaurant — and uses it to teach process flow, indicator design, and capacity planning before pivoting to its real subject: how managers create output through other people.
The book's structural insight is that the same principles govern manufacturing lines and management teams: identifying limiting steps, designing pairs of indicators (one quantity, one quality) so you can't game them, and thinking in leverage rather than effort. Forty years on, this remains the operating manual most often re-recommended by working operators.
Pairs with
If High Output Management works for you, these likely will too.
An Elegant Puzzle
PickWill Larson · 2019
The book most engineering managers will recommend to their successors.
Read if you are a first-time or second-time engineering manager.
framework200–350pintermediateThe Hard Thing About Hard Things
PickBen Horowitz · 2014
The closest thing to a war diary that a Valley CEO has ever published — and the rare founder book that's better the second time.
Read if you are a first-time founder or CEO and want a realistic preview of the role.
memoir200–350pintermediate