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.
An example to consider.
Imagine a table showing how often a guide is opened. Ask which question those visits answer before treating a larger count as a better reading experience.
Put it in perspective.
A helpful explanation gives the reader enough context to act. More detail can wait until the next question makes it useful.
- Check the unit and time window.
- Ask which events are included.
- Compare the number with the question it should answer.
Follow a related question
Choose a nonurgent source.
Choose the moment to checkAsk which conditions the demonstration assumes.
Beyond a compelling demonstrationKeep learning
Related background to continue exploring this subject.
W3C: web standards W3C: accessibility, usability, and inclusion
