Insights

The questions we get most about data quality, governance
and dashboards whose numbers hold, each with the answer
right there. Per topic you find the episodes, articles
and client cases together. 43 in total.

How do you improve data quality in your organisation?

Not by starting with a tool, but with a baseline: where do you stand now, per source and per definition. Then you record who owns which data and which standards apply. The Metro model splits that into a strategic, tactical and operational layer, so you know which measure belongs at which level.

11 episodes, articles and cases

What is data governance and how do you record ownership?

Data governance is not a control mechanism but an agreement about who owns what. Per data item you record who defines it, who maintains it and who may use it. Without metadata that stays abstract, which is why a catalogue is usually the first concrete step.

9 episodes, articles and cases

How do you build a data strategy that works in practice?

By tying it to goals that already exist, instead of writing a separate document. A data strategy that cannot be traced back to the business strategy stays on the shelf. Start small and visible, with a problem people already feel, and expand from there.

5 episodes, articles and cases

What does a Chief Data Officer actually do?

A CDO connects the ambition of the board with what happens daily in the processes. That is less a technical role than a change to carry through: assigning ownership, getting definitions agreed, and making sure the organisation keeps it up once the attention moves on.

5 episodes, articles and cases

How do you get your data in order before starting with AI?

AI only pays off on a solid data foundation. That means definitions that hold, data maintained structurally, and owners who feel responsible for it. Start small and visible rather than with a large programme, because a model on messy data mostly gives you wrong answers faster.

3 episodes, articles and cases

How do you build dashboards whose numbers actually hold?

By taking the business logic out of the report. Power BI should be purely the visualisation layer; definitions, data quality rules and calculations belong in the data layer underneath. If the logic sits in the report, every report builder makes their own version of revenue or margin, and the numbers drift apart by themselves.

10 episodes, articles and cases

Question not answered here?

Half an hour is enough to know whether we can help. No presentation.

Book half an hour
Basket