DataGovernance.ca editorial · 13 October 2026 · Implementation guidance
Days 1–30: choose the decision
Do not begin by asking every team to catalogue every field. Choose a decision that matters: a revenue report, a customer handoff or an AI pilot. Name the sponsor and the domain owner. Write down what a useful improvement would look like and what is outside the pilot. Interview the people who create, transform and use the information. Keep an evidence register that separates observed facts, stakeholder descriptions and unknowns. The first output should be a small map, not a large policy library.
Days 31–60: put one control into use
Choose an issue from the baseline and agree how it will be handled. That might mean a definition approval process, an access review or a quality check with a named responder. Document the trigger, owner, evidence and escalation path. Run it against an approved sample or real workflow with the necessary permissions. Record what did not work: missing authority, unavailable metadata, unclear terms or a dependency on another team. Revise the design rather than pretending the first draft is the operating model.
Days 61–90: prove the routine can continue
Run a second cycle with the internal owner leading it. Review whether the inventory changed, whether issues reached decisions and whether evidence was recorded. Ask what happens when the owner is away or the system changes. The sponsor should decide which improvements continue, which gaps need a separate project and whether another domain is ready. Do not describe completion of a pilot as organisation-wide governance maturity.
Define success before counting activity
A useful pilot may produce fewer meetings, not more. Prefer evidence such as a metric with an agreed definition and source, an issue closed by the right authority or a tested access-review process. Count completed decisions and maintained controls—not simply policies written. Timelines are planning examples and depend on access, scope and client participation.
Rehearse the first decision before expanding the programme.
Choose a fictional pilot domain and complete a one-page mandate. Name the first decision, its owner and the evidence needed. Walk that decision through one review cycle, then let an internal role lead the next cycle. Carry unresolved dependencies into the roadmap rather than turning dates into promises.
The record should identify the scope, owner, evidence, unresolved questions and next review. It is a draft exercise—not evidence that your organisation has implemented or passed the control.