The Optionality Engine

The Problem

You're running your business off a to-do list. A linear plan that assumes one path from here to done. The moment something breaks — a key hire falls through, a client delays, a supplier ghosts — the whole plan stalls because it had no alternatives built in. You don't lack discipline. You lack options.

Who This Is For

Founders or operators who keep getting blindsided by Plan A failing and have no Plan B ready — because they never built one.

What You'll Need

• Time commitment: 20 minutes per outcome to run the full RPM cycle. 5 minutes for the brain dump. 10 minutes to filter.
• Prerequisites: A specific outcome you need to hit this week or this quarter. This protocol doesn't work on vague ambitions — it needs a target.
• Tools: Timer for the brain dump. Paper or a doc for the MAP. The Hedgehog filter from The Essential Momentum Protocol if you want to validate the outcome first.

The Protocol

The Core Philosophy

The Trap: The Fragility of "To-Do" Lists

Most leaders operate from a "To-Do" list. This is a fragile system. A list is a series of isolated tasks without a unified center. When chaos hits (and it always does), a linear plan breaks because it relies on one specific path to get to the finish line. If that path is blocked, you stall.

The Shift: Radical Optionality

We adopt the RPM (Rapid Planning Method), created by Tony Robbins.

• R = Result (What do we want?)
• P = Purpose (Why do we want it?)
• M = Massive Action Plan (How do we get there?)

The superpower of this protocol is Optionality. By generating a massive list of potential "Hows" (The MAP), we realize there are 50 ways to achieve the Result. If Plan A fails, we have Plans B through Z ready. This makes the goal Anti-Fragile — we can pivot instantly without losing the outcome.

"Failure is rarely a lack of resources; it is a lack of resourcefulness." — Tony Robbins.

The 3 Phases of Architecture

We use this protocol for OKRs, Weekly Sprints, and Crisis Navigation.

Phase 1: The Target (The Result)

We never start with "What do I need to do?" We start with "What is the Outcome?"

Most people write: "Call Client X." (This is an activity.) The Protocol requires: "Secure Signed Contract from Client X by Friday." (This is a Result.)

The Check:

• Is it specific?
• Is it binary? (Did it happen, yes or no?)
• Does it drive the business forward?

Phase 2: The Fuel (The Purpose)

Reasons come first; answers come second.

You cannot sustain "Deep Work" or high output without emotional leverage. You must define the stakes.

• The Prompt: Why must this happen now?
• The Leverage: Connect it to the bigger picture. "If we miss this, we lose momentum on Q4."

Phase 3: The Engine (The Massive Action Plan)

This is where we build Optionality.

Step A: The Brain Dump (Quantity over Quality)

Set a timer for 5 minutes. List every single possible way to achieve the Result defined in Phase 1.

• Do not edit.
• Do not judge feasibility.
• Write down the crazy ideas, the expensive ideas, and the simple ideas.
• Goal: We want 20+ options. This proves to your brain that the path is not rigid; it is flexible.

Step B: The Pareto Filter (The 80/20 Rule)

Look at your list of 20+ items. You cannot do them all.

• Identify the 20% of actions that will yield 80% of the result.
• Circle the 3 "needle movers."
• Delete or delegate the rest.

Execution: The RPM Worksheet

Use this structure when setting your Weekly Outcomes or Quarterly OKRs.

R: RESULT — What specifically do I want to achieve? Be precise. Vague goals produce vague results.

• Bad: "Work on hiring."
• Good: "Finalize 3 candidates for the CTO role."

P: PURPOSE — Why does this matter? What is the cost of failure? Connect to the "Anti-Fragile" mindset.

• "This ensures we aren't reliant on a single developer (Fragility)."

M: MAP (Options) — What are ALL the ways I could achieve this?

1. Brain Dump: List 10-20 actions. (Call headhunter, post on LinkedIn, ask investors for referrals, poach from competitor, etc.)
2. Select: Pick the top 3.

The Summary

When you have only one way to win, you are fragile. When you have twenty ways to win, you are dangerous.

The RPM Protocol is not about checking boxes. It is about training your brain to see infinite resources where others see dead ends. This is how we move from "surviving the storm" to "learning from chaos."

What You'll Find

The brain dump is where the magic happens. Most founders stall at 5-7 options because they're already filtering for feasibility. Push past it. Around option 12 or 13, something shifts — you start generating ideas you'd never have considered if you were just "making a plan." The other thing you'll notice: once you have 20 options on paper, the anxiety drops. The goal stops feeling fragile because you can see, in black and white, that there are dozens of paths to the same destination.

Adaptations

Crisis mode (48-hour deadline): Skip Phase 2. You already know the Purpose — survival. Go straight from Result to Brain Dump. Give yourself 3 minutes instead of 5. Pick the top action and execute immediately. You can refine the MAP after the fire is out.

Team planning (OKRs or quarterly sprints): Run the brain dump as a group exercise. Give each person 3 minutes of silent writing, then compile. You'll get 50+ options from a team of five. The Pareto filter becomes a group vote — each person circles their top 3, and the overlaps become the plan.

Where This Came From

Tony Robbins' Rapid Planning Method is the foundation. Robbins built RPM as a counter to traditional productivity systems that optimize for task completion rather than outcome achievement. The Optionality layer — the emphasis on generating 20+ paths before choosing one — came from applying Nassim Taleb's anti-fragility thinking to the planning process. If a plan depends on a single path, it's fragile. If a plan has twenty paths to the same outcome, disruption becomes an inconvenience instead of a catastrophe.

Related Protocols

• The Essential Momentum Protocol — Use the Hedgehog Concept to validate that your Result is worth pursuing before you build the MAP. Optionality without focus is just organized chaos.
• The Ferguson Protocol — When your MAP identifies actions that should be delegated, not done by you. The Chief of Staff becomes the person who executes Plans B through Z while you stay on Plan A.
• The Decision Authority Matrix — Clarifies who owns which actions in the MAP so your team can execute options in parallel without waiting for your approval on each one.