When a team asks us to "look at the numbers," the dashboard is usually full of snapshots: revenue this month, errors today, latency right now. Snapshots are easy to produce and easy to argue about. What they don't tell you is the one thing that actually matters — which way things are heading.
The gradient is the point
A snapshot answers where are we? A gradient answers are we getting better or worse, and how fast? The second question is the one you can act on. A latency of 200ms means little on its own; a latency that's been climbing 5% a week for a month means you have a problem that compounds.
If you only get to keep one metric, keep the slope.
This is why every system we ship leans toward trend over level: rolling comparisons, week-over-week deltas, a clear marker for the direction of change. Not because levels don't matter, but because direction is what tells you whether today's work is paying off.
Make the direction obvious
- Show change, not just state — a delta next to every number that has one.
- Pick a window deliberately. Day-over-day is noise; quarter-over-quarter is too slow to steer by. Most things want a rolling week or month.
- Distinguish a blip from a trend before anyone reacts to it.
Keep your gradient positive, and the snapshots take care of themselves.