MMasters in Business
← All frameworks
Strategy

Failure-Catching Scale-Up

Anticipate breakdowns at each scale and redesign the endeavor before advancing.

Difficulty
Advanced
Time to result
~ongoing to results
Steps
6
Confidence
95%

Failure-Catching Scale-Up treats expansion as the deliberate preparation of an organization for the breakdowns that become possible at its next level. The team first defines the intended scale, then conducts a detailed premortem of everything that could undermine the endeavor there. Each predictable risk triggers an intervention: redesign the underlying system, establish a protocol, train a response, or reconsider whether scaling is desirable. Perez-Breva compares this process to astronauts preparing for the International Space Station by examining what could kill them and changing engines or procedures accordingly. Scale is achieved when predictable failures have been addressed and only genuinely unforeseeable events remain. The framework also permits the conclusion that a worthwhile problem naturally belongs at a small scale rather than requiring continuous growth.

Origin

Perez-Breva draws the model from astronaut preparation described by Chris Hadfield and others, applying it to organizational scaling. Extracted from Masters in Business.

Core principles

  • 01Organizations and capabilities scale; isolated ideas do not.
  • 02Each larger scale introduces new ways for the endeavor to break.
  • 03Predictable breakdowns should be caught before expansion.
  • 04Risks can be addressed through design changes, protocols, or preparation.
  • 05A problem may legitimately have a small natural scale.

How to run it

  1. 1

    Specify the Next Scale

    Define the next operational state in concrete terms, including volume, people, cost, geography, and consequences.

    Pro tip Use one attainable scale transition rather than planning abstractly for global dominance.

    Watch out A vague ambition to grow cannot support useful risk analysis.

  2. 2

    Run an Excruciating Premortem

    List the events, assumptions, and dependencies that could make the endeavor fail at that scale.

    Pro tip Include frontline staff and technical specialists who see failure modes leaders miss.

    Watch out Do not suppress uncomfortable scenarios to preserve enthusiasm.

  3. 3

    Redesign Structural Weaknesses

    Modify the product, process, engine, or organization wherever a predictable risk can be removed at its source.

    Pro tip Prefer eliminating a failure mode over relying entirely on human vigilance.

    Watch out A workaround that succeeds once may collapse under repeated use.

  4. 4

    Build Response Protocols

    For risks that cannot be eliminated, define and rehearse actions that contain the damage and preserve the mission.

    Pro tip Assign clear decision rights before the stressful event occurs.

    Watch out A protocol that has never been tested may create false confidence.

  5. 5

    Reassess the Natural Scale

    Determine whether the problem truly benefits from expansion or whether the evidence indicates a smaller sustainable scope.

    Pro tip Treat a small natural market as learning, not failure.

    Watch out Scaling for status can destroy an otherwise valuable endeavor.

  6. 6

    Advance and Repeat

    Move to the prepared scale, monitor new evidence, and repeat the process before the next expansion.

    Pro tip Capture unexpected breakdowns so the organization’s risk model improves.

    Watch out Preparation at one scale does not guarantee resilience at the next.

In the wild

Preparing for the International Space Station

Astronauts examine in detail what could kill them during a mission. They recommend engine modifications, create operating protocols, and prepare responses before the endeavor reaches the scale of an actual trip to the International Space Station.

→ Predictable risks are addressed before launch, leaving the mission exposed primarily to events that could not reasonably have been anticipated.

Scaling a Community Delivery Service

A local delivery service works with five couriers but plans to expand to fifty. Before hiring, the team maps routing failures, peak-demand overload, customer-support bottlenecks, and accident response, then changes its dispatch system and rehearses incident protocols.

→ The organization enters the larger market with repeatable operations rather than relying on the improvisation that worked at small scale.

Common mistakes

Trying to Scale the Idea

An idea does not reproduce results; people, processes, capabilities, and economics must form an organization that can do so.

Equating Volume with Scale

Doing more at proportionally greater cost is growth in activity, not necessarily a more capable or efficient organization.

Assuming Every Problem Must Grow

The preparation process may reveal that the problem is valuable but naturally limited to a smaller scope.

Is it for you?

Best for

It is best for teams moving a promising solution into higher-volume, higher-cost, or higher-consequence operation.

Not ideal for

It is not ideal when the problem has no need or justification for expansion beyond its current small scale.

From the transcript

“What scales up is organizations, organizations organizations”

Luis Perez-Breva · 40:51

“the only way you can scale up is you catch. If you catch everything that would look like a failure at the skate at which…”

Luis Perez-Breva · 41:57

“they just go through every excruciating detail about what will kill them right, and they plan for it.”

Luis Perez-Breva · 42:08

From the episode

Luis Perez-Breva Explains How to Be ‘Productively Wrong’

→