1. No visuals without data

We only create graphics, charts, or maps that are based on actual, verified data. The data team does not recreate visuals for aesthetic purposes or generate graphics without meaningful analytical content.

2. How the data team works

  • We design visuals that prioritise clarity, correctness, and insight.
  • We choose the most effective visualisation technique for the message and the audience—not necessarily the format originally requested.
  • We follow organisational style standards for consistency and readability.
  • We challenge unclear or incomplete requests to ensure the final product is accurate and meaningful.
  • We collaborate closely with domain experts to ensure contextual accuracy.

3. How coworkers can improve their visualisation requests

To help the data team deliver strong, timely outputs:

  • Clearly define the purpose of the visual (“What is the point?”).
  • Identify the target audience and how the visual will be used.
  • Provide the data source, time period, filters, and any operational nuances.
  • Suggest a draft title that conveys the intended key message.
  • Share examples of past visuals only as inspiration, not as templates.
  • Provide realistic deadlines and indicate if revisions will be needed.

Clear requests reduce iteration, improve quality, and lead to more actionable visuals.

4. Responsibility: Domain Expert vs. Data Expert

Domain expert (Requestor)

Responsible for:

  • Defining the purpose of the visual.
  • Explaining the context, operational relevance, and intended use.
  • Identifying the audience.
  • Confirming the interpretation and narrative accuracy of the final result.
  • Ensuring the visual aligns with operational reality.

In short: The requestor owns the “what” and “why.”

Data team (creator)

Responsible for:

  • Selecting the appropriate visual format based on the purpose and audience.
  • Ensuring data quality, correct aggregation, and appropriate analytical methods.
  • Designing the visual according to best practices and style guidelines.
  • Identifying potential misinterpretations and preventing misleading visuals.
  • Ensuring technical and visual clarity.

In short: The creator owns the “how.”


Back to top

Placeholder footer content. Lorem ipsum dolor sit amet.

This site uses Just the Docs, a documentation theme for Jekyll.