Who this is for: Teams explaining analytics and operational dashboards.
What to prepare
- One dashboard question
- Metric and date definitions
- Consistent illustrative dataset
- Dashboard and supporting-record screens
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Illustrative brief: create a 30-second explanation of a fictional request dashboard answering, “Which sample requests await review?” Show the example period and workspace scope. Focus Awaiting review: 2 within a six-request dataset containing two awaiting review, one draft and three approved records. Inspect matching rows R-014 and R-016, then open R-014. Close with “Two sample requests await review in this view.” Label all data illustrative and avoid claims about customer performance, causes of delay or improved outcomes.
Choose a question instead of a widget inventory
Suitable questions concern a defined view: which requests match a status, how a metric is composed or where to inspect a supporting record. Supply actual metric definitions, date-field meaning, filters and consistent sample data.
A dashboard screenshot without definitions is not enough to support a confident interpretation. A number may count events rather than objects, and a chart may use a different period from a headline card. Resolve those differences before writing the script.
Build a reading order
Establish scope first, then the focal metric, supporting context and the bounded answer. In the illustrative brief, the six-record breakdown explains the total while the two matching rows let viewers verify the featured count.
Keep one region active at a time. Preserve the metric label and period during close-ups. If a detail panel opens, maintain a stable identifier so the viewer can connect the aggregate view with the inspected record.
Separate observation from inference
“Two sample requests await review” follows from the example. “The team needs more staff” does not. A dashboard film should not turn an invented dataset or a selected snapshot into a business diagnosis.
For user training, add the route to the supporting data and explain how to change the view. For an executive overview, reduce control detail but keep definitions and scope. A more senior audience does not justify a stronger unsupported conclusion.
Review data and legibility
Reconcile card values, charts and rows before reviewing transitions. Inspect labels at the intended page size and ensure captions do not cover filters. If the dataset changes, recheck every dependent total and annotation.
Use a source register to record the dashboard version and definition owner. This illustrative brief does not claim a completed render, real customer result or measured comprehension benefit. The produced asset needs its own visual and factual review.
Review checklist
- The focal metric answers the stated question.
- Scope remains visible.
- Counts reconcile across the example.
- Interpretation stays within the supplied evidence.