Principle 3

Embrace Change

A startup must use change as an input, not treat it only as disruption.

Origin codename: Antifragile Adaptation Version 1.0 Updated 2026-07-08

Core idea

Change is not a temporary exception in startups. It is the medium. This principle asks teams to preserve direction while adapting plans, roles, and tactics without drama.

Why it matters in startups

Markets move, customers learn, capital changes, and teams discover reality by acting. Fragile cultures waste energy defending yesterday's plan.

What it looks like in practice

  • Review what changed before forcing old commitments forward.
  • Treat new constraints as design inputs.
  • Keep the mission stable while making the plan revisable.

What it does not mean

  • It does not mean chasing every trend.
  • It does not mean chaos as a management style.
  • It does not erase the need for commitments.

Founder behaviours

  • Explain what changed and why the response changed.
  • Keep strategy legible during pivots.
  • Create rituals for learning from volatility.

Team behaviours

  • Update assumptions when evidence changes.
  • Move quickly without turning every shift into a crisis.
  • Preserve useful context when plans change.

Failure patterns

  • Attachment to obsolete plans.
  • Morale drops whenever priorities move.
  • Teams confuse adaptation with lack of strategy.

Questions to ask

  • What has reality taught us since the last decision?
  • Which parts of the plan are still true?
  • How can this stress make the system stronger?

Representative scenario

A pricing experiment invalidates the original go-to-market plan. The team keeps the market thesis, changes the packaging, and uses the result to sharpen sales qualification.

Adapt without losing the thread.

Field note

From UV's practice

The origin language treats volatility as an input to the system. The useful move is not to romanticize change, but to adapt without losing strategic direction.

Related principles

Back to all principles