Product demos & UI / Storyboard

Dashboard question-to-answer storyboard

Explain a dashboard through the decision it supports. This illustrative 30-second sequence answers which sample requests await review, using a consistent count and matching records.

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

Who this is for: Teams explaining reporting screens.

What to prepare

  • Metric definitions
  • Consistent sample dataset
  • Dashboard and supporting-row screens
  • Period and scope labels

Scene-by-scene storyboard

30-second planning sequence · illustrative copy and visual direction

  1. 01

    0–5s

    Ask the question

    Show the dashboard title, example period and active workspace scope with the sample-data label.

    On screen:Which sample requests await review?

  2. 02

    5–10s

    Find the focal metric

    Highlight the actual Awaiting review card with value 2. Preserve its label and period.

    On screen:Awaiting review: 2

  3. 03

    10–15s

    Show the denominator

    Inspect the status breakdown: 2 awaiting review, 1 draft and 3 approved, totaling 6 sample requests.

    On screen:Six sample requests in this view

  4. 04

    15–21s

    Inspect supporting rows

    Show R-014 and R-016 in the matching filtered list using the real navigation behavior.

    On screen:Two matching sample records

  5. 05

    21–26s

    Open one item

    Open R-014 and retain its status and identifier. Avoid introducing a new metric.

    On screen:R-014 · Awaiting review

  6. 06

    26–30s

    State the answer

    Hold the scoped result with the example period still identified.

    On screen:Two sample requests await review in this view

Make it your own

Dashboard question
Choose one question and the metric definition needed to answer it.
Sample data
Replace every card, status total and supporting record with one consistent illustrative dataset.
Period and scope
Keep the reporting period, filters and population labels visible in the relevant scenes.

Prepare consistent data

Supply actual metric definitions and a fictional dataset whose cards, chart and rows agree. Confirm whether the measure counts records or events. The six-request example is invented for explanation and must not be framed as a customer outcome.

Adapt the question

A different metric requires a new supporting chain, not just a changed headline. For training, add the route to the supporting rows. For an executive explanation, preserve scope while reducing control detail. A 60-second version can inspect another relevant segment.

Review observation and inference separately

The shown count supports a statement about this view. It does not establish understaffing, improved performance or causation. Keep interpretation within the supplied evidence and inspect the focal number at the intended viewing size before production approval.

Review checklist

  • The opening question matches the metric.
  • Totals reconcile with supporting records.
  • The conclusion stays within the shown scope.
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