High Output Management: a manager's output and leverage

Who should use it, and when not to

Use it when a manager is busy all week but the team's results don't move, when a newly promoted manager still does most of the hands-on work, or when planning where a manager's time should go next quarter.

It is a book about running an organization that already works. If the company faces an existential threat, the priorities change, see The Hard Thing About Hard Things. For the goals themselves, see Measure What Matters.

The core ideas

Management as production. Grove opens with a factory example, a breakfast with an egg, toast and coffee, to explain production, bottlenecks and indicators. He then treats a manager's work the same way: inputs, outputs and measures.

The manager's output. A manager's own hands-on work counts only as one person's work. What counts is the output of the organization and of the teams they affect. Ben Horowitz's foreword to the 2015 edition highlights this equation.

Leverage. Some activities affect many people or a long time: teaching a process, a decision that unblocks a team, a clear goal. Grove's advice is to spend more time on those.

Can't or won't. When someone isn't doing their job, either they can't (train them) or they won't (motivate them). The book's last chapter argues that training is the boss's job.

Task-relevant maturity. How closely to manage depends on the person's experience with that specific task, not their seniority.

One-on-ones and meetings. The book treats the one-on-one as a core management tool, and distinguishes meetings that share information from meetings that make decisions.

A worked mini example

This is an illustration. A support lead spends 14 hours a week answering tickets, 6 in meetings, 2 on one-on-ones and none on training. Sorting the week by leverage shows the tickets are the lead's own work. Two hours teaching a newer agent how to handle escalations, and one hour a week raising support's needs with the product team, would raise the output of the whole support team and of a neighbouring one. The experienced billing agent can take billing tickets over outright; the new agent needs pairing first.

How to audit your own week

1. List a typical week, each activity with its hours.
2. Label each activity: raises my team's output, a neighbouring team's, or my own hands-on work.
3. Find your own work someone else could own, and note how experienced they are at it.
4. Delegate to the experienced, train the new.
5. For each performance gap, write whether it looks like can't or won't, with evidence.
6. Check one-on-ones: who hasn't had one recently.
7. Check next quarter's goals: do they measure output, and can each be graded met or not met?

The Grove-style managerial leverage audit skill runs these steps on your calendar. To prepare a single one-on-one, use the one-on-one prep skill.

Common mistakes

• Counting your own tickets as output. A manager's hands-on work is the least leverage they have.
• Treating everyone the same. The right amount of supervision depends on the task, not the title.
• Skipping training because it's slow. Grove saw it as one of the highest-leverage activities.
• Meetings with no purpose. Decide whether a meeting is for sharing or deciding.

Where it comes from

Andrew S. Grove joined Intel at its founding and later became its chief executive. He wrote High Output Management in 1983, about the methods he used there. A new edition appeared in 2015 with a foreword by Ben Horowitz. John Doerr, who learned objectives and key results from Grove at Intel, later wrote about them in Measure What Matters (2018). For more on Grove's ideas from accessible sources, see Andy Grove's OKRs, one-on-ones and managerial leverage.

This page is an independent summary in our own words. It is not affiliated with or endorsed by the author's estate or publishers. The book's title is used only to name it. More explainers are in the business books index.

Questions

What is the main idea of High Output Management?

That a manager's output is not their own work but the output of their team, plus the teams they influence. A manager's job is to choose the activities with the most leverage on that output.

What is task-relevant maturity?

How experienced someone is at a specific task. Grove argued that a manager should be hands-on with someone new to a task and delegate more to someone experienced in it.

Did High Output Management introduce OKRs?

The book describes the objectives and key results system Grove used at Intel. John Doerr, who learned it there, later popularized OKRs in Measure What Matters.