usage-trend-narrationlisted

# Usage Trend Narration ## Why this exists A number without a story is not useful, but a story without discipline is worse — it's how "usage dropped 8%" quietly turns into a confident, wrong explanation that then drives a bad decision. Two failure modes show up constantly: 1. **Narrating the aggregate** — reporting one top-line number when the real story is that one segment moved sharply and the rest were flat, which the aggregate hides. 2. **Correlation dressed as causation** — "usage dropped after the pricing change, so the pricing change caused it" without checking for other things that happened in the same window (a competing launch, a holiday, an outage, a marketing push that ended). This skill is a discipline for avoiding both, so the narrative earns the trust the chart alone can't. ## Process ### 1. Establish the baseline and cadence before looking at the delta Know what "normal" week-over-week or month-over-month variance looks like for this specific metric before deciding a move is notable. A metric that normally swings ±5% needs a bigger move to be a story than one that's usually flat. Also check for known seasonality (day-of-week effects, end-of-quarter spikes, holiday dips) before treating a cyclical pattern as a trend. ### 2. Segment before you narrate Break the aggregate down by at least one dimension — plan tier, cohort age, platform, geography, feature — before writing anything. Specifically check: is this move happening broadly, or is it one segment