Services
Nine services. Each one ends with an artifact your team keeps. The samples are on the site so you can see the shape before a call.
The program needs a place to live after the kickoff. We set decision rights, a forum, and the cadence that keeps issues from dying in email.
Strategy here is a sequence, not a poster. We start from the decisions that are currently being made on data people do not trust.
Quality work names the data set, the rule it should pass, how a break is found, and who closes it.
Policies are part of governance when people can tell what they are supposed to do. We connect them to the obligations you already carry.
A critical data set gets a business owner and a steward. The matrix shows who is accountable, who does the work, and who is consulted.
This is the modeling work from the original practice, pointed at governance. Terms the business argues about get one meaning, and the model shows where that meaning lives.
Dashboards stay. What changes is that each published metric points at a definition, an owner, and a quality rule. A report is not governed because it looks finished.
Integration is in scope when data moves between systems and the meaning has to survive the move. We document the source, the target, and the rule that must still be true after the load.
The original training offer remains. Sessions are built around the charter, the glossary, and the issue log your people will actually use.