opondo300/born-builders-agent-library/operator-frameworks

Operator Frameworks — Musk, Grove, Bezos

Sources: Elon Musk (First Principles + Algorithm), Andy Grove (High Output Management), Jeff Bezos (Shareholder Letters + Working Backwards)

Elon Musk — The 5-Step Algorithm

Apply in strict order. Never skip to a later step before completing the prior one.

1. Question every requirement — Every requirement must have a name attached. "The regulations require it" and "legal said so" are not sufficient. Find the human who made the requirement. Challenge it. A smart engineer is often better than a legal team at identifying what's actually necessary vs. what is bureaucratic inertia.
2. Delete everything possible — Remove parts, steps, processes. If you don't add back at least 10% of deleted things later, you are not deleting enough. Things that were deleted can be added back. Things that were never deleted become permanent fixtures.
3. Simplify and optimise — Only AFTER deletion. Optimising something that should have been deleted is the most common expensive mistake in business and engineering.
4. Accelerate cycle time — Speed up the process, but only after Steps 1–3 are complete. Speeding up a broken process just produces broken output faster.
5. Automate — Only after Steps 1–4. Automating before simplifying locks in complexity permanently.

Diagnostic rule: If your team is at Step 4 or 5, go back and run Steps 1–2 again. Most plans skip deletion entirely.

First Principles Thinking:

• Do not reason by analogy. Analogies describe what has been done, not what is possible.
• Ask: "What do we know to be absolutely true about this problem?" Start from the physics. Work forward.
• Example: Battery cost. Analogy thinking: "Batteries have always been expensive — it's the market price." First principles: "What are batteries made of? What do those materials cost on commodity markets? If assembled optimally, what could a kWh of storage actually cost?" — led to Tesla's entire vertical integration strategy.

The Factory Is the Machine: Think of the production process as a machine to be designed, not a problem to be managed. Ask: "If I were designing this machine from scratch, would I include this step?" This shifts the question from "how do we improve this?" to "do we need this at all?"

Andy Grove — High Output Management

Manager Output Formula

Manager's Output = Output of their organisation + Output of neighbouring organisations they influence

This has two implications:

1. A manager's personal productivity is almost irrelevant. Only leverage matters.
2. Training one person who manages ten people has 10× the output impact of training one individual contributor.

Highest-leverage activities (in order):

1. Training — teaches a process that will run repeatedly without you
2. One-on-ones — removes blockers and builds judgment that propagates through the team
3. Decisions in meetings — unblocks multiple downstream tasks simultaneously
4. Writing — thoughts once written can propagate indefinitely at zero cost

Task-Relevant Maturity (TRM)

The single most important variable for how you manage someone is their maturity on the specific task, not their general capability.

Critical insight: A senior person doing a new job has low TRM on that specific job. Treat them accordingly — not according to their title.

Management failure modes:

• Managing a high-TRM person as if they are low-TRM = micromanagement, destroys motivation
• Managing a low-TRM person as if they are high-TRM = abdication, produces errors and frustration

Leverage Framework

Every managerial activity has different leverage. Before any action, ask: "Which activity produces the most output across the whole system right now?"

High-leverage activities:

• Information gathering before a decision (prevents costly path changes later)
• Nudging team decisions toward better outcomes before they're locked in
• Interviewing and hiring (a bad hire propagates errors for months)
• Building process once to replace recurring manual decision-making

Nudge vs. Order:

Default to nudging. Orders should be the exception. A team that always waits for orders is a team with no independent judgment.

1:1 Structure

The 1:1 belongs to the subordinate. Its purpose is information flow from them to you, not task assignment from you to them.

Agenda owned by the team member. Manager's job: listen, ask, remove blockers.

Key questions:

• "What are you most worried about?"
• "What's slowing you down?"
• "What do you need from me to make progress?"

Frequency rule: Match frequency to TRM. High-TRM: every 2 weeks is fine. Low-TRM or in a critical period: weekly minimum.

Grove's OKR Framework (Origin)

• O (Objective): What direction are we going? Qualitative. Inspirational but grounded.
• KR (Key Results): How do we measure progress? Quantitative. Should be aggressive enough that hitting 70% is a strong result. 100% on every KR means the goal wasn't ambitious enough.

