Product demos & UI / Guide

Explain a dashboard without animating every widget

Start a dashboard film with a question, then reveal only the data needed to answer it. Keep the reporting period and filters visible so the featured number has context. Animate the reading order rather than every widget.

By AnimroUpdated 2 min readAI-assisted · independently agent-reviewed

Who this is for: Teams explaining reporting interfaces to evaluators or users.

What to prepare

  • One dashboard question
  • Actual metric definitions
  • Visible period and filters
  • Consistent illustrative totals and supporting rows

Give the dashboard a specific question

“Explore powerful analytics” does not tell a viewer which number matters. “Which review requests remain open in this example period?” establishes a selection rule. Choose the question before choosing the most colorful chart.

Record the metric definition, date range and filters from the actual product. If a card counts requests and a chart counts events, they cannot be presented as interchangeable. Ask the product owner to clarify the difference before writing the interpretation.

Illustrative reading order for a small queue

Use fictional sample data: six requests in the displayed example period, of which two remain Awaiting review. The film explains how to inspect that dataset; it makes no claim about customer workload or performance.

  • Frame the question: show the dashboard title, period and “Illustrative data” label.
  • Focus the card: highlight “Awaiting review: 2” while keeping its label and the active period in frame.
  • Explain composition: show the status breakdown for six requests, with two awaiting review, one draft and three approved.
  • Inspect supporting records: show R-014 and R-016 in the matching filtered list. Preserve identifiers when opening one detail panel.
  • State the bounded answer: “Two sample requests await review in this view.” Do not claim the organization has only two open requests unless the scope establishes that fact.

Keep context stable while attention moves

Dim unrelated regions lightly or use a border around the current focus. Leave enough surrounding interface to recognize the dashboard. Making every widget count upward simultaneously asks viewers to divide attention before they know the question.

If the numbers are supplied as still images, camera movement and callouts can explain them. Invented count-up animations may imply a live data refresh. Use that treatment only when its illustrative nature is clear and it does not misrepresent the product’s behavior.

Distinguish observation from explanation

“Two requests are awaiting review” is an observation supported by the example. “The team is understaffed” is an interpretation requiring evidence beyond this screen. Put unresolved questions in the narration as questions, or omit them.

For an executive audience, emphasize the question and its scope. For user training, add how to reach the supporting records and change the period. Do not use a stronger conclusion simply because the audience is senior.

Review checklist

  • The focal metric answers the opening question.
  • Period, filters and sample-data label stay available.
  • Totals and supporting records agree.
  • The conclusion does not infer causes or outcomes absent from the data.
Explore product demos & ui ↗

Use case / Product demos & UI

Dashboard walkthrough videos

Plan a dashboard walkthrough around a specific question, one focal metric and supporting records, with illustrative data and careful interpretation.

Read resource