A focused first dashboard that identifies the asset, shows current state and trend, and makes the next action clear.
Name the reader and the question
A service engineer diagnosing one unit needs a different view from a product manager comparing a fleet. Write the reader and question at the top of the dashboard brief before choosing visual components.
- Which asset or fleet is in scope?
- What must the reader know within the first few seconds?
- Which time interval reveals normal and abnormal behaviour?
- What action should follow an exception?
Build the first useful view
Use a small number of widgets with explicit units, state labels, and time ranges. Visual decoration should never hide missing data, stale timestamps, or uncertain quality.
- 01Create a clearly named dashboard for one operating audience.
- 02Add asset identity and last-seen status.
- 03Add the current value or state for the primary variable.
- 04Add a trend using the operating interval that exposes meaningful change.
- 05Add the event or service status needed to close the loop.
Validate it with the person who will act
Review the dashboard with a service or operations user using a normal case, a stale-data case, and a known exception. Confirm that colours, thresholds, units, and labels mean the same thing to the people using the equipment.
Completion check: the intended user can explain what changed, whether the data is current, and what to do next without asking the builder.