The best management book is from 1983 and most managers haven't read it
Andy Grove ran Intel. His management manual has outlasted everything published since. What a supply chain manager specifically should take from it.
High Output Management was published in 1983. It is still in print. It is assigned reading at several large technology companies. Ben Horowitz called it the best book for managers. It is more useful than most management books published this decade, and the gap is not close.
Grove's central argument: a manager's output is the output of the teams they manage. Not their individual contribution. The aggregate output of the people they are responsible for. This sounds obvious until you trace every implication of it, which Grove does with a rigour that most management writing declines.
The production analogy is what makes the book unusual. Grove spent his career in manufacturing before running Intel. He treats management work as a production process — inputs, throughput, outputs, constraints. He asks the same questions of a staff meeting that a factory engineer would ask of an assembly line: Where is the bottleneck? What is the throughput? Where is quality being lost?
For supply chain managers this analogy is accessible in a way it isn't for people with no operations background. The concept translates directly: decisions are inventory. A production order waiting for approval, a forecast exception waiting for a call, a supplier issue waiting for escalation — these are work-in-progress items consuming organisational time. The manager's job is to reduce the decision cycle time, not to make every decision personally.
Grove's framework applied to demand planning: who is the bottleneck in your management process? How much output is held up because a decision is waiting for someone who is busy or unclear on their authority? The system might be running perfectly and the constraint might be entirely in the management layer above it.
The performance review chapter is the part most worth sitting with.
Grove's argument: a review done well changes behaviour for the next twelve months. Done poorly — vague, diplomatic, avoidant of honest assessment — it confirms that mediocre performance is acceptable. The manager who protects a direct report from uncomfortable feedback is not being kind. They are withholding the information the person needs to improve.
His prescription: write the review before you give it. Writing forces clarity. Verbal reviews are too easy to soften in response to the other person's reaction. A written assessment is a commitment made before entering the room.
What's dated: the diversity of the workforce is invisible (1983 Silicon Valley), and the planning cadences assume a pre-digital pace. Adjust accordingly.
What hasn't aged at all: managerial leverage, the production model, the one-on-one as an information system, and the performance review as the highest-leverage management activity available.
Re-read it every five years. It gets better.
Five stars.
Full review: High Output Management, re-read at 40