Start with demand. The entry pairs “Weekly arrivals” with “Trend”. That pairing is useful only when it is clear why the context supports the state. More charts can make a dashboard less useful when none of them answers the question that brought the reader there.
Begin with the constraint
Write the decision first, then choose the smallest set of measures needed. Add definitions where interpretation could change the result.
Example: Demand
The illustrative record contains weekly arrivals. Its state is trend. Ask what evidence supports that state, which detail is still uncertain and whether the next person could understand it without reading a separate message thread.
Questions for a working review
- Define the decision the reader needs to make. For demand, use “Weekly arrivals” as the starting context.
- Find the source behind the example record. For demand, use “Weekly arrivals” as the starting context.
- Write down the open question before choosing a state. For demand, use “Weekly arrivals” as the starting context.
A small exercise
Take one recent dashboard planning example from your own process. Write its context without using a status label, then add the label separately. If the two contradict each other, investigate the source before updating the record. Compare the result with “Capacity” in the demonstration to see which distinctions your process needs.
These are planning notes. The specimen is illustrative, and the preview does not process live work.
More resources →