Data hygiene is the completeness, accuracy, and accessibility of the core data stores a business relies on. A red score on that dimension proposes the Data Hygiene Remediation Sprint for leadership to confirm. It measures duplicates, stale records, and field completeness, freezes new data silos, then cleans customer, revenue, and pipeline records in that order.
Why Data Hygiene Deserves a Defined Method
An owner may sense that records need attention, but a sense is not the same as a measurement. The Data Hygiene Remediation Sprint answers that gap with a defined trigger, owner, sequence, and outcome. It sits inside the Intelligent Foundations module as one of several remediation playbooks there.
The method does not start with a cleanup project chosen by instinct or frustration. It starts with a score, and the score decides whether leadership even considers the sprint. That order matters because the owner then acts on a measured reading rather than a general impression.
What follows walks through the full method in plain terms for a small business owner. It covers how the diagnostic scores the dimension, what fires the sprint, and what the sprint actually does. Later sections cover who owns the work, how long it runs, and how a run closes or escalates.
How the Diagnostic Scores Data Hygiene
The Intelligent Foundations Diagnostic scores 14 dimensions across three tools on a 0 to 5 scale. Those tools are the Vision Canvas, the Leadership DNA Radar, and the AI Readiness Index, called AERI. Scorers rate every dimension against written anchors, and every instrument scores in half points.
Data Hygiene is one of the five AERI dimensions, and it carries a weight of 0.10. The AERI block carries a weight of 0.40 inside the composite score. Each of the Vision Canvas and Leadership DNA blocks carries a weight of 0.30 in that same composite.
The dimension measures an audit of completeness, accuracy, and accessibility across core data stores. It also looks at duplicate rates, stale-record share, and access patterns inside those stores. Those inputs give the scorer evidence to place the business against the written anchors for the dimension.
Written anchors describe what each score looks like in practice for the business. At the low end, the anchor describes data that is incomplete, duplicated, and scattered across systems. At the high end, the anchor describes complete, accurate, and accessible data with continuous quality monitoring.
What Triggers the Sprint
The composite bands run on the same 0 to 5 weighted score with no gaps or overlaps. Red covers 0.0 up to but not including 2.0, and it proposes the owning remediation playbook. Amber covers 2.0 to 3.5 inclusive, and green covers above 3.5 up to and including 5.0.
A red Data Hygiene score proposes the Data Hygiene Remediation Sprint as the owning playbook. Because the route fires from a scored dimension, it stays a proposal until leadership confirms it. Confirmation happens at the next monthly governance review or the Core Execution Phase 3 review, whichever comes first.
The stated duration of the playbook starts at confirmation, not at the moment of scoring. That means the clock does not run before leadership has agreed to act on the proposal. The sprint therefore begins from a confirmed decision rather than from the raw score alone.
A color changes only when a score clears the band edge by a set margin. A color also changes when a score holds for two consecutive scorings on the same side.
An amber Data Hygiene score does not open the sprint at all under the module rules. Every amber dimension instead gets a 30-day pulse check that the COO runs. A green dimension holds, and the Core Execution quarterly cycle monitors it instead of a playbook.
What the Sprint Does First
The sprint first scopes the audit across the core data stores of the business. It then measures duplicate rate and stale-record share across those same stores. Those two measures, together with completeness, form the baseline that later work answers to.
Completeness covers the 10 fields that downstream modules depend on, according to the playbook. That choice ties the completeness measure to fields that other parts of the operating system rely on. The playbook names the count of fields, and the measure covers each one.
The sprint also freezes new data-silo creation across the business. That freeze stops new scattered stores from appearing while the team cleans existing stores.
The Remediation Order
Remediation runs in dependency order, and the playbook names that order. Customer records come first, revenue records come second, and pipeline records come third. The order is part of the method, so an owner should not reshuffle it to suit convenience.
Readers who know the theory of constraints may recognize a familiar idea in this sequence. That theory is an outside lens only, and it is not part of the playbook itself. The playbook simply states the dependency order and expects the team to follow it.
As remediation proceeds, the sprint installs weekly duplicate reports and monthly completeness reports. They give the business a recurring view of duplicates and completeness over time.
Ready for the Next Step?
The next guide on this site covers a closely related system: Building a Data-Driven Culture.
What Changes in Other Modules While It Runs
A red Data Hygiene score does more than propose this sprint inside the Intelligent Foundations module. While the sprint runs, the Integrated Tech Stack module prioritizes data centralization before any AI project. The KPI Precision Grid constrains its work to high-confidence data sources only during the same period.
The AI Deployment Canvas restricts machine learning model deployment for as long as the dimension stays red. Cyber, Data Privacy, and Security doubles its compliance audit frequency, which the playbook calls governance doubled. The SOP Codex also prioritizes data-related SOPs covering data entry, validation, and ownership.
These routes show why the owner should treat a red Data Hygiene score as a business priority. A single red reading reaches well beyond the database and into several other modules. Owners can see the full map of those modules in the VWCG OS framework that houses this playbook.
Owner, Duration, and Outcome
The playbook names the COO as owner, working with a data steward. Its stated duration is 6 weeks, counted from the point that leadership confirms the proposal. The playbook fixes both owner and duration, so the business does not invent its own.
The outcome has three parts, and the run succeeds only when it meets all three. Quality must show measured improvement against the baseline that the audit set at the start. Each core entity must have a named system of record, and the dimension must return amber or better at re-score.
The playbook requires that name for each core entity before the outcome counts as met.
How a Run Closes, Queues, or Escalates
Every playbook in the module follows one lifecycle: open, running, met or missed, escalated, closed. Any trigger that arrives while the sprint is already open goes into the log against that open run. That rule prevents a second sprint from starting on top of the first.
An outcome met, with an independent re-score at amber or better, closes the run. Someone other than the owner re-scores the dimension, so the COO does not grade the work. After closure, the owner’s next queued red playbook opens.
An outcome missed at the end of the stated duration escalates to the owner’s manager. It also goes onto the agenda for the next Core Execution quarter planning session. Each owner runs at most three red playbooks at once, and further reds wait in a queue.
How many modules the red dimension routes into sets the rank of each item in that queue. Data Hygiene routes into several modules, and that count sets its place in any queue. When the run meets its outcome, any standing duty the sprint set up continues under the standing playbook.
An Illustration for a Small Business Owner
Consider a small distribution business that keeps customers, invoices, and open deals in separate tools. Suppose its Data Hygiene dimension scores red, and leadership confirms the proposal at the monthly governance review. The 6-week clock for the sprint would start at that confirmation, not at the scoring.
Imagine the COO and a data steward scoping the audit across those three stores. They would measure duplicate rate, stale-record share, and completeness for the 10 named fields. Next, the pair would freeze any new spreadsheet or tool that could hold customer or revenue records.
The team would then clean customer records first, revenue records second, and pipeline records third. Weekly duplicate reports and monthly completeness reports could then keep that baseline in view. Someone other than the COO would re-score the dimension before the run could close.
This illustration describes the steps only, and it does not predict any particular result. The method defines what the team does and how leadership judges the outcome. Whether the run meets its outcome depends on the re-score, not on the effort alone.
Where the Sprint Fits in a Data Culture
Clean records are one input to a wider habit of deciding with evidence rather than instinct. Owners who want that wider context can read this guide to building a data-driven culture in a small business. That guide covers the cultural side that sits around this more structured remediation method.
The sprint itself stays narrow and measurable, and that narrow focus is deliberate. It scopes, measures, freezes, cleans in order, and installs reports that keep quality visible. An owner who follows those steps gives the business a fair test against the outcome the playbook defines.
Frequently Asked Questions
What does the Data Hygiene dimension measure?
The Data Hygiene dimension measures an audit of completeness, accuracy, and accessibility across core data stores. It also looks at duplicate rates, stale-record share, and access patterns. It is one of the five AERI dimensions, carries a weight of 0.10, and receives a score on a 0 to 5 scale against written anchors.
What triggers the Data Hygiene Remediation Sprint?
A red Data Hygiene score, from 0.0 up to but not including 2.0, proposes the sprint. Because the route fires from a scored dimension, leadership must confirm it first. Confirmation happens at the next monthly governance review or the Core Execution Phase 3 review, whichever comes first, and the stated duration starts there.
In what order does the sprint clean records?
Remediation runs in dependency order, as the playbook states it. Customer records come first, revenue records come second, and pipeline records come third. Before that work begins, the sprint scopes the audit, measures duplicates, stale records, and completeness for the 10 named fields, and freezes new data-silo creation across the business.
What reports does the sprint install?
The sprint installs weekly duplicate reports and monthly completeness reports as remediation proceeds. When the run meets its outcome, any standing duty the sprint set up continues under the standing playbook, which does not count toward the cap of three red playbooks per owner.
Who owns the sprint and how long does it run?
The COO owns the sprint, working with a data steward, and the stated duration is 6 weeks. The run closes when quality improves against baseline, each core entity has a named system of record, and an independent re-score lands at amber or better. A missed outcome escalates to the owner’s manager.
How does a small business owner begin data hygiene remediation?
A small business owner begins by working with World Consulting Group, which delivers this playbook through the VWCG OS service. The engagement starts from the Intelligent Foundations Diagnostic, which scores Data Hygiene alongside the other dimensions. A red reading then proposes the Data Hygiene Remediation Sprint for leadership to confirm before work starts.
