The Source Codethecofounderstandard.com.au

The Velocity Protocol

One-Way Doors vs Two-Way Doors

StrategyProtocol

The problem this addresses

My co-founder and I can't agree / decisions are slow

The Problem

Your team spent three weeks debating which project management tool to use. Meanwhile, you signed a 10-year office lease in an afternoon because you were tired of the uncertainty and "just wanted it done."

This is the Velocity Mismatch. Almost every organization has it. Weeks of cognitive cycles burned on decisions that could be reversed by next Tuesday. And the ones that actually reshape the company — the ones you can't undo — get rushed through on gut feel because the discomfort of sitting in ambiguity became unbearable.

The result: structural debt from the big calls. Organizational paralysis on the small ones. Both problems share the same root cause. You're treating every decision as if it carries the same weight.

Who This Is For

Founders and co-founder teams where decisions either stall indefinitely or get made too fast for the wrong reasons. If your leadership meetings regularly end with "let's think about it more" on things that don't matter, and "let's just go with it" on things that do — this is the fix.

What You'll Need

  • Time commitment: 20 minutes to learn the classification. Then it's a lens you apply in real time — no separate session required.
  • Prerequisites: At least two people making decisions together. This protocol works solo, but the real value is shared language. When your co-founder says "that's a Two-Way Door," the argument ends.
  • Tools: Nothing. This is a decision filter, not a worksheet. You'll carry it in your head after one use.

The Protocol

The Velocity Mismatch

Here's what's actually happening in your company right now. Two failure modes, running simultaneously.

On one side: reversible decisions getting the full boardroom treatment. Committee input. Stakeholder alignment. A Slack thread with forty-seven messages about font choices. The cost of all that deliberation far exceeds the cost of just picking wrong and adjusting.

On the other side: irreversible decisions getting made in the gap between meetings. Someone was frustrated, or exhausted, or just wanted the relief of having it settled. So a cap table gets restructured over a weekend call. A co-founder gets pushed out during a bad week. A market pivot happens because one customer complained loudly.

Both of these are speed problems. But they require opposite solutions.

Type 1 — One-Way Doors (Structural)

These are consequential and irreversible. The door locks behind you. If you're wrong, reversal isn't a course correction — it's a demolition job.

Examples:

  • Selling the company
  • Cap table structure
  • Firing a co-founder
  • Radical product pivot with no path back
  • Signing a 10-year lease
  • Taking on a strategic investor

The Protocol: DECELERATE.

Precision over speed. Write the thesis down. Gather 70-90% of the data you'd want before committing. Leave open loops — they're fine. The discomfort of not deciding yet is cheaper than the cost of deciding wrong.

One-Way Doors earn every minute you spend on them. If someone pressures you to move faster on a Type 1, that pressure is the signal to slow down, not speed up.

Type 2 — Two-Way Doors (Variable)

These are changeable. Reversible. You can walk back out. The cost of failure is close to zero — it's tuition, not damage.

Examples:

  • A new marketing headline
  • Meeting cadence
  • Trying a new SaaS tool
  • Hiring a contractor for a trial project
  • Changing your onboarding flow
  • Testing a pricing page variant

The Protocol: ACCELERATE.

Velocity over precision. You need 30% of the data. Maybe less. Decide. Ship it. Wrong? Fix it next week. The information you get from doing will always beat the information you get from discussing.

Here is the line worth remembering: Debating a Two-Way Door is Organizational Entropy. Every hour spent arguing about something reversible is an hour stolen from something that isn't.

The Classification Heuristic

One question sorts every decision you'll face:

"If I am wrong, what does it cost to fix?"

High cost to fix = Type 1. Treat it with gravity. Slow down. Write the thesis. Pressure-test the assumptions.

Low cost to fix = Type 2. Decide by end of day. Literally today. Not "this week." Today.

If you can't tell which type it is, ask a sharper version: "Could we reverse this in 30 days without permanent damage?" If yes, it's Type 2. Move.

The Golden Rule of Delegation

Your job as founder is Type 1 decisions. That's it.

Delegate almost all Type 2 decisions. If you're sitting in a meeting debating a Two-Way Door, you are not "being careful." You are micromanaging. You are spending your scarcest resource — founder-level attention — on something your team could resolve in fifteen minutes without you.

The math: if 80% of your decisions are Type 2 (and they are), and you're personally involved in all of them, you've given yourself a 5x workload for zero additional value. Worse — you've trained your team to wait for you. Now everything is slow, and it's your fault.

Shadow Culture Warning

