Data readiness is decided per use case, not per company

A company-wide data readiness score tells a CTO almost nothing about what to fix first. The same table can be ready for one tool and useless for the next. We check readiness per use case, and the checks turn into a short data backlog instead of a data programme.

Stojan VeličkovićPractice Lead for Cloud, Software and Data PlatformsPublished 21 October 2026 · 2 min read · Cross-industry

01

Why the company score misleads

—

It averages what should not be averaged.Policy documents can be in good shape while sensor history is full of gaps. One number hides both.

—

It sends money to the biggest gap,not to the gap in front of the most valuable use case.

—

It goes stalethe day the next system lands or the next team changes a process.

02

The check, per use case

QuestionWhat we look atReady when
Where does the data live?The systems, exports and inboxes the use case needsEvery source is named and reachable by API or a scheduled export
Who owns it?A named person per sourceThey can say which version is right when two disagree
How current is it?How often it changes against how often it updatesIt updates at least as often as the decision is made
Who may see it?Permissions, residency, consentThe tool can respect the same permissions as the people using it
Is it right?100 real records checked by hand with the ownerThe error rate is below what the owner agrees the use case can carry

03

The bar rises with the level of build

LevelWhat the data needsWho catches a wrong answer
1 · The subscription as boughtWhatever a person pastes inThe person, every time
2 · The configured subscriptionCurrent documents, permissions set, one owner per domainThe person reading the answer
3 · The No-Code TrackOne or two clean sources for one decisionThe team member who built it
4 · The Custom Build TrackSeveral sources reconciled, tested and monitoredOften nobody, so the system has to be right

04

From gaps to a backlog

Every failed check becomes a prerequisite with an owner, an estimate and the use cases it unblocks. Sort by the value it unblocks: a fix that serves three use cases goes before a fix that serves one. That list is the readiness plan, and every item on it has a use case waiting.

05

What a platform lead should push back on

—

"Clean all the data first."It never ends, and nobody can say when it is done.

—

"Buy a catalogue before choosing a use case."A catalogue of data nobody uses yet is a second backlog.

—

"The model will cope with messy data."At Level 4 it acts on that data, often before anyone checks.

The question to ask every time is "ready for what?". Related on the site: the pillar, The four levels of building AI systems, and the Find step page.

Practice Notes · for CTOs and tech leadsMore in Insights →

Ask how this applies to your own stack.

Schedule a call with a partnerFree until 11 December