A number can be precise and still be difficult to interpret. Page views, response times, and error counts become useful only when we know what was measured and why.
Look at units, time windows, and the people or events included. An average can hide very different experiences. A change may reflect a new measurement method rather than a change in the system.
Start with a question you want to answer. Then choose the measure that speaks to it, and record the limits of what that measure can tell you.
Bring the idea into a day.
A list of unfinished tasks might suggest workload, confusion, or changing priorities. One conversation about the task can help explain what the count alone leaves uncertain.
Another angle on the story.
Follow the information through one complete task. What is created, where does it go, and what will someone need to understand it later?
- Check the unit and time window.
- Ask which events are included.
- Compare the number with the question it should answer.
Follow a related question
Compare one object under two light sources.
A color depends on the lightNotice what is complete or waiting.
A review that stays lightweightKeep learning
Related background to continue exploring this subject.
W3C: web standards W3C: accessibility, usability, and inclusion
