high-output-management
Manage for output using Grove''s "High Output Management": a manager''s output is their organization''s output, raised by high-leverage activities. Use when the user mentions "high output management", "managerial leverage", "one-on-ones", "1:1 agenda", "OKRs", "performance review", "task-relevant maturity", "delegation", "meeting overload", "new manager", "how do I run a 1:1", or "just got promoted to manager". Also trigger when structuring a manager''s calendar and meeting cadence, designing team metrics, running planning, coaching delegation, or preparing performance reviews. Covers leverage
npx skills add wondelai/skills --skill high-output-management --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Instructs the agent to apply Grove's High Output Management framework to manage teams by focusing on the organization’s output, using high-leverage activities, and structuring calendars, meetings, reviews, and planning to maximize impact. It emphasizes production principles for knowledge work, indicators of output, managerial leverage, and meetings as the medium of management.
How it works
The skill outlines concrete concepts and practices:
- Managerial output equals the organization’s output plus influenced neighbors; prioritize high-leverage actions and minimize negative leverage.
- Use a scoring system (0-10) to assess management practices, calendars, and processes against defined levels (9-10, 7-8, etc.), describing what distinguishes each tier.
- Production principles: identify limiting steps, fix at the lowest-value stage, batch high-cost activities, and forecast versus order work.
- Indicators that don’t lie: measure output (shipped features, problems solved) with paired quality indicators; use leading indicators and stagger charts.
- Managerial leverage: treat calendar as production system; forecast events, batch tasks, and say no when capacity is full; monitor at the task level and tailor depth by TRM; batch interruptions via office hours.
- Meetings are the medium of management: designate regular process-oriented meetings (1:1s, staff meetings, operation reviews) and ad hoc mission meetings for decisions; set 1:1 frequency by task-relevant maturity; supervisor records notes and actions; avoid hijacking 1:1s for status only.
- Decisions and planning (incl. OKRs): facilitate free discussion, clear decisions, and broad support; assign decisions to the lowest competent level; use six-question briefs for decision prep; cascade OKRs.
- TRM-based approach: adjust management style to subordinate task-relevant maturity; structure performance reviews as key feedback for improvement; avoid mismatched styles.
When to use it
Triggers include mentions of high output management, managerial leverage, one-on-ones, 1:1 agenda, OKRs, performance reviews, task-relevant maturity, delegation, meeting overload, new manager, or how to run a 1:1. Also applies when structuring a manager’s calendar, planning, coaching delegation, or preparing performance reviews.
What it can touch
Tools and concepts explicitly touched by the skill include calendar design, 1:1s, reviews, OKRs, planning processes, delegation protocols, and TO-DO/indicators modeling; it references specific practices like forecasting key events, batching, and TRM-based monitoring depth.
Caveats
License: MIT. The content emphasizes measurements and governance practices; careful handling is required to avoid treating people as mere indicators or over-optimizing for metrics at the expense of performance and development.
# High Output Management 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. ## Core Principle **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. ## Scoring **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. - **9-10:** Output indicators with quality pairs, subord
- Core Principle
- Scoring
- Framework
- 1. Production Principles for Knowledge Work
- 2. Indicators That Don't Lie
- 3. Managerial Leverage
- 4. Meetings Are the Medium of Management
- 5. Decisions and Planning (incl. OKRs)
- 6. Task-Relevant Maturity, Reviews, and Training
- Common Mistakes
- Quick Diagnostic
- Further Reading
- About the Author
What does the high-output-management skill do?
Manage for output using Grove''s "High Output Management": a manager''s output is their organization''s output, raised by high-leverage activities. Use when the user mentions "high output management", "managerial leverage", "one-on-ones", "1:1 agenda", "OKRs", "performance review", "task-relevant maturity", "delegation", "meeting overload", "new manager", "how do I run a 1:1", or "just got promoted to manager". Also trigger when structuring a manager''s calendar and meeting cadence, designing team metrics, running planning, coaching delegation, or preparing performance reviews. Covers leverage
How do I install it?
Run `npx skills add wondelai/skills --skill high-output-management --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From wondelai/skills, a repository with 1,835 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
