Andy Grove's High Output Management, re-read at 40
Written in 1983 by the man who ran Intel. Still more useful than most management books published this decade. What holds, what's dated, and what supply chain managers specifically should take from it.
High Output Management was published in 1983. Andy Grove was President of Intel at the time — the company that had essentially invented the microprocessor and was in the process of becoming one of the most important industrial organisations in human history. Grove wrote the book as a practical management manual. Not a philosophy. Not a collection of anecdotes with morals attached. A manual.
The book is still in print. Ben Horowitz, co-founder of Andreessen Horowitz, called it "the best book for managers." It is assigned reading at several major technology companies. It is cited by practitioners across industries with the kind of reverence usually reserved for much older texts.
I re-read it in 2025, twenty-two years after first picking it up. The experience was disorienting in the specific way that re-reading a good book at a different age always is: the parts I had found interesting in my twenties had become so obvious as to be invisible, and the parts I had skimmed had become the most important parts.
The central argument
Grove's central argument is deceptively simple: a manager's output is the output of the teams they manage. Not their individual contribution. Not their decisions in isolation. The aggregate output of the people they are responsible for.
This sounds obvious. Most management writing says something like it. What Grove does that most management writing doesn't is trace every implication of this principle with genuine rigour.
If a manager's output is the team's output, then the manager's primary leverage point is the things that affect the entire team simultaneously — not the things that affect one person at a time. A one-hour meeting with twenty people is a twenty-hour investment of collective time. If that meeting improves everyone's decision quality by even a small amount, it is among the highest-leverage activities available. If it doesn't, it is twenty hours wasted.
Grove introduces the concept of managerial leverage — the ratio of output produced to time invested — and argues that high-leverage activities should dominate a manager's time. He defines high-leverage activities as those that:
- Affect many people or decisions simultaneously
- Enable downstream work to proceed that would otherwise be blocked
- Provide information that prevents costly mistakes
This framework has not aged.
The production analogy and why it matters for supply chain
Grove spent his career in manufacturing before moving into management. His mental model for management is explicitly a production model. He treats a manager's work as a production process with inputs, throughput, and outputs, and applies the same analysis he would apply to an assembly line.
This is not a metaphor. He means it literally. He describes one-on-ones, staff meetings, and process discussions as production operations with cycle times, yield rates, and bottlenecks. He asks the same questions of management work that a factory engineer would ask of a production line: Where is the constraint? What is the throughput? Where is quality being lost?
For supply chain professionals, this analogy is unusually accessible. The concepts are not foreign — they are the same concepts applied to a different domain. A demand planner who understands cycle time in a planning process, batch sizes in a review cadence, and throughput in a decision-making workflow is doing Grove-style analysis whether or not they know it.
The specific supply chain application that Grove's framework illuminates best is the cost of management delay as a supply chain constraint. In most supply chain environments, decisions are the real bottleneck — not the physical supply chain. The factory can produce faster if someone decides to release the production order. The purchase order can be placed if someone approves it. The forecast can be adjusted if someone owns the call.
Grove's framework asks: who is the constraint in your management system? How much output is being lost each day because a decision is waiting for a person who is busy, unavailable, or unclear about their authority? This is inventory in the management process — work-in-progress decisions that are consuming working capital in the form of time and organisational attention.
The performance review chapter
The chapter on performance reviews is the part I had skimmed in my twenties and the part that stopped me cold on re-reading.
Grove's argument: a performance review is the single highest-leverage management activity available to a manager. It is the moment when a manager communicates, with maximum clarity and specificity, what the organisation values, what the individual has done well, what they must change, and what the path forward looks like. Done well, it changes behaviour for the next twelve months. Done poorly — with vague praise and diplomatic avoidance of criticism — it confirms that mediocre performance is acceptable.
He writes: "The manager should think of himself as a mirror. If the mirror is blurry — if the manager is unclear, avoidant, or inconsistent — the person looking into it gets a distorted reflection. They cannot improve based on a distorted reflection."
The performance review chapter is the most direct thing I have read about why most management feedback fails: not because managers are malicious, but because clarity is uncomfortable and most managers optimise for the comfort of the conversation rather than the utility of the feedback.
Grove's prescription is specific: the review should be written before it is given. The writing forces clarity. Verbal reviews are too easy to adjust in real time based on the recipient's reaction. A written review requires the manager to commit to an assessment before they are in the room — and committing to an assessment is the discipline most managers avoid.
The one-on-one as an information system
Grove describes one-on-ones as the primary mechanism by which managers obtain accurate information about what is actually happening in their organisation. Not status updates. Not dashboards. One-on-ones.
His reasoning: formal reporting systems produce information that has been filtered, formatted, and selected by the people who prepared it. They are not wrong, but they are optimised for a purpose — presenting progress, managing perceptions, demonstrating compliance. The informal signal that tells a manager what is actually going wrong travels in a different channel: the hesitation before an answer, the problem mentioned at the end of a conversation, the question asked by a person who doesn't want to ask it officially.
One-on-ones, done well, are the mechanism for extracting this signal. They require the manager to ask questions that don't have politically correct answers: What's frustrating you? What are you worried about? What's taking longer than it should? What do you think we're getting wrong?
The supply chain application is direct. An IBP process that produces the right numbers in the system but fails to surface the demand planner's concern about a promotional assumption is an information system with a quality problem. The numbers are right. The judgment behind them is wrong. One-on-ones between the planning director and the demand planners — with the specific purpose of surfacing concerns that the system won't capture — are Grove's information mechanism applied to planning.
What's dated
Three things have aged poorly.
The book assumes a factory context. Grove's examples are heavily drawn from Intel's manufacturing operations. The concept of managerial leverage translates cleanly to knowledge work, but the production analogies sometimes require translation. A reader with no manufacturing background will find some sections opaque.
The diversity of the workforce is invisible. The book was written in 1983 Silicon Valley. The management model assumes a relatively homogeneous workforce — same values, same career aspirations, same definition of professional performance. The manager as mirror works differently when the mirror needs to be calibrated for people with different backgrounds, communication styles, and relationships to institutional authority. Grove doesn't address this because it wasn't the problem he was solving for.
The speed assumption is different. Grove's planning cycles, decision rhythms, and review cadences were designed for a world where information moved at the speed of memos and quarterly reports. The book assumes a slower tempo. The specific cadences he recommends — monthly staff meetings, quarterly reviews — may need adjustment for environments where decisions need to move faster and information is continuous.
The verdict
Five stars. Not because it's perfect, but because it is the most practically useful management book written in English. The framework is rigorous, the prescriptions are specific, and the production analogy is genuinely clarifying for anyone who works in operations.
Supply chain managers specifically: the chapter on managerial leverage applied to your planning process is worth the cost of the book alone. The question "where is the bottleneck in my management system?" is a more useful question than most of the things your IBP consultant will ask you.
Re-read it every five years. It gets better.
Sources
- Grove, A. S. (1983). High Output Management. Random House.
- Grove, A. S. (1996). Only the Paranoid Survive. Doubleday.
- Horowitz, B. (2014). The Hard Thing About Hard Things. HarperCollins. (Foreword to Grove re-release.)
- Drucker, P. F. (1954). The Practice of Management. Harper & Row.
- Goldratt, E. M., & Cox, J. (1984). The Goal: A Process of Ongoing Improvement. North River Press.
- Kim, G., Behr, K., & Spafford, G. (2013). The Phoenix Project. IT Revolution Press.