Principle 1

Assume Nothing

A startup must not build decisions on unverified assumptions.

Origin codename: Zero-Assumption Protocol Version 1.0 Updated 2026-07-08

Core idea

Assumptions are invisible bugs in a startup's operating system. The principle asks founders and teams to verify the signal before they build strategy, product, hiring, or conflict narratives on top of it.

Why it matters in startups

Early-stage companies move with incomplete information. That is unavoidable. The danger begins when an unknown becomes treated as truth and spreads through the team as certainty.

What it looks like in practice

  • Name what is known, unknown, and assumed before committing.
  • Inspect customer evidence, system data, and first-hand context.
  • Convert strong opinions into tests, questions, or observable checks.

What it does not mean

  • It does not mean waiting for perfect certainty.
  • It does not mean distrusting every person.
  • It does not excuse slow execution when a reversible test is available.

Founder behaviours

  • Ask what evidence would change the decision.
  • Separate narrative from fact during strategy reviews.
  • Reward people who surface uncertainty early.

Team behaviours

  • Clarify ambiguous instructions before executing.
  • Bring source material into discussions.
  • Document assumptions beside decisions.

Failure patterns

  • Roadmaps built on imagined customer needs.
  • Conflict caused by invented motives.
  • Metrics interpreted without checking definitions.

Questions to ask

  • What are we treating as true without evidence?
  • Who has first-hand knowledge?
  • What is the smallest test that can verify this?

Representative scenario

A founder hears that enterprise buyers need a compliance dashboard. Instead of adding it to the roadmap, the team interviews five active prospects, reviews lost-deal notes, and discovers the real blocker is procurement documentation.

Do not build on fog. Verify the foundation first.

Field note

From UV's practice

In UV's operating vocabulary, this principle protects the team from false certainty. It asks people to slow down just enough to inspect the signal before speed turns an assumption into strategy.

Related principles

Back to all principles