The Myth of the “Average User” in Product Design

Product designers often talk about the “average user.”

That imaginary person who is typical, predictable, and representative of the largest group.

But in real life, such a user doesn’t exist.

In this post I want to explore why relying on the idea of an average user matters — and why it can lead teams astray.

Averages Describe Data, Not People

Averages are statistical constructs.

They tell you about the center of a dataset — the median, the mean — but they say nothing about variation. They don’t describe the range of needs, contexts, abilities, or goals that real users bring to a product.

Designing around averages smooths diversity into a single vector.

This isn’t just an abstract critique: when engineering teams optimize for numbers — like average session length or average retention — they often end up aligning the product with what is measurable, not what is meaningful. That tension appears in the way metrics reshape systems over time, explored in The Metrics That Quietly Destroy Good Software

.

Defaults Assume Uniform Behavior

One reason “average user” persists is convenience.

Defaults are cheap to set. A single configuration works for most users most of the time. And as seen in The Power of Default Settings in Digital Systems

, defaults are powerful precisely because they reduce complexity for product teams — and for users who rarely change what’s preselected.

But “most” is not “all.” Defaults become directional choices, not neutral conveniences.

When Simplifying Becomes Restrictive

Teams often say something like “95 % of users never change this setting.” That might be true, but it doesn’t mean settings are irrelevant.

People with different needs — people who are more experienced, or who are interacting in different environments — are pushed to the margins by interfaces optimized for aggregate behavior.

As described in The Illusion of Control in Modern Digital Life

, interfaces can present choices while simultaneously narrowing structural flexibility.

Experienced users don’t always want simplicity. Sometimes they want control.

Averages and Personalization

Personalization systems — like recommender engines — are built on statistical inferences. They cluster users based on patterns, assign weights, and tune outputs to maximize engagement.

That creates environments optimized for predicted behavior — not necessarily individual needs.

You can explore this dynamic in more detail in Recommendation Algorithms and Behavioral Shaping

.

When systems adapt to predictable patterns, they reduce diversity of experience over time.

Behavioral Patterns and Consent

Another area where “average user” logic shows up is consent and permission dialogs.

If most users click “accept,” a team might simplify or gloss over consent mechanisms — but that does not mean users understood the underlying implications.

This phenomenon was discussed further in Why Permission Dialogs Don’t Create Real Consent

, where interface structure and true agency diverge.

Edge Cases Are the Norm at Scale

In small systems, extraordinary cases feel rare.

In large, distributed systems with millions of users, edge cases aren’t exceptions — they’re inevitable.

Designing only for average behavior eliminates nuance, and that nuance is often where meaningful value resides.

For example, accessibility needs, cultural differences, and cognitive preferences can vary widely across users. There is no single “average context” that captures all of them.

Product Design Beyond Averages

So what does it mean to reject the myth of the average user?

Practically, it means:

designing with flexible defaults, not hard assumptions

offering layered interfaces that can grow with expertise

avoiding optimization solely for median metrics

understanding that individual contexts matter

experimenting with inclusive patterns, not one-size-fits-all

These are not easy choices. They complicate roadmaps and require additional thinking. But they also reflect reality more accurately.

Products serve individuals interacting at scale — not statistical shadows.

Conclusion

The “average user” is a convenient fiction.

It simplifies decisions. It accelerates roadmaps. It reduces cognitive load for teams.

But it also narrows systems, erases diversity, and reinforces structural assumptions that might not serve real people.

Good design embraces variation — not just the center of a distribution.

Read the full article (and links to related essays) here:

https://50000c16.com/average-user-myth-product-design/