data storytelling for market infrastructure

The plumbing of markets is invisible until it breaks. How to explain settlement, clearing, and custody to people who vote on their budgets.

Market infrastructure has a communication problem, and it arrives on a schedule. Settlement systems, clearing houses, custody chains — the machinery that moves trillions works so reliably that the people who fund it, regulate it, and depend on it forget it exists. Then a budget cycle arrives, and the team that runs the invisible thing has to explain, again, why the invisible thing costs money.

We’ve built data-storytelling layers for several infrastructure operators. The craft is different from product analytics or journalism, and the differences are worth writing down.

The reader is a board member, a ministry official, a bank CFO. They can absorb any amount of complexity that earns its place, and none that doesn’t. The failure mode isn’t dumbing down — it’s the opposite: charts that presume the reader already knows what a failed settlement costs and who eats the loss.

The correction is to lead with consequence, not mechanism. Not “T+1 settlement compresses the reconciliation window” but “when settlement fails, someone’s cash is in the wrong place overnight — here is how often that happens and what it costs.” Mechanism follows for those who want it. The number that opens the story must be a number the reader already cares about.

Infrastructure’s core achievement is that nothing happened. 99.98% uptime is a flat line, and a flat line argues for nothing. The techniques that work all involve making the counterfactual visible: what a bad day looks like next to a normal one, what peak volume did to the system during the March volatility and how close the margins came, what the near-misses were and what absorbed them.

One operator we work with now publishes a quarterly “stress ledger” — every incident and near-incident, its cause, and what contained it. It reads like an argument for the budget, because it is one. The alternative was a flat line and a request for money, which reads like a contradiction.

The organizational trap is producing each report as a one-off — the board deck, the regulator filing, the member update, each hand-assembled from different exports, each subtly disagreeing with the others. The disagreements are what kill credibility; a regulator who spots a number that doesn’t match the board deck stops trusting both.

The fix is structural: one knowledge hub holding the canonical series — volumes, fails, incidents, margins — with every story generated from it. The board version and the filing version can differ in depth, framing, and language, but never in the underlying number. Consistency is the trust story; the charts are just its delivery mechanism.

The last principle is cadence. Infrastructure stories persuade by accumulation — the same honest format, quarter after quarter, until the reader has a baseline and can spot a deviation themselves. That’s when the storytelling starts working: the audience stops needing the story explained, because they’ve internalized the shape of normal. A dramatic one-off deck can win a meeting. A boring series wins the budget, every year, from people who have stopped needing to be convinced.