Framework

The Amundsen Preparation Standard

Before undertaking a high-risk venture, systematically think through every failure mode and build contingencies for each. The explorer who returns safely is rarely the boldest — they are the most prepared.

How it works

  1. 1Roald Amundsen beat Robert Falcon Scott to the South Pole and returned with his entire team alive. Scott's team froze to death. The difference was preparation, not boldness.
  2. 2Amundsen spent years planning routes, depot placements, and supply chains before the expedition began.
  3. 3Scott improvised under pressure. Amundsen had already made his decisions before the pressure arrived.
  4. 4Applied to startups: map failure modes before committing to a market, product, or spend decision. What breaks if this goes wrong? What is the recovery path?
  5. 5Preparation is not the opposite of speed. It is what makes speed survivable.

Hear it on the podcast

AI Is Quietly Stealing Your Life's WorkListen to the episode

More from this episode

Get the next framework first

One email a week with the frameworks, tools, and founder stories from the podcast. Free.

More frameworks for Operations & Scaling

Eliminate Before You HireWhen operational complexity makes you feel like you need to hire someone, the correct order of operations is: first try to eliminate the task entirely — does it even need to exist? Second, fix it with a focused project or sprint. Third, and only if both fail, find a person. The instinct to hire is a reasonable response to overwhelm, but it skips the harder and more valuable question of whether the thing causing the overwhelm needs to exist at all.Minimum Effective Dose (Operations)Build and do the least amount legally and operationally required to make a system functional. Bureaucrats over-build because every additional process justifies headcount and grant spend. Lean founders strip everything that is not legally required or genuinely operationally necessary. The goal is not cutting corners — it is refusing to rebuild complexity that only exists because someone was incentivized to create it.The Founder's FourAt MVP/pre-PMF stage, founders should only do four things: marketing, sales, customer conversations, and fundraising. Anything else is not value. A founder at this stage is at a developmental milestone — and these four activities are the only ones where their presence creates leverage that no one else can replicate. Technical execution is delegated; everything else is a distraction or a delegation failure.The Founder Operating SystemUse the same platform for your user-facing product and your internal tooling — then eventually let it run operations.Provisional-as-Priority StakeThe provisional patent application is the most underused tool in the founder's legal stack. Under the America Invents Act, the US runs first-to-file: whoever reaches the patent office first wins priority, regardless of who invented first. A provisional costs $65 for a micro-entity, requires no formal claims, and grants 12 months of patent-pending status. The gap between 700K non-provisional applications and only 170K provisionals per year is a market failure — not a founder behavior problem. The gatekeeper was always attorney economics, not founder willingness.Three-Track IP StrategyOphir's framework for choosing between the three available IP protection vehicles based on the nature of the invention, competitive environment, and operational realities. Patent, trade secret, and defensive publication each solve a different problem — and the wrong choice can leave you either over-exposed or locked into disclosure requirements that hurt more than they help.