High Output Management by Andrew S. Grove, first published by Random House in 1983, is a management manual written by the man who ran Intel. Grove wrote it for middle managers, and it has since become a favourite among startup founders and venture capitalists. The book treats management as a skill that can be measured and improved, using the language of a factory to explain how offices work.
What is High Output Management about?
Grove opens with a breakfast factory. To serve an egg, toast and coffee at the same moment, you have to plan around the slowest step, inspect quality early and keep the right amount of stock. He uses this simple operation to introduce ideas such as the limiting step, early indicators and the cost of catching a defect late. The point is that any work, from writing software to closing deals, has inputs, steps and outputs you can manage.
The book’s central claim is that a manager’s output equals the output of their team plus the teams they influence. A manager adds value through activities that multiply other people’s work: gathering information, making decisions, nudging people, setting an example and teaching. Grove argues that one hour spent training a new hire or making a clear decision can improve the work of many people for months, so managers should pick those activities first.
The rest of the book covers the tools. Grove explains one-on-one meetings, run by the employee with the manager mostly listening, and two types of meetings: regular process meetings and mission meetings called to solve one problem. He describes how to make decisions in groups, how to set objectives with measurable results (the method John Doerr later spread as OKRs), how to structure a company that mixes product teams and shared functions, and how to give honest performance reviews. He also introduces task-relevant maturity: how closely you manage someone depends on how experienced they are at that particular task.
What are the main lessons for founders?
- Measure your week by team output. At the end of each week, ask which of your activities raised the team’s results. Drop or delegate the rest.
- Hold regular one-on-ones. Thirty minutes every week or two with each direct report, with an agenda they prepare, surfaces problems long before they explode.
- Track a few early indicators. Pick signals that warn you before results drop, such as qualified leads or support tickets, and look at them weekly.
- Match supervision to experience. Give a new hire on an unfamiliar task close guidance, and give an experienced person on a familiar task room and a light touch.
- Teach in person. Founders hold most of the company’s know-how. A short training session from you beats any document.
Who should read High Output Management?
It is ideal for founders whose company has grown to the point where they manage managers, roughly 15 to 100 people. First-time managers in any startup get a clear model of what their job is. Engineers and operators who think in systems find Grove’s production metaphors easy to apply.
Pre-launch founders working alone can save it for later. The book assumes you already have a team and a process worth improving.
How do you put High Output Management to work this week?
- Schedule a recurring one-on-one with each person who reports to you, and ask them to bring the agenda.
- Choose two early indicators for your most important outcome and set up a simple weekly tracker.
- Review last week’s calendar and mark each meeting as process or mission. Cancel any that are neither.
For more founder-level advice on running a growing team, blog.mean.ceo publishes practical guidance for CEOs on managing people, time and decisions.
Where does High Output Management fall short?
The examples come from Intel in the early 1980s, with memos, factories and office hierarchies that feel dated next to remote, async startup teams. Grove writes from inside a large, well-funded company and says little about managing with no money or no structure at all. The tone is dry and engineering-heavy, which suits some readers and loses others. It also treats people mostly as contributors to output, with little on motivation or wellbeing. For the emotional side of leading through crises, read The Hard Thing About Hard Things.