high-output-management

Applies Grove's High Output Management framework to managerial leverage, meetings, OKRs, and delegation.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/HafidJoss/Lummy --skill high-output-management-hafidjoss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: high-output-management
Source: https://github.com/HafidJoss/Lummy/tree/main/agent/skills/high-output-management
Command: npx skills add https://github.com/HafidJoss/Lummy --skill high-output-management-hafidjoss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managers often measure busyness instead of output, run ad hoc meetings instead of process meetings, and apply one management style to everyone. This Skill turns Andy Grove's High Output Management into auditable practice: output indicators with quality pairs, leverage audits, 1:1 playbooks, decision briefs, OKR cascades, and task-relevant maturity coaching. ## Core Features & Use Cases - Output Indicators and Production Thinking: Find the team's limiting step, pair every quantity metric with a quality counterpart, and use stagger charts to expose forecast bias. - Managerial Leverage and Calendar Design: Audit a week for high- and negative-leverage activities, delegate with TRM-based monitoring depth, and redesign the calendar around forecasted key events. - Meetings, Decisions, and OKRs: Run subordinate-owned 1:1s, staff meetings, and operation reviews; frame decisions with the six-question brief; write Grove-style cascading OKRs decoupled from compensation. - Use Case: A newly promoted engineering manager drowning in 34 hours of meetings uses the leverage audit, installs weekly 1:1s and a staff meeting, and cuts ad hoc meetings while raising team throughput. ## Quick Start Ask the assistant to audit your management calendar and 1:1 cadence using the High Output Management framework and score it against the 10-point scale.

Frequently Asked Questions about high-output-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a one-on-one meeting as a new manager?

Make the 1:1 the subordinate's meeting: they own and send the agenda the day before, covering indicators, problems, plans, and hold-list items. Set frequency by task-relevant maturity (weekly for new-to-task, monthly for veterans), take notes yourself, and end by asking what else is on their mind.

How do I write OKRs that are not sandbagged?

Write two or three objectives with dated, verifiable key results that can be scored yes or no without argument. Cascade so one level's key results become the next level's objectives, let each team write its own, and never wire OKR scores mechanically to compensation, which guarantees safe objectives.

What is task-relevant maturity and how does it change management style?

Task-relevant maturity is a person's experience and confidence for a specific task, not their seniority. Low TRM calls for structured how-to instruction, medium for mutual reasoning, and high for agreed objectives with light monitoring, and the style must shift whenever the task changes.

How do I measure team output instead of activity?

Count what shipped and survived, not hours or tickets touched. Pair every quantity indicator with a quality counterpart, such as deploys per week with change-failure rate, and add leading indicators like review queue age so you can act before output drops.

When should a manager delegate a task and how much should they monitor?

Delegate the tasks you know best, since monitoring them costs you least, and hand off outcomes with constraints in writing. Agree on the monitoring plan in the handoff conversation and set depth by task-relevant maturity: frequent structured checks at low TRM, milestone-only review at high TRM.

Why do ad hoc meetings keep multiplying on my calendar?

Ad hoc mission-oriented meetings multiply when regular process meetings are missing, so problems surface late as emergencies. Install weekly 1:1s and a staff meeting, convert any recurring ad hoc meeting into a standing format, and apply the cost test to kill meetings that produce no decisions.