90-Day Federated Governance Proof of Value

Prove the operating model and consumer outcome before scaling

Days 0–30 — Baseline & Design

Select 1–2 meaningful Governance Domains. For the initial PoC / Proof of Value, consider Functional Unit as the starting type where the ownership policy assigns accountability by organisational function; if not, select the domain type that reflects the actual ownership boundary.

Agree central versus domain decision rights; identify the Sponsor, Governance Domain Owners, Data Product Owners, Stewards, Custodians and representative Consumers; select 5–15 priority Data Products; baseline Data Dave journeys; document current access and quality issues; define minimum metadata, role, access and measurement standards.

Days 31–60 — Establish

Configure the agreed domain structure and roles; register or scan agreed sources; establish relevant Data Products, assets, ownership, stewardship, glossary terms, Critical Data Elements (preview) where appropriate, classifications, lineage, Data Quality and access information where supported; create Guided Enablement and role checklists.

Days 61–90 — Test & Prove

Bring back the same consumer cohort; repeat comparable journeys; assess domain role adoption; compare discovery, understanding, ownership, trust, request, access and reuse; quantify evidenced benefits; capture lessons; present a scale/no-scale decision.

90-day exit criteria

• Priority consumer journeys show a measurable improvement or a clear explanation of why they did not.
• Governance Domain Owners, Product Owners and Stewards can perform their roles with documented guidance and realistic capacity.
• At least one material benefit is evidenced, not merely asserted.
• Known constraints, source limitations and integration gaps are documented.
• Federated decision rights and cross-domain escalation are understood.
• The operating model, costs and resource requirements for scale are understood.
• The Sponsor has evidence to approve, reshape or stop the next phase.

The 90-day decision

Not: “Did we configure Purview?”

Instead: “Did the federated operating model improve accountability and the consumer journey, reduce friction or risk, and create enough measurable value to scale?”

12–18 month roadmap

• 0–3 months — PROVE: pilot domains and decision rights, priority Data Products, baseline, consumer tests, initial role model and benefit evidence.
• 3–6 months — ESTABLISH: formal operating model, domain hierarchy, minimum standards, stewardship community, Guided Enablement, support, governance forums and review cadence.
• 6–12 months — SCALE: additional domains and products, cross-domain standards, CDEs (preview) where appropriate, more sources, DQ, lineage, governed access, metadata/API automation, wider adoption and reuse.
• 12–18 months — OPTIMISE: health management, business-OKR alignment, lifecycle controls, consumer behaviour analytics, cross-domain interoperability, automation, benefits realisation and mature governed self-service.