operational-excellence

name	operational-excellence
type	domain
family	executive
rigor	standard
description	Use when designing execution systems, OKR frameworks, or operational processes.
keywords	execution, systems, OKRs, management, processes, operations, efficiency
compatibility	Claude Code and compatible agent products
requires	[]
enhances	["strategy-clarity","team-builder","prd-writing"]
sources_pdf	["High Output Management (Grove)","Measure What Matters (Doerr)","Working Backwards (Bryar)","An Elegant Puzzle (Larson)","The Mythical Man-Month (Brooks)"]
sources_web	["Stratechery: The Amazon Tax","Google re:Work: Team Effectiveness","Farnam Street: Second-Order Thinking"]

Overview

Operational excellence is the discipline of creating high-leverage execution systems that translate strategic choices into measurable output. This skill focuses on building "Mechanisms" (not just good intentions), managing by controllable inputs, and optimizing team topology for maximum flow.

Guiding Principles

Principle 1: Manage by Leverage (Source: Grove, High Output Management)

A manager's output is the output of the units under their influence. High-leverage activities—those that affect many people for a long time—must be prioritized over low-leverage tactical "busyness."

Principle 2: Mechanisms, Not Good Intentions (Source: Bryar, Working Backwards)

If a process fails, do not ask for more "effort" or "better focus." Build a Mechanism—a recurring, automated process that includes a tool, a training, and an audit to ensure the problem is solved structurally.

Principle 3: Focus on Controllable Inputs (Source: Bryar, Working Backwards)

You cannot control outputs like revenue or stock price. You can only control inputs like selection, price, and convenience. Operational excellence requires identifying and obsessively measuring the inputs that drive the desired outputs.

Principle 4: Task-Relevant Maturity (TRM) (Source: Grove, High Output Management)

Management style is not fixed; it must adapt to the subordinate's experience level in a specific task. High TRM requires a hands-off, objective-oriented approach; low TRM requires detailed, process-oriented monitoring.

Principle 5: The Amazon Tax (Source: Stratechery, "The Amazon Tax")

Design internal operations as modular service layers (APIs). If an internal service is efficient enough to be externalized, it becomes a profit center rather than a cost center. This forces internal units to compete at market standards.

When to Use This Skill

• When a team is "Falling Behind" or "Treading Water" and needs system redesign.
• When setting quarterly OKRs or annual planning.
• When a recurring failure occurs despite "good intentions."
• When scaling an organization from a single team to a "Team of Teams."

When NOT to Use This Skill

• For highly creative, non-linear tasks where process would stifle innovation.
• For one-off, low-stakes activities where the "Mechanism" overhead exceeds the benefit.

Core Process

Step 1: Identify the Limiting Step

Model the operational flow and identify the "bottleneck" or "limiting step"—the part of the process that is most difficult, expensive, or slow. (Source: Grove, Ch. 2)

1. Model the Breakfast Factory: Map the steps from input to final output.