Mean vs median for product metrics: why averages mislead on revenue, session length and other skewed data, and how to choose the right one.
By Sergey BruhPublished 8 min read
A free course for PMs and marketers: short lessons, real product data and exercises with instant feedback.
Start the free courseMean vs median in one line: the mean is the sum divided by the count, the median is the middle value once you sort the data. When data is roughly symmetric, they are close and either works. When data is skewed, as revenue per user, session length, order value and time-to-delivery almost always are, a few extreme values drag the mean far from what a typical user experiences, and the median gives a more honest picture of "normal". Neither is always right: use the median to describe the typical user and the mean when you need totals, such as revenue forecasts or budgets.
Here is 90-day spend for ten customers of CatChow, an online pet-food shop, sorted from smallest to largest:
Customer 10 is a cat shelter that stocked up for the whole winter.
Now look at the table again. Nine of the ten customers spent less than the mean. If a marketer builds a campaign for "our average customer who spends 75 dollars", it targets almost nobody. The median of 31 dollars is much closer to what a regular CatChow customer looks like.
To see how fragile the mean is, change the shelter's 480 to 48. The mean drops from 75.2 to 32 dollars. The median stays at 31. One customer moved the mean by more than 40 dollars and didn't touch the median at all.
A distribution is skewed when one tail is much longer than the other. Product data is full of right-skewed metrics, with most values bunched near the low end and a long tail of large ones:
In a right-skewed distribution, the mean is pulled toward the long tail, so mean > median. The bigger the gap between them, the more skewed the data. That gap itself is a quick diagnostic: if your dashboard shows an average session of 7.5 minutes but a median of 3, the "average" user doesn't exist, and a handful of very long sessions are carrying the number.
The median is not automatically better. The mean has one property the median lacks: mean × count = total.
That makes the mean the right tool whenever the decision is about totals:
So the rule is not "median good, mean bad". It is: describe the typical user with the median, plan money with the mean, and always check both.
The median has blind spots of its own.
Zero-heavy metrics. Suppose 1,000 people visit a CatChow landing page, 40 buy, and each order is 50 dollars. Revenue per visitor has a mean of dollars and a median of 0, because more than half of visitors spent nothing. Run an A/B test on that page, and both variants will almost certainly have a median of 0, even if one earns twice as much. For metrics like this, report the conversion rate and the mean order value among buyers separately.
Changes in the tail. A loyalty programme that makes top customers order more often may not move the median at all. If the tail is exactly what you're trying to change, the median is the wrong lens.
When you need something between the two:
A common question after "mean or median?" is "then which test do I use?". If you compare two groups on a skewed metric:
Whichever you choose, decide before looking at the results. Switching from mean to median because the median "looks better" is a quiet way to fool yourself.
Neither is better in general. The median describes a typical value and resists outliers; the mean connects directly to totals. For skewed product metrics, look at both, and pick the one that matches the question you are answering.
Because the data is right-skewed: a few very large values pull the mean up while the median, which only depends on the middle of the sorted data, barely moves. Revenue, order value and session length usually behave this way.
Report the mean when you use AOV for revenue planning, because mean AOV times the number of orders gives total revenue. Add the median, or a few percentiles, when you want to show what a typical order looks like.
The average after dropping a fixed share of the lowest and highest values, for example 5% or 10% from each end. It is a compromise between the mean and the median: less sensitive to outliers than the mean, but it uses more of the data than the median.
The free lesson Typical value: mean, median, mode works through real-looking CatChow data and lets you practise choosing the right summary, with quizzes and an AI-checked task. When you're ready for the next step, Outliers and skewed data shows how to spot and handle the extreme values behind most misleading averages. Both are part of the free course Statistics for Product Managers and Marketers.
