Assessment

Data Readiness Assessment

Eight questions on whether your data estate can support serious commitments: ownership, quality, access, integration, reporting trust, governance, skills and whether data actually reaches decisions.

Analytics programmes, AI initiatives and system migrations all stand on the same floor: the data estate. This assessment scores whether that floor bears weight, before you find out by loading it. Eight questions, fixed scoring, in-browser.

Last reviewed 3 July 2026 · Free and ungated

Pressure-test this decision

The initiative your data estate will carry is easier to challenge before it is funded than after it is live. Selected senior operators from the Global Board provide that challenge in a confidential report.

Pressure-test this decision

How a client brief works · What you receive

Fixed questions · no AI · nothing stored

Run the scorecard

Answer for the data domains your next major initiative actually depends on, not for the estate in general.

0–39 Low maturity 40–59 Developing maturity 60–79 Moderate maturity 80–100 Stronger maturity How our tools are scored
  1. Data ownership Do critical data domains have accountable owners?
    • Data belongs to whichever system it sits in; owners exist only on slides
    • Owners are named for key domains but have no time or authority
    • Critical domains have owners who fix issues and answer for quality
  2. Data quality Is quality measured, or discovered at the point of use?
    • Quality problems surface when a report is wrong in front of the board
    • Known issues are documented; systematic measurement is patchy
    • Quality is measured against defined rules, with trends tracked and worked
  3. Access control Is access to sensitive data deliberate and auditable?
    • Access accumulates over careers and extracts circulate by email
    • Controls exist on the crown jewels; the rest is informally shared
    • Access is role-based, reviewed periodically and auditable end to end
  4. Integration readiness Can data move between systems without heroics?
    • Every new connection is a bespoke project with its own surprises
    • Core pipelines work but were built by people who have since left
    • Documented, supported interfaces exist for the systems that matter
  5. Reporting trust Do leaders trust the numbers enough to argue about the business instead?
    • Meetings begin with duelling versions of the same figure
    • Headline numbers are agreed; drill-downs still spark reconciliation wars
    • One agreed source exists for key figures, and disputes are about meaning
  6. Governance cadence Is data governance a working rhythm or a written policy?
    • A governance framework was approved once and has not met since
    • Governance meets but decisions stall for lack of authority or teeth
    • A regular cadence makes decisions on standards and issues, and they stick
  7. Skills coverage Does capability extend beyond a small central team?
    • Data capability is two irreplaceable people and a backlog
    • A capable central team exists; the business waits in its queue
    • Data skills are distributed, with the central team setting standards
  8. Decision usage Does data actually change decisions, or arrive after them?
    • Analysis is commissioned to justify choices already made
    • Data informs operational calls; strategic ones run on seniority
    • Major decisions wait for the analysis, and the analysis has changed them
Reading the score

What the result bands mean

0–39: Low maturity

The estate cannot yet bear the initiatives being planned on top of it. Anything ambitious (AI, advanced analytics, a migration) will spend most of its budget rediscovering these gaps under a deadline, which is the most expensive way to find them. Unlike a culture problem, this one is concrete and fixable.

40–59: Developing maturity

Foundations are being laid but unevenly: typically decent pipelines and tooling with soft ownership and governance that meets without deciding. Initiatives succeed here when a strong team drags them through, which reads as capability but is actually dependence on heroics.

60–79: Moderate maturity

The estate is genuinely serviceable: owned domains, measured quality, numbers leaders mostly trust. The residual risks are concentration (skills and knowledge in a few heads) and the gap between operational data discipline and strategic decision usage, which is usually the last thing to mature.

80–100: Stronger maturity

These answers describe a data estate run as infrastructure: owned, measured, governed and actually used. The remaining exposure is subtle: trust. When numbers are believed by default, an error propagates further before anyone questions it, and models built on the estate inherit its blind spots invisibly.

Why readiness, not maturity theatre

Data programmes attract frameworks the way transformations attract consultancies, and both can run for years without anyone asking the operative question: will this estate carry the specific weight we intend to put on it next? The eight questions here are scoped to that question, which is why the assessment asks you to answer for the domains your next initiative touches, not the estate at large.

How scoring works

Every question has three answers worth 0, 5 or 10 points; the total is expressed out of 100 and lands in one of four bands. Repeatable, in your browser, no interpretation layer. Re-run it when remediation claims to have finished, and let the movement arbitrate.

The two questions that predict the rest

In practice, data ownership and reporting trust are the leading indicators. Where domains have real owners, quality and governance tend to follow within a few cycles; where leaders bring rival versions of the same number to meetings, every downstream ambition gets discounted. If you only have time to fix two answers, fix those.

Common profiles and what they mean

  • Strong tooling, weak ownership: an estate built by a capable team that the business never took delivery of. Expect decay when that team turns over.
  • Strong access control, weak decision usage: a locked archive. Secure, compliant and commercially inert.
  • Strong decision usage, weak quality measurement: leadership is trusting numbers nobody is checking, the most dangerous profile on the list.

Frequently asked questions

Should we complete this before an AI initiative specifically?

Yes, and answer for the exact data the use case consumes. AI initiatives inherit every weakness in their training and input data, and the data-quality and ownership questions here are where most of them are actually decided.

What is a realistic score for a mid-sized organisation?

Most land in the developing band, and that is workable: readiness only needs to match ambition. A 45 with a modest analytics roadmap is fine; a 45 underneath an enterprise AI programme is a funded incident.

Data quality feels subjective. How do we answer honestly?

Use the operational test in the options: where do quality problems surface? If the answer is "in front of an executive, via a wrong number", score low regardless of what the quality tooling claims. The point of discovery is the measure.

The estate is measurable. The decision built on it still needs challenge.

Pressure-test this decision