high-output-management

High Output Management

Andrew S. Grove's operating system for managers — distilled from High Output Management (Random House, 1983; Vintage reprint 2015 with Ben Horowitz's foreword), his strategy follow-up Only the Paranoid Survive (Currency, 1996), his HBR articles and Stanford GSB teaching, and the roster of modern carriers who keep his method alive (Ben Horowitz at a16z, John Doerr on OKRs, Julie Zhuo, Claire Hughes Johnson, Robert Burgelman).

Grove was Intel's third employee, its CEO from 1987 to 1998, and Time's Person of the Year in 1997. He wrote HOM as an unironic management manual for the middle manager at a chip factory. Four decades later it is the single most-recommended management book in Silicon Valley — Zuckerberg, Chesky, Houston, Collison, Horowitz, Andreessen all hand it out.

This skill helps the assistant think in Grove's mechanics, not just cite his book. Grove is opinionated because he was an engineer: management is a production system, output is the team's output, and every ambiguity in the system has a specific instrumentation. Applying the frameworks without the mechanics (weekly one-on-ones that are status meetings, OKRs that are wishes, "delegation" without monitoring) is the thing Grove would have called out coldly in a Stanford classroom.

A note on Grove being dead. Grove died 2016-03-21. The book is closed; the ideas are alive because named carriers keep publishing on them. This skill treats Ben Horowitz's essays, John Doerr's OKR canon, Julie Zhuo's first-time-manager translation, and Claire Hughes Johnson's operational playbook as legitimate extensions of Grove — always attributed as extensions, never blurred with the source. See references/post-book.md and references/author-live-sources.md.

When this skill activates

Use this skill when the user is:

• Designing, fixing, or running one-on-ones — cadence, agenda, what to talk about, why they're not working.
• Auditing their meeting stack — which are process-oriented, which are mission-oriented, which shouldn't exist.
• Running a decision meeting that keeps drifting — no one knows who decides, or the decision doesn't stick.
• Setting up or debugging OKRs / cascaded goals — especially when the OKRs feel disconnected from strategy or from daily work.
• Delegating and worrying about micromanagement (or being accused of it) — the task-relevant maturity call.
• Giving a hard performance review or dealing with an underperformer.
• Hiring: designing interview loops, deciding what to ask, whether to promote.
• Transitioning from IC to manager, or manager to manager-of-managers.
• Suspecting the business is at a strategic inflection point — 10X change, whether to pivot, what to listen for.
• Rebuilding culture around directness / constructive confrontation without it turning into cruelty.
• Reading HOM / Only the Paranoid Survive / Horowitz / Doerr / Zhuo / Hughes Johnson and wanting a thinking partner.