High Output Management
Andrew S. Grove
High Output Management is Andrew Grove's account of management as a production process, written while he ran Intel. Its core equation is that a manager's output is the output of their organisation plus the organisations they influence, so the job is to choose high-leverage activities: decisions, training, well-run meetings and the weekly one-on-one, which Grove treats as the subordinate's meeting. It also introduces task-relevant maturity, the idea that how closely to manage someone depends on the person and the task together.
You have the same hours you had before the promotion and twice the demands. Grove's book is the arithmetic for what goes in them: which activities multiply the team's output and which ones only feel productive. Written in 1983 by the man who ran Intel, it is still the manual most working managers pass to each other.
The book in essence
Grove starts with a breakfast factory, to show that any organisation is a production line with inputs, steps, limiting factors and indicators, and then applies the same lens to a manager's day. The equation follows: a manager's output equals the output of their organisation plus the output of the neighbouring organisations under their influence, and never their personal output. From it he derives leverage, the measure of how much an activity changes the output of the people it touches and for how long. High-leverage activities include a clear decision, an hour of training, a well-prepared meeting and information passed at the right moment; low or negative leverage includes doing the work yourself, being late to a meeting of eight, and reviewing everything. The one-on-one is treated as the highest-leverage regular hour a manager has, and it belongs to the subordinate. Task-relevant maturity resolves the question of how closely to manage: it depends on the person and the specific task, not on seniority. Later chapters cover meetings as the medium of managerial work, decision-making, planning, performance review and training as the manager's own job.
First published in 1983 and revised in 1995, the book grew out of Grove's years running Intel's operations and then the company. Its examples are semiconductor plants and 1980s offices; its rules have outlived them and were adopted wholesale by the generation of technology managers who followed.
Who it's for
- Managers who want a way to decide what deserves their hours
- Anyone who has been told to hold one-on-ones without being told what they are for
- Founders and team leads who feel busy and cannot see their output
Who it's not for
- — Readers who want a warm book about people; Grove is precise and a little cold, on purpose
- — Anyone expecting modern examples; the setting is a 1980s chip maker and you translate as you go
Key lessons
01
A manager's output is the team's output
Not your tickets, your reports or your late-night fixes, except as they raise what the team produces. The sentence is hard for an expert to accept and it is the whole job. Sort your week by leverage, protect the high-leverage hours first, and move recurring low-leverage blocks into teaching someone to do them.
A support lead in Izmir answers twenty hard tickets a day and is proud of it. A two-hour guide to the fifteen common refund cases would save the team ten hours a week. She writes the guide, stops taking tickets, and response times improve without her.
02
The one-on-one is the subordinate's meeting
Weekly, on their agenda, with the manager listening and asking one level deeper. Grove's rule of thumb is that an hour in a one-on-one can improve a subordinate's work for two weeks. Cancelled one-on-ones send a message about importance that people receive accurately.
A sales manager in Mersin switches from monthly pipeline reviews to weekly one-on-ones on the salesperson's agenda. In week three the quietest person reveals a two-month-old complaint from the largest client that no review would have surfaced.
03
Task-relevant maturity decides how closely to manage
How much to direct depends on the person and the task together. Someone expert at one thing is a beginner at the next and needs structure there; someone junior may need only the goal on a task they know well. Low maturity wants detailed direction, medium wants two-way discussion, high wants the objective and your absence.
A team lead in Ankara manages everyone the same way and is called a micromanager by one report and absent by another. Sorting each person's tasks by maturity, she gives the senior engineer detailed direction on his first budget and leaves the junior alone on the migration he has done twice.
04
Meetings are the medium of the work
Grove distinguishes process-oriented meetings, the one-on-one, the staff meeting and the review, from mission-oriented ones called to make a decision, and argues that a manager who cannot run both well cannot do the job. A meeting's output is the decisions made and the information moved, not the time spent.
A product manager in Istanbul ends every meeting by reading the decisions with owners and dates. The team, which had been re-deciding the same questions weekly, stops.
Try this today
Mark every block of last week's calendar high, low or negative leverage, then move one recurring low-leverage block next week into teaching someone else to do it.
Quick check
What is a manager's output, in Grove's equation?
Whose meeting is the one-on-one?
Selected quotes
“A manager's output = the output of his organization + the output of the neighboring organizations under his influence.”
“Ninety minutes of your time can enhance the quality of your subordinate's work for two weeks, or for some eighty-plus hours.”