Do we know what data we have, and what it means?

Eighteen statements in plain language, about five minutes. Score your organisation honestly. You will see whether people can find, understand and trust data, where it stalls, what that costs and which steps come first.

First: what matters most to your organisation right now?

Your result will be framed around this goal.

Steer

Does management see knowledge about data as something to organise?

We have an overview of our most important data: what it is and where it lives.
Management knows that knowledge about data now sits in people's heads, and sees that as a risk.
We know how much time people spend searching for data and asking what it means.
Someone is responsible for how we record and share knowledge about our data.
We have chosen for which data a good description pays off most.
With new systems and data deliveries, a description of the data is a fixed part.

Build

Is it agreed where and how we record what data means?

There is one place where people can look up which data we have.
The meaning of our most important terms is recorded, in the language of the business.
For important data it is recorded where it comes from and what was done to it on the way.
For important data it is recorded which rules it meets and how good the quality is.
For every important collection of data it is recorded who you can ask about it.
For data it is recorded who may use it and for what.

Run

Do people use the descriptions, and do they stay correct?

A new colleague can find out which data exists without asking around.
When someone sees a number in a report, they can look up exactly what it means.
Descriptions are updated when the data or the system changes.
Before we change a system, we can see which reports and processes it affects.
People reuse existing data instead of collecting or building it again.
When we share data with another department or party, the description travels with it.
0 / 18

I’d love to hear from you