High Output Management summary: Andy Grove's key ideas for a new manager
High Output Management is a 1983 book by Andrew S. Grove, who ran Intel. Its main idea is that a manager's output is the output of the team they lead or influence, so your time should go to the few things that lift the whole team. This summary covers leverage, one-on-ones, meetings and matching your style to the person, then shows what a first-time manager can use now and who should read it later.
Free · one email
Leverage is the idea. What do you say in the one-to-one?
A ready script for a real hard talk, from a 10-minute lesson: how to open, where to pause, what to ask next. Day 1 is free; plans are $9.99 a month or $39.99 a year after.
Get today's script freeWhat the book is
High Output Management was written by Andrew S. Grove and first published in 1983. Grove was a leader at Intel, the chip maker. The book is about how work gets done in a company, and how a manager can raise the amount of useful work a team does. It is more of a toolkit than a story.
It often appears on lists of management books as a book to read second or third. It is denser than The Making of a Manager, and it is more about systems than about feelings.
The core idea: your output is your team's output
Summaries give the idea like this: a manager's output is the output of the group they supervise or influence. If you spend all day on your own tasks and your team stalls, your output is low, even if you were busy. If you spend an hour that unblocks five people, your output is high.
This is the hardest change for a new manager. You were promoted for doing the work well. Now the work you should do is the work that helps others do theirs.
Leverage: where to put your hour
Grove calls an activity high leverage when a small amount of your time makes a large difference to the team's output. Sources list the kinds of activity where this happens. Here is a way to apply it, in our words:
| Activity | Leverage | Why |
|---|---|---|
| Removing a blocker for the whole team | High | One fix helps many people |
| A one-to-one that sets clear next steps | High | Shapes a person's whole week |
| Teaching one skill to someone who will teach others | High | The effect repeats |
| Doing a task your report could do | Low | Only you gain, and they learn nothing |
| Sitting in a meeting where you add nothing | Low | One hour, no change |
At the end of each week, list your five biggest uses of time and mark each high or low. The list teaches you more than any book.
One-on-ones as a main tool
Summaries say Grove treats the one-on-one as a key leverage tool, not a status check. One summary adds that the meeting belongs to the report, not to you, and a manager who takes it over lowers the team's output even with good intent. So let them set most of the agenda.
A plain way to run it: they bring topics, you ask questions, and you leave with agreed next steps. Start with how to have an effective 1 on 1, copy the one-on-one meeting template, and pick questions from one on one questions to ask employees.
Match your style to the person: task-relevant maturity
Grove's idea of task-relevant maturity, as summaries describe it, is that the right style depends on how skilled and experienced a person is at one specific task. Not at the job overall. The same person can be an expert in one task and new at another.
| Person is... | You do... |
|---|---|
| New to this task | Give clear steps, check often, explain why |
| Doing it well | Set the goal, check on a schedule, stay out of the how |
The table is our simple version of the idea. One summary adds that you should keep watching the work even when the person is experienced, and change your style if the task changes. This links to how to delegate as a manager and how to set expectations.
Meetings are your work
A well-known point from the book is that meetings are the medium of a manager's work, not a break from it. The question is not "how do I have fewer meetings", but "does each one move output?" Decide what each is for, who needs to be there and what changes afterward. Our guide on running a team meeting turns that into a checklist.
What to use in your first month
- Week 1: Do the leverage list. Mark each use of time high or low.
- Week 2: Hold a one-to-one with each person and let them set the agenda.
- Week 3: For each person, note their maturity on their top task. Change how closely you check.
- Week 4: Drop one low-leverage meeting. Tell the team why.
Use it together with the 30-60-90 day plan so the work has dates.
What to know before you read it
- It is old. The first edition is from 1983, and some examples come from factories and offices of that time. The ideas hold; the details may feel dated. Check whether your edition is updated.
- It is dense. Parts read like a business manual. Many people read a chapter at a time.
- It is light on feelings. A hard conversation with an upset person is not the focus. For that, see difficult conversations with employees.
- It fits some jobs better. Work that has counts, such as tickets closed, calls handled or orders shipped, fits it well. Creative or care work needs more translating.
How it compares with the other well-known books
| Book | Best for | Style |
|---|---|---|
| High Output Management | Using your time and running a system | Dense, practical |
| The Making of a Manager | Your first year | Warm, stories |
| Radical Candor | Feedback | Framework, examples |
If you can read only one first, pick the book that matches your problem. Not sure of your problem? Our common new manager mistakes page helps you name it.
A worked example: one week for a shift lead
Say you lead a team of six and your week is full. You list where your hours went: 6 hours fixing other people's tickets, 5 hours in status meetings, 3 hours in one-to-ones, 2 hours on your own project work, 4 hours on email. Now mark each one.
- Fixing tickets, 6 hours: low. Pick the two kinds of ticket that come back most and teach the team to solve them. You lose an hour this week and win many later.
- Status meetings, 5 hours: mixed. Ask whether a shared written update could replace two of them.
- One-to-ones, 3 hours: high. Protect them and do not cancel them when you are busy, because that tells people they come last.
- Email, 4 hours: mostly low. Set two fixed times a day and close it between them.
Next week, measure again. The goal is not a perfect week. It is to move a few hours from low to high each week and see whether your team gets more done. If it does not, change one thing and test again.
Who should read it
Read it if you like numbers and systems, you feel buried in tasks, or you run a team with clear measures. Wait if your problem this week is a person, not a process. A busy week is the wrong time to start a dense book. Start with one idea from the list above, such as the one-to-one, and use it for a month.
Free · one email
Use the one-to-one the way Grove meant it
Our daily lesson gives you a short script for the talks that lift your team most. Day 1 is free.
Get today's script freeQuestions
What is High Output Management about?
It is about how a manager raises the output of a team. Andy Grove says your output is your team's output, so spend your time on what lifts everyone.
What is managerial leverage?
It is how much a small amount of your time raises the team's output. Unblocking many people is high leverage; doing a task alone is low.
Is High Output Management good for new managers?
It is useful for new managers who like systems. It is denser than most first books, so many people read it second.
What does Grove say about one-on-ones?
Summaries say he treats them as a core tool and says the meeting belongs to the report, not the manager.
When was it published?
The first edition came out in 1983. Check the edition you buy, as some are updated.
Sources
- Secondary summaries, read 2026-11-18: Mooncamp, Dan Lebrero, Rework. They are not the book; read it for exact claims.
- Google search suggestions for "high output management", checked 2026-11-18.
- The tables of leverage and style are our own illustrations of the ideas.