Step 1 — Should you use robust methods?

Check these triggers:

TriggerWhy it matters
Clear outliers in histogram or boxplotMean and SD are pulled toward outliers; unreliable
Distribution is heavily right- or left-skewedMean no longer represents the “centre”
Small with fat-tailed or unknown distributionNormal-based methods break down
Max SD / Min SD > 2 across groupsEqual variance assumption fails for t-test / ANOVA

Breakdown point: the fraction of contaminated data an estimator can tolerate before it becomes arbitrarily bad. Mean has breakdown point = 0 (one extreme outlier destroys it). Median has breakdown point = 50%.


Step 2 — Choosing a Location Estimator

EstimatorFormulaBreakdown pointWhen to use
Mean0%Data is Normal with no outliers
MedianMiddle value50%Heavy skew or many outliers
-Trimmed meanDrop smallest and largest values, average the restModerate outliers; recommended
Winsorised meanReplace smallest with , largest with , then averageSame situations as trimmed mean; keeps sample size intact

Trimmed vs Winsorised: trimmed mean removes extreme values; Winsorised replaces them with the nearest kept value. Winsorised variance is used to compute the SE of the trimmed mean — they go together.

Use (20% trim) as a sensible default when you suspect outlier contamination but don’t know the exact fraction.


Step 3 — Choosing a Scale Estimator

EstimatorFormulaFor Normal, converts to byBreakdown point
SDalready 0%
IQR25%
MAD$\text{median}(X_i - \text{median}(X))$50%

Rule of thumb: if you’re using a robust location estimator, use a robust scale estimator too. Pair trimmed/Winsorised mean with IQR or MAD.


Step 4 — Quick Flowchart

Is your data approximately Normal with no obvious outliers?
│
├─ Yes → Mean + SD
│
└─ No
    ├─ Moderate outliers or mild skew
    │   └─ γ-Trimmed mean (γ ≤ 0.2) + IQR or MAD
    │
    ├─ Heavy skew or many outliers
    │   └─ Median + MAD
    │
    └─ Unknown distribution / can't tell
        └─ Median + MAD (safest default)
            or Bootstrap CI (see Simulation & Bootstrap Guide)

Step 5 — Asymptotic Relative Efficiency (ARE)

ARE tells you how many extra observations the non-robust method needs to match the robust one.

  • Trimmed mean vs mean on pure Normal: ARE ≈ 88% (you “lose” 12% efficiency for robustness)
  • Trimmed mean vs mean on 10%-contaminated Normal: ARE > 100% (robust estimator is better)

The ARE trade-off: robust estimators are slightly less efficient on clean Normal data, but dramatically better once contamination exists. For real data where the distribution is unknown, robustness is usually worth the cost.


See also: L5 Robust Statistics · EDA Guide · Simulation & Bootstrap Guide