The scientific method tests the hypothesis.
Normalization turns an assumption into a decision.

A product leader can be punished this quarter for pursuing evidence that could change the roadmap. They may never be blamed next year when the product misses the market.

That’s the asymmetry.

When evidence is weak, preserving uncertainty creates immediate, visible risk. Building on an untested assumption creates delayed, diffuse risk. The decision-maker carries the first. The organization absorbs the second.

So teams often choose the path that feels safer internally—even when it leaves the larger risk unresolved.

The Assumption Gap describes the distance between what an organization believes and what it knows. The Normalization Law describes what happens when a plausible direction is treated as the answer before evidence has tested it.

Lean UX applies the logic of the scientific method to product development. It makes assumptions explicit, turns them into hypotheses, tests them, learns from evidence, and then decides what level of commitment is justified. Normalization breaks that sequence by converting an assumption into a decision before it has been tested.

Scientific Logic — Test Before Committing
Observe→ Form a hypothesis→ Test→ Learn→ Decide
Normalization — Commit Before Testing
Observe→ Settle on an answer→ Decide→ Specify→ Build→ Test later

The difference is not whether assumptions exist. It is whether the emerging answer is tested before the organization commits to it.

An assumption is not yet a hypothesis. A hypothesis is an assumption made testable. Normalization is attractive precisely because it skips that step—it reduces internal decision risk without reducing external market risk. The market consequences of a bad assumption may not surface for months, and by then tend to get attributed to execution, timing, sales, pricing, adoption, or change management rather than to the assumption itself. The Normalization Path can be locally rational even when it’s systemically dangerous.

The cause isn’t primarily ego, ignorance, or bad leadership. Normalization converts an uncomfortable question into a plan the organization knows how to accelerate—it creates direction, alignment, estimable work, executive confidence, roadmap clarity, and visible progress. The unresolved uncertainty isn’t removed. It’s transferred to the market.

Where Both Paths Begin

Both paths start the same, ordinary way.

1

The team sees an opportunity

A new product or improvement may create value.

2

The team discusses what should work

People bring experience, precedent, preferences, constraints, and beliefs about the right direction.

3

One direction begins to feel right

A plausible answer gains support before the team has evidence that it will produce the intended outcome.

↓
A direction feels right. What happens next?
↙Trust the directionTreat it as the answer
↘Test the directionTreat it as a hypothesis

The Normalization Path

Commit before testing

The Evidence Path

Test before committing

Same decision moments. Different standards of proof.

Frame the direction

Treat it as the answer

Treat it as a hypothesis

After a preferred direction emergesWhat evidence supports this direction—and what is still belief?
Before requirementsWhat are we trying to learn before we commit?
Respond to uncertainty

Make a commitment

Design a test

Build confidence

Translate the decision into requirements

Gather evidence

Before changing the testDoes this improve the test—or remove what needs to be tested?
Before roadmap commitmentWhat evidence has this level of investment earned?
Decide investment

Commit the plan to the roadmap

Advance, revise, or stop based on evidence

Demonstrate progress

Measure delivery

Increase investment with confidence

Validate

Test after building

Continue learning while scaling

Where Each Path Leads
Product reaches market
The organization has increased confidence in delivery, but the original assumption may remain unresolved.
The roadmap becomes certain. Market fit does not.
Product moves toward market fit
The team reduces avoidable risk before scaling investment.
Evidence earns the commitment.

The Evidence Path doesn’t guarantee market fit. It improves the quality of the decision and increases the probability that investment follows learning.

Not a Story About Villains

Every hypothesis begins with assumptions—that’s not the problem. An assumption is not yet a hypothesis; a hypothesis is an assumption made testable. The problem occurs when an untested assumption is treated as though it were already established, and becomes the basis for a decision that gets converted into roadmap certainty without ever being tested. The Normalization Law describes a predictable organizational shortcut under uncertainty, not a personal failing.

Leaders sometimes must decide before sufficient evidence exists—that is not the failure. The failure is when the decision gets presented as though it were already validated, and the roadmap treats an open hypothesis as settled fact.

Testing later isn’t always wrong—some propositions require a live product to evaluate. The failure mode is using “we’ll test it later” to avoid cheap, decision-relevant learning before a large commitment, or testing only after what needs to be tested has already been removed.

One path gets you to market. The other improves your odds of market fit.