Anti-patterns to watch:

• Too many OKRs — focus is impossible, prioritisation is abdicated
• Key Results that describe activities, not outcomes ("we will run 3 workshops" vs. "25% of team trained on new process")
• OKRs set once and never referenced — they become bureaucracy, not alignment tools

Jeff Bezos — 16 Leadership Principles

Every decision at Amazon is weighed against these. They are operational, not inspirational.

1. Customer Obsession — Start with the customer, work backwards. Leaders earn trust by obsessing over customer problems, not internal metrics.
2. Ownership — Think and act like an owner. Never say "that's not my job." If you see a problem, own the outcome, not just the task.
3. Invent and Simplify — Expect and require innovation. Accept that being misunderstood is part of doing new things. Never accept complexity when simplicity is achievable.
4. Are Right, A Lot — Seek diverse perspectives. Be willing to change your mind. Strong intuition plus analytical rigour. Being right is more important than being consistent.
5. Learn and Be Curious — Never stop learning. Explore new possibilities with genuine curiosity. Self-improvement is a responsibility, not a luxury.
6. Hire and Develop the Best — Every hire should raise the bar. If you wouldn't enthusiastically hire someone for yourself, don't hire them. Identify and develop talent relentlessly.
7. Insist on the Highest Standards — Standards that others call unreasonably high are simply what's required. Defects don't pass to the next stage. Quality compounds.
8. Think Big — Small thinking is a self-fulfilling prophecy. A bold direction inspires results that incremental thinking cannot reach.
9. Bias for Action — Speed matters. Many decisions are reversible. Don't wait for certainty on Type 2 decisions. Move now, adjust later.
10. Frugality — Constraints force resourcefulness. Headcount and budget are not achievements — output is.
11. Earn Trust — Listen attentively. Speak candidly. Self-critique openly. Benchmark against the best.
12. Dive Deep — Leaders operate at all levels. No detail is beneath a leader when it matters. Data and instinct together.
13. Have Backbone; Disagree and Commit — Challenge respectfully but disagree explicitly when you believe something is wrong. Once the decision is made, commit fully — no passive resistance.
14. Deliver Results — Obstacles are inputs, not excuses. Focus on the key inputs that drive outcomes. Deliver with the right quality, on time.
15. Strive to Be Earth's Best Employer — Build an environment that is safe, productive, and where people do their best work.
16. Success and Scale Bring Broad Responsibility — With reach comes responsibility. Consider second-order effects on community and environment.

Application rule: When diagnosing a decision failure, identify which principle was violated first. Most failures trace to Ownership (#2), Bias for Action (#9), or Backbone (#13).

Bezos — Working Backwards (PR/FAQ)

Before building anything, write the press release that will announce it when it ships, plus the FAQ that customers and internal teams will ask.

Why this works: It forces you to define what success looks like before you start. You can't write a compelling press release for a mediocre product. If you can't make the press release clear and exciting, the product isn't well-defined enough to build.

Structure:

1. Customer headline — What is the compelling benefit in one sentence?
2. The problem — What exactly is the customer experiencing that this solves?
3. The solution — How does the product solve it?
4. Quote from a customer — What would a delighted customer actually say?
5. Call to action — What does the customer do next?

FAQ: Two sections:

• External FAQ: Questions customers will ask (including hard ones about limitations)
• Internal FAQ: Questions the team and business will ask (cost, dependencies, operational complexity)

Diagnostic use: If the FAQ section for customer objections is longer than the PR section, the product isn't ready. Fix the product, not the FAQ.

Bezos — Type 1 vs Type 2 Decisions

Most organisations apply the same heavyweight decision-making process to both types. This is the primary cause of slowness and missed opportunities.

The failure mode: Treating Type 2 decisions like Type 1. This is caused by risk aversion, committee culture, and the desire to avoid blame — not by genuine uncertainty.

Rule: When facing a decision, ask first: "Can we reverse this?" If yes, bias heavily toward speed. If no, slow down.

Bezos's 70% Rule: If you have 70% of the information you'd like, make the decision. Waiting for 90% is usually too late. The cost of delay exceeds the cost of a correctable mistake.