Dashboard · DucDZ

01

Context and metrics

Understand the numbers before deciding what to do.

Show the current situationSummarize information relevant to the user and highlight important changes since their last visit.Keep the greeting brief. Prioritize what has changed and the work the user needs to continue.Give metrics useful contextShow metrics that support the main task, with their units, date range, and update status.Every number needs a unit, a clear definition, and a date range that makes it meaningful.Example “42 orders processed in the past 7 days” is more useful than an isolated number 42.Make the date range clear and adjustableShow the date range and time zone when relevant, and apply the same range to related metrics.The “Today” label must use the same time zone as the data calculation.Example Calculate today's statistics in Asia/Bangkok time rather than using the UTC calendar date.Use a clear comparison baselineState the comparison period, units, and meaning of an increase or decrease instead of showing arrows alone.Use equivalent calculations for both periods, and disclose when their lengths differ.Show how current the data isShow the last refresh time or known delay, and provide feedback when users request an update.Shows the update time and time zone next to the data. An old number should be recognized even if the user does not click refresh.

02

Tasks and actions

Return to work and handle tasks that need attention.

Make recent work easy to reopenLet users return to recently created or edited items, with recognizable names and timestamps.Each activity line should indicate the actor, object, and timing; Opens the correct record instead of a generic list.Prioritize tasks that need attentionHighlight deadlines and decisions that need attention, and state the next action clearly.Show alerts that require a decision. Too many alerts make important tasks harder to notice.Keep frequent actions within reachProvide quick access to common tasks, using specific action labels.Set actions according to what you usually do after viewing the data, such as processing pending requests; check permissions before displaying.

03

Data states

Distinguish loading, missing data, and loading errors.

Guide users when there is no dataExplain what will appear here and offer a first step to create, import, or connect data.Suggest a first create, import, or connect action that matches the reason the data is missing.Load each area without losing contextKeep widget layouts stable. Do not present old numbers as the results of a new filter.Load each block independently when possible; keep the position and label so the page doesn't jump when a data source is slow to respond.Distinguish errors from zero valuesIdentify the area that failed to load, keep the selected filters, and offer a retry without clearing areas that loaded successfully.When a widget fails, keep the available widgets and retry the same part with the same selected time interval.Example Show “Revenue could not be loaded — Retry” instead of displaying zero revenue when the connection fails.

04

Accessibility and control

Make the dashboard usable for different roles and input methods.

Support reading and interaction without relying on colorLabel charts, offer a text representation of the data, and make every action accessible from the keyboard.Provide text labels and metrics for charts; check to read in logical order when removing multi-column layout.Allow layout changes when usefulIf appropriateIf users can hide or reorder widgets, provide a way to restore defaults and an alternative to dragging.A dashboard with fixed tasks may not need customization. Add layout controls only when they help users.

Dashboard Web app

Context and metrics

Tasks and actions

Data states

Accessibility and control

How to review

Start with the decisions users need to make

Check consistent date ranges and units

Keep successful results when one widget fails

Offer customization when it meets a need

Usage examples

Order processing dashboard

One widget fails to load

Find a checklist

No checklists found