Manage teams the way Andy Grove ran Intel: a manager's output is not what the manager does — it is what their organization produces. This skill turns High Output Management into auditable practice: production principles for knowledge work, output indicators, managerial leverage, meetings as the medium of management, clean decisions, OKRs, and a management style matched to task-relevant maturity.

A manager's output = the output of their organization + the output of the neighboring organizations under their influence. Nothing a manager does — emails, meetings, reviews, decisions — counts in itself; it counts only through how it raises that combined output. Since managerial time is the scarce input, the craft reduces to one question asked relentlessly: of everything I could do right now, what creates the most output per hour spent? Choose high-leverage activities; eliminate negative-leverage ones.

Goal: 10/10. Rate management practices, calendars, and processes 0-10 against the principles below. State the current score and the specific changes needed to reach 10/10.

Core concept: Grove's breakfast factory — deliver a three-minute egg, buttered toast, and hot coffee simultaneously, at acceptable quality and lowest cost — contains all of production: build the flow around the limiting step (the egg), fix problems at the lowest-value stage, batch where setup costs dominate, and choose deliberately between building to forecast and building to order. Every team — engineering, support, recruiting — runs a production line, whether or not anyone has drawn it.

Why it works: Knowledge work hides its assembly line, and invisible flow invites firefighting. Production thinking makes flow visible: once you know the limiting step, everything else gets scheduled around it; once defects are caught at the egg stage instead of on the customer's plate, fixing them costs a fraction.

Ethical boundary: Run systems hot, not humans — production thinking optimizes the work, never treats people as interchangeable machines.

See: references/indicators-and-production.md when finding a limiting step or building a dashboard — limiting-step analysis, worked indicator pairs, leading vs trend indicators, stagger charts, and how to run an operation review.

Core concept: Measure output, not activity — what the team shipped that survived, not how busy it looked. Pair every quantity indicator with a quality counterpart so neither can be optimized at the other's expense, favor leading indicators that buy time to act, and report forecasts in stagger charts that show how each forecast evolved.

Why it works: People do what management measures, so an unpaired indicator is an instruction to game it. The pair closes the loop: push throughput and the escape rate exposes the corner-cutting. Leading indicators and stagger charts convert measurement from autopsy to steering.

Ethical boundary: Indicators measure the work, not the worker — used for surveillance, they teach people to optimize the number instead of the output.

Core concept: Leverage is the output created per unit of managerial time. High-leverage activities affect many people at once (training, well-prepared decisions, information gathering) or redirect months of work with a small, well-timed nudge. The calendar is the manager's production system: forecast the key events, batch the rest, and say no at the source when capacity is full.

Why it works: Managerial activities differ by orders of magnitude in output per hour — ninety minutes preparing a review shapes a year of someone's work, while a day of meddling subtracts output. A manager who lets the calendar happen to them spends prime hours on whatever shouted loudest.

Ethical boundary: Leverage means multiplying others' output, never hoarding information or approvals until you become the bottleneck everyone must visit.

See: references/leverage-and-calendar.md when auditing a calendar or setting up delegation — the weekly leverage audit, positive/negative-leverage catalog, delegation protocol with TRM-based monitoring depth, calendar-redesign procedure, and interruption management.

Core concept: A meeting is not a symptom of bad management; it is where managerial work — gathering information, imparting it, deciding, nudging — actually happens. Process-oriented meetings (one-on-ones, staff meetings, operation reviews) run on a regular cadence and should carry the bulk of that work, roughly a quarter of the calendar. Mission-oriented meetings are ad hoc and exist solely to produce a decision.

Why it works: Regularity makes meetings cheap — standing agendas, shared expectations, zero setup cost — and starves the expensive kind: issues get caught small in 1:1s and staff meetings instead of exploding into emergency decision meetings. Grove's malorganization test: ad hoc mission-oriented meetings eating more than about a quarter of managerial time means the process is broken.

Ethical boundary: Hijacking the 1:1 for status extraction teaches people to stop bringing real problems — status belongs in writing.

See: references/meetings-and-one-on-ones.md when designing a meeting cadence or running a 1:1 — the full 1:1 playbook with agenda templates, staff-meeting design, operation-review roles, and meeting-cost math for when to kill a meeting.

Core concept: The ideal decision moves through free discussion (all views aired, dissent welcome), a clear decision (stated crisply — the more contentious, the crisper), and full support (disagree and commit). Decisions belong at the lowest competent level, closest to current technical knowledge. Planning runs the same arc: assess environmental demand, face present status honestly, close the gap — because the output of planning is decisions and actions taken now, not documents.

Why it works: Free discussion surfaces knowledge that lives at the edges; a clear decision prevents the costliest outcome, ambiguity; full support lets the organization move without unanimity. And today's firefight is yesterday's planning failure — planning works on next year's gap, not this week's smoke.

See: references/decisions-planning-okrs.md when prepping a contentious decision or a planning cycle — the six-question brief, peer-group-syndrome counters, three-step planning, and a Grove-style OKR cascade with pitfalls.

Core concept: There is no universally good management style. The right style depends on the subordinate's task-relevant maturity (TRM) — their experience, training, and confidence for this specific task: low TRM calls for structured "how" instruction, medium for mutual reasoning about "what and why", high for agreed objectives with light monitoring. TRM is task-specific, not seniority, so style must shift the moment the task does.

Why it works: Mismatched style fails in both directions — hands-off at low TRM is abandonment dressed as empowerment; detailed instruction at high TRM is meddling that destroys ownership. The performance review is where the cost of a mismatch compounds: a year's feedback delivered in the wrong register lands as either neglect or insult.

See: references/case-studies.md when preparing a review or coaching a newly promoted manager — three worked scenarios (meeting-drowned new manager, velocity-up/quality-down, a botched review repaired with TRM coaching).

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