Speed problems aren't always structural. Sometimes they're emotional. Two traps to watch for:

The Type 2 Trap — Fear of Being Wrong

This is the team that over-analyzes small decisions. Three rounds of feedback on a blog post. A week-long deliberation about which CRM to trial. The root isn't thoroughness. It's a culture where being wrong feels unsafe.

The fix is philosophical: a failed experiment is not a failure. It's new data. The only real failure is slow execution. If your team is afraid to make reversible mistakes, you have a psychological safety problem, not a decision-making problem.

The Type 1 Trap — Fear of Commitment

This is the founder who rushes big decisions for the relief of "just deciding." The discomfort of sitting in uncertainty becomes so painful that any answer feels better than no answer. So they sign the deal, make the hire, burn the bridge — not because the signal was clear, but because the ambiguity was intolerable.

The fix is harder: learn to tolerate discomfort. Sit in uncertainty until the signal arrives. Type 1 decisions don't reward speed. They reward patience. The relief you feel when you "just decide" is not clarity — it's surrender.

What You'll Find

The first thing that changes is meeting length. Once your team has shared language for "that's a Two-Way Door," the forty-five-minute debates about vendor selection or Slack channel structure evaporate. Someone names it, the room agrees, someone owns it, done. You'll get hours back per week.

The second shift is subtler and takes longer. You'll start noticing how many Type 1 decisions you've been making at Type 2 speed. Commitments you locked in because someone pushed, or because Tuesday's energy was different from Monday's. The Velocity Protocol doesn't make those decisions for you — but it forces a pause at the moment you're most tempted to skip one.

The delegation effect compounds. Once your team learns they have permission to make Type 2 calls without you, two things happen: they get faster, and they get better at judgment. They start classifying on their own. Within a month, the only decisions that reach you are the ones that should.

Adaptations

Co-founder deadlock: When you and your co-founder can't agree, start by classifying the decision together. Half the time, the deadlock breaks immediately — you discover you've been arguing about a Type 2 as if it were a Type 1. For actual Type 1 disagreements, the classification at least reframes the conversation: "We both agree this door locks behind us. So what data would change your mind?" That's a more productive fight than "I think we should" versus "I think we shouldn't."

Solo founder: Without a co-founder to check you, the Type 1 Trap gets worse. Build a forcing function: before any commitment you can't reverse in 30 days, write a one-page thesis and send it to your advisor, investor, or smartest friend. The act of writing it often reveals whether you're deciding from signal or from fatigue.

Scaling teams (20+ people): The protocol breaks down if only founders use it. Teach the classification to your leadership team. Give them explicit authority: "If it's Type 2, you don't need my approval. You need to tell me what you decided." Put that sentence in your operating docs. The cultural shift — from "ask permission" to "inform after acting" — is where the real speed comes from.

High-frequency decision environments (product sprints, fundraising): When you're making fifty calls a day, you won't have time to consciously classify each one. Instead, batch: at the start of the sprint or raise, identify the two or three Type 1 decisions in the mix. Protect those. Everything else moves at full speed with no committee.

Where This Came From

Jeff Bezos introduced the One-Way Door / Two-Way Door framework in his 2015 Amazon shareholder letter. His argument: as companies grow, they tend to apply Type 1 decision-making processes to Type 2 decisions — heavyweight, slow, risk-averse — and it kills them. "The end result of this is slowness, unthoughtful risk aversion, failure to experiment sufficiently, and consequently diminished invention."

The delegation principle — that founders should reserve their attention for irreversible decisions and push everything else down — aligns with Andy Grove's argument in High Output Management that a manager's output is the output of their organization, not their personal activity. If you're personally touching Type 2 decisions, you're optimizing your activity, not your output.

The Shadow Culture traps came from pattern recognition across dozens of founder coaching engagements where the presenting problem was "we're too slow" but the actual problem was either a fear culture (Type 2 Trap) or a founder who couldn't sit with ambiguity (Type 1 Trap).

  • The Decision Architecture — When you've identified a Type 1 decision and need a structured process to work through it. The Velocity Protocol tells you to slow down; the Decision Architecture tells you what to do with the time.
  • The Ferguson Protocol — The operational structure for delegation. Once you've committed to handing off Type 2 decisions, the Ferguson Protocol shows you how to install a Chief of Staff who can carry them.
  • Top Goal Theory — If the Velocity Protocol frees up your time by removing Type 2 decisions from your plate, Top Goal Theory tells you exactly where to point that reclaimed attention.

These protocols work on their own.
They work differently with someone in the room.

Learn about coaching →