Business intelligence

Before You Buy Another BI Tool, Run This Readiness Check

We have seen a great many dashboards built. We have seen far fewer that anyone still opens three months later. The failure is almost never the tool.

Power BI, Tableau, Qlik and their competitors all work. When a business intelligence project fails, it is usually because the organisation was not ready, and no software resolves that.

Run these seven questions before you select a platform. Score each out of two: two if the answer is a clear yes, one if it is partial, zero if it is no.

1. Is there one agreed definition of your core metrics?

If sales, finance and operations calculate order intake differently, a dashboard will publish that disagreement at higher resolution and with greater authority. The argument does not go away. It simply acquires a chart.

Definitions are an organisational agreement, not a technical artefact. They have to be settled by people with the standing to settle them, before anything is built.

2. Does the source data exist, and is someone accountable for it?

Not whether the field exists in the system. Whether it is populated, on time, by somebody whose job depends on it being populated.

This is where most projects actually fail. The reporting layer is built correctly on top of a data layer that was never maintained, and the output is confidently wrong.

3. Can you name the decision each report supports?

A report that exists to provide visibility will not be used. Every view should answer a question that somebody has to act on, on a known cadence, with a known consequence for the answer.

If nobody can name the decision, the report is decoration.

4. Who is accountable when a number looks wrong?

There must be a named person. Without one, the first inconsistency destroys confidence in the entire system, and that confidence is very difficult to rebuild. People revert to their own spreadsheets quietly, and the project is dead months before anyone admits it.

5. Does existing reporting change what anyone does?

Take one report you already produce and ask what decision changed because of it in the last quarter. If the honest answer is none, adding more reports will not help. The problem is not information supply.

6. Is there a manual process the dashboard quietly replaces?

If the spreadsheet survives alongside the new system, the spreadsheet wins. It is faster, it is trusted, and its owner understands it.

Decide explicitly which one dies, and make somebody responsible for ensuring it does.

7. Is anyone's performance visible in it, including at the top?

Systems that measure only the front line get gamed, because the people being measured had no say in what is measured. Systems where leadership is also visible tend to get trusted, because the exercise reads as management rather than surveillance.

Reading your score

Twelve or above: you are ready, and the tool choice matters far less than the vendors will suggest. Pick one that fits your existing estate and move.

Seven to eleven: fix the gaps first. A short data discipline exercise will do more for you than a long implementation, and it costs a fraction.

Below seven: buying software now will cost you money and, more expensively, credibility for the next attempt. The organisation will conclude that business intelligence does not work here, and the next person to propose it will inherit that verdict.

The most common cause of a failed dashboard project is a successful dashboard project that nobody was ready to use.

Is this what you are working on?

Describe it and you will have a considered written response within one business day. No sales script, and an honest answer on whether we are the right firm for it.