The average fare usd is not the typical one

Every skewed column has the same conversation attached to it, so here it is once, on fare_usd in ride-hail-trips.

The mean is 22.16. The median is 14.29. That is a gap of 55.1%, and it is not noise — the p90 is 44.54 and the max is 270.61, so the top of the distribution is dragging the average somewhere a minority of rows actually live.

select
  avg(fare_usd)                                                     as mean,
  percentile_cont(0.5) within group (order by fare_usd)             as median,
  percentile_cont(0.9) within group (order by fare_usd)             as p90,
  max(fare_usd)                                                     as max
from ride_hail_trips;

The practical consequence is that "average fare usd" answers a question nobody asked. If someone wants to know what a typical row looks like, the median answers it. If someone is forecasting a total, the mean is the right tool and the skew does not matter, because the mean times the count is the total.

So the rule is not "never use the mean". It is: name which question you are answering, then pick the statistic that answers it. A report that shows 22.16 with no median next to it has quietly decided you meant the first question.

There is a longer version of this in Describing a column without lying, and the pattern is the short one.