Experimentation is supposed to help product teams learn faster.

But there is a point where running more experiments can actually make the process less useful.

I’ve seen teams become so focused on experimentation that every product decision starts becoming a test.

Change a button? Test it.

Change a workflow? Test it.

Change a message? Test it.

Eventually, teams can become exhausted by the process, while the quality of learning goes down.

That’s experiment fatigue.

What Is Experiment Fatigue?

Experiment fatigue happens when teams run too many experiments without enough attention to their purpose, quality, or learning value.

It can affect both product teams and users.

Internally, teams spend increasing amounts of time designing, implementing, monitoring, and analyzing experiments.

For users, constantly changing experiences can create inconsistency and confusion, particularly when multiple experiments affect the same workflow.

The problem isn’t experimentation itself.

It’s experimentation without enough discipline.

More Experiments Don’t Always Mean More Learning

Experiment velocity is often treated as a success metric.

A team might celebrate running 50 experiments in a quarter.

But what did those experiments teach you?

How many changed a product decision?

How many invalidated an important assumption?

How many produced results that nobody acted on?

If most experiments don’t influence what the team does next, increasing experiment volume isn’t necessarily improving the product development process.

Start With a Meaningful Question

Every experiment should answer a question that matters.

Instead of:

“Which button color performs better?”

Ask:

“Will making th