Skip to main content
    Davies Meyer – home

    Make your numbers understandable.

    Data visualisation connects analysis and design. We create charts and views that help people compare, understand relationships and see uncertainty.

    Discuss visualisation

    The chart is part of the explanation

    A number can be correct while its presentation is misleading. Without a period, denominator or comparison, readers have to guess its meaning. We start with the question a visualisation should answer and the people who need to use it.

    Bring analysis and design together

    Our approach connects metric definitions, information design and UX. A management view needs different detail from an operational report or a public infographic. The aim is a presentation that connects its message, evidence and possible next action.

    Choose a form that serves the question

    Do you need to show change over time, differences between groups or the composition of a total? That question guides the chart choice. Scales, units, periods and sources belong alongside the data.

    Illustrative example, not a client result: enquiry volume can rise while the qualified share falls. Showing count, share and their definitions makes this distinction visible. It does not establish the cause.

    Make it readable and usable

    We plan clear labels, meaningful contrast and explanations that do not rely on colour alone. Interactive views include keyboard access and appropriate text or table alternatives, followed by checks of the actual implementation.

    An initial project might deliver a revised report template or a clickable prototype with agreed views. Data connections and ongoing refresh are separate tasks that we explicitly scope.

    Deliver a presentation system your team can use

    Depending on scope, you receive chart templates, labelling and state rules, and a tested prototype or implemented view. Missing values, empty results and stale data need understandable states just as the normal case does.

    How we deliver

    01

    Understand usage

    Identify the audience, decision and context of use.

    02

    Define the data

    Document metrics, units, comparisons and limitations.

    03

    Design the views

    Develop charts, information hierarchy and explanations.

    04

    Test understanding

    Check whether users interpret the message and its limits correctly.

    05

    Handover or build

    Deliver templates and rules or implement the agreed view.

    FAQ

    Sources and technical context

    Which report still needs too much explanation?

    Show us a typical view and tell us who needs to make which decision. We will shape a focused starting point.

    Discuss visualisation