# High Output Management

> Managerial leverage, 1:1s, OKRs, task-relevant maturity — an AI agent skill based on *High Output Management* by Andrew S. Grove.

Published 2026-06-11 · Updated 2026-08-17 · Team & Operations · Free and MIT-licensed
Canonical: https://skills.wondel.ai/skills/high-output-management/
Source: https://github.com/wondelai/skills/tree/main/high-output-management

**Install:** `npx skills add wondelai/skills/high-output-management --global`

## What is the High Output Management skill?

Every hour a manager spends has a multiplier, and High Output Management is the skill that makes your AI agent compute it. Andy Grove’s Intel-era manual supplies the equation — a manager’s output is the output of their organization — and your agent applies it to your calendar, your metrics, your 1:1 cadence, and how decisions get made.

## Key concepts from High Output Management your agent applies

- **Managerial Leverage** — Activities differ by orders of magnitude in output per hour — choose high-leverage work like training and well-prepared decisions; eliminate meddling and waffling.
- **Output Indicators** — Measure output, not activity — and pair every quantity metric with a quality counterpart so neither can be gamed.
- **One-on-Ones** — The subordinate's meeting: they own the agenda, you listen and take notes. Set frequency by task-relevant maturity, not seniority.
- **Clean Decisions** — Free discussion, clear decision, full support — made at the lowest competent level, with decider and ratifier named in advance.
- **Task-Relevant Maturity** — No universally good management style: structure for the new-to-task, light monitoring for the experienced — per task, not per person.

## When to use High Output Management — and when not to

Reach for it when:

- Your week is full, your team’s week is not productive, and you can’t say which hours multiplied anything.
- Every decision routes through you for approval, and work sits waiting while you are in other meetings.
- You run 1:1s at one cadence for everyone, from last month’s hire to your most experienced engineer.
- The dashboard counts activity — tickets closed, features shipped — with nothing pairing it to quality.

Reach for something else when:

- You want a whole-company operating system with fixed artifacts and a weekly rhythm — that is Traction EOS.
- Teams are structurally in each other’s way, which no 1:1 will fix — Team Topologies redraws boundaries.
- The disengagement is about autonomy and purpose rather than technique — Drive Motivation goes at the cause.
- Nobody has decided what the organization should be doing at all — Good Strategy Bad Strategy comes first.

## About Andrew S. Grove

Legendary Intel CEO, Time's 1997 Man of the Year. Andrew S. Grove (1936–2016) fled Hungary at twenty, became Intel's third employee, and rose to president, CEO, and chairman, driving the famous pivot from memory chips to microprocessors. Time's 1997 Man of the Year, his management-by-objectives system became the OKR method now standard across tech.

More: https://en.wikipedia.org/wiki/Andrew_Grove · https://www.wikidata.org/wiki/Q432929
The book: https://openlibrary.org/books/OL533591M/High_Output_Management · https://en.wikipedia.org/wiki/High_Output_Management · https://www.wikidata.org/wiki/Q124830345

## Example prompts

- Redesign my weekly calendar around high-leverage activities using high-output-management skill _(Time management)_
- Build paired output indicators for my engineering team using high-output-management skill _(Metrics design)_
- Set up a 1:1 cadence and agenda template for my reports using high-output-management skill _(Meetings)_
- Draft cascading OKRs for next quarter that stretch without sandbagging using high-output-management skill _(Planning)_

## Frequently asked questions

### How do I install the High Output Management skill?

Run `npx skills add wondelai/skills/high-output-management --global`. It takes about 30 seconds and needs no account. The High Output Management skill then works in Claude, Claude Code, Claude Cowork, Codex, Cursor, OpenClaw and Hermes Agent — anything that reads the open agentskills.io format — and your agent loads it on its own when a task calls for it. It is free and MIT-licensed, and the source is at https://github.com/wondelai/skills.

### Which book is the High Output Management skill based on?

It packages *High Output Management* by Andrew S. Grove — legendary Intel CEO, Time's 1997 Man of the Year. The skill distils the book's method into instructions your agent follows while it works, covering managerial leverage, output indicators and one-on-ones. It sits in the Team & Operations part of the library.

### What does Grove mean by managerial leverage?

The output produced by an activity divided by the time it took — and activities differ by orders of magnitude. Training your team, a decision made before others are blocked, a standard communicated once to twelve people: all high leverage. Grove also names negative leverage, where your hours actively reduce output — meddling in an expert’s work, waffling on a decision people are waiting for, broadcasting your own gloom. The skill sorts a real calendar along that axis.

### How is this different from the Team Topologies skill?

Ask what breaks when the manager goes on holiday. If the answer is that decisions queue, quality slips, and nobody was trained, that is a leverage problem and this is the skill. If the answer is that work still crawls because three teams must coordinate for any change, no amount of 1:1 craft will help — the boundaries are wrong, and Team Topologies is the tool. Management technique cannot out-run a bad org chart.

### Do I have to read High Output Management?

The tools transfer cleanly into the skill: leverage, paired indicators, the subordinate-owned 1:1, task-relevant maturity, and the free-discussion-then-clear-decision model. What resists compression is the opening third, where Grove runs an entire breakfast factory as an analogy and teaches you to see your team’s work as a process with a limiting step. People who have read it think differently about scheduling forever.

### It was written in the 1980s. Does it still hold up?

The core ideas do, and OKRs came out of this book’s management-by-objectives chapter. The context shows in places: Grove writes from a large, hierarchical manufacturing and engineering company, so the dual-reporting structures and meeting taxonomies assume more organization than a ten-person startup has. The skill leans on the durable parts. If you have no direct reports yet, most of its value is still ahead of you.

## Related

- All Team & Operations skills: https://skills.wondel.ai/skills/team/
- Traction EOS: https://skills.wondel.ai/skills/traction-eos/
- Drive Motivation: https://skills.wondel.ai/skills/drive-motivation/
- Team Topologies: https://skills.wondel.ai/skills/team-topologies/