Insights · Data analytics

The dashboard nobody opens

Every insurer has one. It took a quarter to build, it pulls from the warehouse nightly, it has twenty tiles, and its usage log shows four sessions last month, three of them from the person who built it.

The instinct is to blame adoption. Usually the problem is upstream: the dashboard answers questions nobody was asking, in an order nobody thinks in.

Reporting is an argument, not an inventory

Actuarial reporting tends to be organised around what the data contains rather than around a decision. Every metric available gets a tile, every tile gets equal weight, and the reader is left to assemble a view. That is work the report should have done.

A report that gets used usually opens with a single claim — new business is running below plan, driven by one channel — and then supports it. Everything else is a second click.

If the reader has to build the story themselves, they will build it in a spreadsheet instead, and yours becomes the version nobody trusts.

Three practical tests

• Name the decision. Which specific choice does this change, and who makes it? If the answer is a role rather than a person, it is not ready.
• Check the cadence. A monthly metric on a weekly dashboard trains the reader to see noise. Match the refresh to the rate at which the number can actually move.
• Trace one figure end to end. Pick a tile and follow it back to source. If nobody in the room can do that in ten minutes, the trust problem will surface later, at the worst moment.

Where actuarial teams have the advantage

Data teams build the pipeline; actuarial teams know which movements are signal. Benefit usage, lapse behaviour and new business mix all have known relationships to value, and a report built by someone who understands those relationships will foreground different things — usually fewer things — than one built from the schema outward.