A reference to the same domains explored in the tour. Open a domain to read its purpose and examples of supporting evidence.
D1 · Data Value & Alignment
Start with the decision or service you want to improve. Connect data work to that outcome so effort goes where it matters.
Evidence to look for: A use-case register, agreed business definitions and success measures.
D2 · Data Ownership & Stewardship
Assign owners with decision-making authority and stewards who can resolve day-to-day issues. Everyone should know where to take a problem.
Evidence to look for: Named owners, responsibility records and an issue-escalation process.
D3 · Core Data Quality
Check accuracy, completeness, consistency and the other quality characteristics against the needs of the use case. A quality threshold needs a reason and evidence.
Evidence to look for: Quality rules, test results and a record of how failed checks were resolved.
D4 · Pipeline Quality & Operations
Ingestion, transformation and delivery can introduce errors. Make those steps observable and controlled so failures are detected and handled.
Evidence to look for: Pipeline tests, monitoring records, change approvals and incident runbooks.
D5 · AI Readiness & Provenance
Know where training and input data came from, how it changed and whether it is suitable. Consider bias, drift and the link between a model and its data.
Evidence to look for: Data provenance, version records, bias checks and input-validation results.
D6 · Governance & Compliance
Turn governance expectations into rules, responsibilities and records. Make it possible to trace a decision back to the policy and evidence that informed it.
Evidence to look for: Approved policies, control records, lineage and an audit trail.
D7 · Security & Privacy
Control access, protect sensitive information and prepare for incidents. Include threats specific to AI as well as familiar security and privacy risks.
Evidence to look for: Access reviews, security tests, privacy assessments and incident-response records.
D8 · Tooling & Technology
Choose and connect tools that support the controls you need. The test is whether teams can use them to operate and evidence governance consistently.
Evidence to look for: Tool inventories, integration records, automation coverage and usability feedback.
D9 · Transparency & Access
Make ownership, quality, access conditions and limitations visible. People need enough context to judge whether data or an AI output is suitable.
Evidence to look for: Catalogue entries, quality reports, output guidance and change communications.
D10 · Lifecycle & Retention
Manage information from creation through retention, archival and disposal. Keep a reason for retaining it and a controlled way to retire it.
Evidence to look for: Retention schedules, deletion records, archival tests and retirement approvals.
D11 · Organisational Readiness
Governance depends on skills, leadership and everyday behaviour. Give people the understanding, support and authority their roles require.
Evidence to look for: Role-based training, leadership sponsorship, adoption feedback and a maturity roadmap.
D12 · Sustainable & Maintainable
Keep documentation, versions, knowledge and improvement work under control. Governance needs to survive staff changes and evolving systems.
Evidence to look for: Version history, current runbooks, knowledge-transfer records and an improvement backlog.