Design for understanding
Different questions need different visual structures. These are starting points for an actual brief.
Charts can clarify how quantities differ when the unit, baseline and grouping are explicit. A report graphic should help a reader answer a particular question, not simply make a dataset look busy.
The supplied data needs clear definitions, a known source and the correct permissions. Data validation and specialist interpretation should be assigned explicitly; design does not independently verify the source.
Outline this project ↗A dashboard composition can separate a key question from supporting measures. Grouping, labels, spacing and chart selection help establish which information belongs together and what action it supports.
A visual concept is distinct from a deployed analytics system. Data connections, refresh behaviour, access control and business logic require a separately defined technical scope.
Outline this project ↗Relationships, stages and categories often need a diagram rather than a chart. The work can focus on a sequence, a comparison or a hierarchy, with labels written for the people who will use it.
Provide the process facts, terminology and intended audience. Final content accuracy and approvals remain part of the project brief, especially when the diagram informs a consequential decision.
Outline this project ↗