Your dashboard should earn its place in the meeting

Start with the conversation the dashboard needs to support. What choice can the audience make? A portfolio review might compare investment and capacity. A programme review might resolve a dependency. A team review might unblock a specific piece of work.

Give the first view one clear purpose. Write the question in ordinary language, then identify the evidence needed to answer it. If a chart cannot support that question or explain a constraint, consider moving it into supporting detail. Information is useful when it has a job to do.

Before presenting a measure, record its definition, source, owner and reporting period. Explain the calculation and what it includes or excludes. Planned capacity and available capacity can answer different questions. A delivery date may represent an approved commitment, a working forecast or an aspiration. The label should make the distinction clear.

Show when the information was updated and describe material gaps. A blank field should not quietly become a green status or a zero. Where definitions differ, agree a common basis or show the difference explicitly. This preparation gives people a reason to trust the discussion behind the visual.

Keep the overview easy to scan, then let readers inspect the records that explain it. A trend might lead to a programme, a dependency or an individual risk. Give filters useful names and keep the selected scope and reporting period visible. People should know which part of the organisation they are looking at without reconstructing their previous clicks.

Use words alongside colour so status remains understandable when colour is difficult to distinguish. Label interactions clearly and consider keyboard use when testing the view. Supporting detail should explain the headline, including exceptions and uncertainty. A useful drill-down ends with evidence someone can discuss, rather than another unexplained total.

A red status can draw attention without explaining what help is needed. Add the reason, the consequence and the decision or action required. Where work is blocked by another team, make the dependency visible. Identify the person or role responsible for the next step and when the issue should be reviewed again.

Keep facts and judgement distinguishable. A calculated measure and an owner's assessment can both be useful, provided readers understand the basis. An overall status should leave room for the exception that matters. The purpose is to turn a broad concern into a conversation with an accountable next step.

Review a prototype with its intended audience. Ask them to find a priority, explain why it matters and identify their next action. Watch where they hesitate. An unfamiliar label, a missing comparison or a buried dependency can matter more than the styling of a chart.

Agree how the finished view will stay useful. A dated snapshot may suit a reporting cycle; a connected view needs an agreed refresh process, access model and support arrangements. Record who updates the information and who maintains the definitions. Handover should make the next reporting cycle manageable for the people who own it.