Most dashboards are data pretending to be information. The two aren’t the same thing, and the gap between them is where most workforce reporting quietly fails.

Data is what you gather. Attendance figures, completion rates, sickness absence, incident logs, and survey scores. It’s raw and just sits in a spreadsheet or system, doing nothing on its own. Collecting more of it doesn’t make you better informed, simply better stocked.

Information is what happens when a person applies cognition to that data: context, comparison, judgement, and a question worth asking. A completion rate becomes information only when someone asks what it means, against what baseline, for whom, and so what. If you skip that step, you end up with a number, not an answer.

Most organisations invest heavily in the gathering and much less in the cognition. Build the reporting suite, populate the dashboard and circulate it monthly, and many people will tick the box marked complete. Except nobody’s asked what the numbers mean, and nobody’s positioned to ask, because the system was built to produce data, not to prompt thinking.

I see these issues constantly in workforce reporting. Sickness absence by directorate, mandatory training compliance by team, and exit interview themes by department. All present, all correct, but inconsistently interrogated. The report gets sent, the meeting nods at it, and the same pattern repeats next quarter, because a number sitting in a slide isn’t the same as someone asking why it’s that number and not another.

The fix isn’t more data but building the cognitive step back into the process deliberately: who reads this, what question are they meant to ask of it, and what decision does the answer change? If a report doesn’t change a decision, it’s data doing information’s job badly.

Before you commission another dashboard, are you building a way to gather more or a way to think harder about what you’ve already got?