Governance purpose and decisions

Review questions

Integrated summary: Governance purpose and decisions

Data governance begins with the decision being served, not the name of a committee or tool. When teams disagree about 'completed order,' the steward assembles affected-record evidence and proposes a rule, and the custodian tests implementation effects, but the planning decision owner approves the indicator's meaning. A bounded charter states data domain, roles, authority, escalation and review cadence. A field is not critical merely because someone labels it so; identify its use. Technical permission to edit a query does not resolve a definition dispute. For conflicting consumers, show alternatives, consequences and missing evidence, then record who approved the version in use. A provisional figure may be contained and published with its population and uncertainty visible. Temporary containment is not proof that the originating defect has been repaired.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

  1. Question 1A steward documents two meanings of completed; a custodian can change the filter. Who approves the meaning used for staffing?
  2. Question 2UI color is missing in 40 orders; destination code is missing in five and blocks tomorrow's dispatch. Which element is critical to this decision?
  3. Question 3A charter says issues are reviewed monthly but names no definition owner or dispute route. What should be repaired first?
  4. Question 4Twelve records remain unresolved before a capacity dashboard release, and a purchase decision is due tomorrow. Which path balances speed and confidence?