/high-output-management

name: high-output-management
description: "Think like Intel's legendary CEO. Apply Andy Grove's management operating system to maximize your team's output through leverage, OKRs, and systematic decision-making. Use when: **Scaling a team** when individual contribution isn't enough; **Performance management** to measure and improve output; **Meeting optimization** to make meetings productive; **Decision-making** in management contexts; **New manager transition** from individual contributor"
license: MIT
metadata:
  author: ClawFu
  version: 1.0.0
  mcp-server: "@clawfu/mcp-skills"

High Output Management

> Think like Intel's legendary CEO. Apply Andy Grove's management operating system to maximize your team's output through leverage, OKRs, and systematic decision-making.

When to Use This Skill

• **Scaling a team** when individual contribution isn't enough
• **Performance management** to measure and improve output
• **Meeting optimization** to make meetings productive
• **Decision-making** in management contexts
• **New manager transition** from individual contributor
• **Organizational design** for efficiency

Methodology Foundation

| Aspect | Details | |--------|---------| | **Source** | Andy Grove - High Output Management (1983) | | **Core Principle** | "A manager's output = Output of their organization + Output of neighboring organizations under their influence." | | **Why This Matters** | Management is a skill, not just a title. Grove's engineering approach to management created modern tech management practices, including OKRs (used by Google, Intel, LinkedIn, etc.). |

What Claude Does vs What You Decide

| Claude Does | You Decide | |-------------|------------| | Structures analysis frameworks | Strategic priorities | | Synthesizes market data | Competitive positioning | | Identifies opportunities | Resource allocation | | Creates strategic options | Final strategy selection | | Suggests implementation approaches | Execution decisions |

What This Skill Does

1. **Defines management as output** - Measurable, not abstract 2. **Teaches leverage** - Maximize output per unit of management time 3. **Structures 1:1s and meetings** - For information gathering and decision-making 4. **Introduces OKRs** - Objectives and Key Results framework 5. **Builds management rhythm** - Systematic operating cadence 6. **Improves performance management** - Task-relevant maturity

How to Use

Design Your Management System

I'm managing a team of [X] people doing [type of work].
Help me design a Grove-style management operating system.

Improve Your Leverage

I'm spending my time on [activities].
Apply High Output Management thinking to improve my leverage.

Set Up OKRs

Help me create OKRs for [team/individual/company].
Context: [current goals, challenges]

Instructions

Step 1: Understand Management as Production

## The Production Principle

### Grove's Key Insight

Management isn't about status or authority.
Management is about OUTPUT.

**A manager's output =**
Output of their team +
Output of other teams they influence

### The Factory Analogy

Think of your team as a production line:
- Raw materials → Work in progress → Finished goods
- Input → Process → Output

**Your job:**
1. Identify limiting steps
2. Remove bottlenecks
3. Increase throughput
4. Maintain quality

### Manager Activities

Everything you do falls into three categories:

**1. Information gathering**
- 1:1s
- Staff meetings
- Reports
- Walking around

**2. Information giving**
- Direction setting
- Teaching
- Decisions communicated
- Feedback

**3. Decision-making**
- Prioritization
- Resource allocation
- Hiring/firing
- Process design

### The Leverage Equation

**Leverage = Output / Activity**

High leverage activities:
- Training (multiplies across many people)
- Decisions (unlock blocked work)
- Systems (automate repeated work)

Low leverage activities:
- Doing work others could do
- Meetings without decisions
- Reviewing what's already done well

---

Step 2: Master Management Leverage

## Types of Leverage

### High Leverage Activities

**1. Training**
An hour spent training 10 people = 10 hours of improved output.
Training has the highest ROI of any management activity.

**Questions:**
- Who on my team could I train?
- What knowledge do I have that would help them?
- How can I systematize training?

**2. Decisions that unblock work**
When your decision is the bottleneck, make it.
Delayed decisions multiply delays.

**Questions:**
- What decisions are people waiting on?
- Which decisions must be mine vs. delegated?
- How fast am I making decisions?

**3. Motivation and recognition**
Peak performance requires motivation, not just direction.
Recognition costs you nothing but drives output.

**Questions:**
- Who deserves recognition this week?
- What motivates each person on my team?
- Am I providing meaning, not just tasks?

### Low Leverage Traps

**1. Doing work yourself**
If someone else can do it 70% as well, delegate.
Your job is enabling output, not doing output.

**2. Attending meetings you don't need**
Every meeting is time not doing high-leverage work.
Audit: "Would this meeting happen without me?"

**3. Over-reviewing work**
Review is valuable. Over-review is micromanagement.
Match review depth to risk and skill level.

### The Meddling Trap

**Signs you're meddling:**
- Making decisions your team should make
- Reviewing work that doesn't need review
- Being in every meeting
- People wait for your approval on everything

**The fix:**
Delegate. Then don't take it back.

---

Step 3: Run Effective Meetings

## Grove on Meetings

### Two Types of Meetings

**Process-oriented meetings (Regular)**
- 1:1s
- Staff meetings
- Operations reviews

Purpose: Information flow, coordination, rhythm

**Mission-oriented meetings (Ad hoc)**
- Decisions needed
- Problems to solve
- Opportunities to evaluate

Purpose: Make a decision, then di