Close view of a laptop and monitor running a custom financial dashboard

Design

Designed around the decision, not the software

A dashboard is a set of choices about what a reader is allowed to see first. We make those choices with your finance team before a single chart is styled.

The design sequence

Five stages. Each one produces something you can keep even if you later pause the build: notes, a dictionary, a map of views, a visual system, and a prototype on real extracts.

  1. 01

    Listening fortnight

    Structured conversations with the finance director, the person who runs the close, and one operator who argues with the numbers. We ask what decision was late last quarter, and which figure caused the argument.

  2. 02

    Measure dictionary

    Each candidate tile gets a name, a formula, a source, a refresh rhythm, an owner, and the comparison that matters. If two people disagree, the disagreement is written down before it is designed away.

  3. 03

    Information architecture

    We separate the Monday management view, the weekly operating view, and the board pack. Density is a choice. Analysts can have more grain. Directors get fewer tiles and a written bridge.

  4. 04

    Visual system

    Type, colour, and comparison marks follow a small set of rules so a forecast cannot be mistaken for an actual. We avoid decorative charts that do not change a decision.

  5. 05

    Prototype on your numbers

    A working slice, not a slide of imaginary data. We use a recent close, anonymised if you need that for a wider audience. You react to your own cash bridge, your own branch margin, your own lockup. That is when the dictionary either holds or gets rewritten.

Printed reporting pack, linen notebook, and a tablet on an oak desk

What the design deliberately leaves out

We do not start from a gallery of chart types. We do not promise a tile for every ratio a textbook lists. Vanity measures — follower counts of the finance function, traffic-light grids with no threshold — are refused in the first draft.

We also do not pretend the dashboard is an accounting system. Journals, statutory accounts, tax computations, and audit files stay where they belong. The dashboard reads from those systems. It does not replace the ledger, and it does not constitute financial advice.

If a number cannot be defined, it does not earn a place on the front page. It can live in an appendix until the definition is agreed. That restraint is the design.

Read the reporting standards

Bring us the argument your last pack could not settle

A short note about entities, systems, and the readers is enough to start. We will tell you plainly if a custom dashboard is the wrong tool.

Start a design conversation