Separate accountability for a business definition from stewardship, technical custody, and use; produce a decision-rights matrix and escalation path.
Sales and service publish different active-customer counts at month end. Each may be correct inside its own system, yet management needs to know who can approve the meaning of active when both numbers inform one decision. Data governance arranges decisions about meaning, use, accountability and evidence. It is more than buying a cleaning tool. Start with the decision affected by the data, identify who may approve the definition, who implements it, and who must be consulted. If an engineer repairs a query before the teams agree on the meaning of activity, the resulting report may be technically consistent and still mislead its reader.
Separate four functions. A business decision owner approves the meaning, intended use and acceptable exception. A data steward maintains definitions and rules, gathers evidence, and proposes resolutions, without treating a proposal as approved policy. A technical custodian operates the system and implements authorized changes. A data user explains the use and consequence and checks whether the output fits that use. These are functions in a sample operating model, not compulsory job titles. One person may perform several functions in a small team, but the approval authority should remain explicit. Where the conflict materially affects a decision, a change implementer should not silently approve their own altered business definition.
In a small decision-rights matrix, make each row a decision rather than a whole department: approve the definition of purchase-active for forecasting. Record one approving owner, the person gathering evidence, the person changing the system, and those consulted or informed. One approver is a design choice that resolves this case's conflicting approvals, not a universal legal rule. If the sales and service owners disagree, do not force one shared definition merely because a column has one name. The steward presents each definition's numerical effect and use to a small decision forum. The decision record states the date, version, approving owner and effect on older reports so historical figures do not change silently.
Review the resulting artifact with three practical questions. Can another user reproduce the count from a written definition? Can the decision maker see how the exception changes the figure? Is it clear who approved the change and who implements it? If any answer is no, a verbal agreement has not closed the work. A small decision log linking purpose, definition, owner, evidence and version is enough to begin. As asset count or impact grows, the escalation path may expand without turning every minor correction into an enterprise meeting. This lesson teaches a proportionate operating arrangement, not professional authorization or a legal requirement in any country.
Lesson summary
The affected decision owner approves an indicator's meaning; the steward gathers evidence and the custodian implements. A role matrix records exceptions and escalation before a filter changes.
