Skip to content
Resources / GA Applications

Guide / Dashboards

Design the decision before designing the dashboard.

A useful dashboard answers defined questions for a specific role and connects each measure to a dependable source and next action. Begin with decisions, metric definitions, time boundaries and data quality. Select charts only after the meaning is stable, and allow authorised users to inspect the records behind important totals and exceptions.

Questionwhat the reader needs
Evidencedefinitions and boundaries
Next stepa useful action path
Why it matters

Role

Identify who can influence the result.

CHAPTER 01

Name the user and decision.

A dashboard is not a general collection of charts.

01.1

Role

Identify who can influence the result.

01.2

Question

State what needs attention or comparison.

CHAPTER 02

Give each number a contract.

Make calculation and quality visible.

02.1

Definition

Document source, formula and exclusions.

02.2

Freshness

Show when the data last became reliable.

CHAPTER 03

Connect the view to action.

Observation alone is not an operational outcome.

03.1

Drill-through

Open the records behind a measure.

03.2

Queue

Route exceptions to an owner.

Continue through the resources system.

Each route answers a different operating question while retaining the same standards for evidence, responsibility and a usable next step.

Questions worth resolving

What to clarify before committing.

Does a dashboard need real-time data?
Only when the decision genuinely requires it.
Can spreadsheets be the source?
Yes after ownership, structure and update controls are reviewed.

Bring the real problem

Choose one operational decision to make visible.

Bring the current report, source and responsible role.