What the extra dashboard is for

When a marketing team asks for more data, I have stopped hearing a request for more data.

Not always. Sometimes the question genuinely cannot be answered with what is on the screen, and the honest thing is to go and get the number. But I have sat in enough of these meetings, on both sides of the table, to know the other version. The one where the number is already there. Where the answer is not in doubt and has not been for a fortnight. And the request goes in anyway, for one more cut, one more cohort, one more week of the test.

That request is not about information. It is about cover.

Nobody gets fired for waiting on data. People do get fired for deciding, and being wrong, and having done it without a report to stand behind. So the team asks for the report. Not because it will change the decision, but because it will change who is blamed if the decision goes badly. The dashboard is a witness.

I do not say this with contempt. Fear is rational when the organisation punishes error more than delay, and most of them do. The data request is a reading of the room, and the reading is usually correct.

But it is on no dashboard. Nothing in the reporting stack measures how much decision a team is willing to carry, and that number decides more outcomes than any of the ones being displayed.

So when the request comes in, I ask one thing before I go and build it. If this number comes back exactly as we expect, what will we do differently?

If the answer is nothing, we did not need data. We needed permission, and that is a different conversation.