Skip to content

Reconstruction Key & Repair Protocol

Use after retrieval, not before.

Rapid-recall reconstruction key

R1–R18

  • R1: authority/control over data assets: planning, implementation, monitoring, enforcement.
  • R2: strategy, policy, standards, oversight, compliance, issue management, DM projects, data-asset valuation.
  • R3: reduce risk + improve processes.
  • R4: DG = data assets; ITG = IT investments, application/project portfolios, technical architecture.
  • R5: Sustainable, Embedded, Measured.
  • R6: Leadership/strategy; Business-driven; Shared responsibility; Multi-layered; Framework-based; Principle-based.
  • R7: DG ensures/oversees; Data Management executes.
  • R8: Centralized, Replicated, Federated.
  • R9: core Metadata; rules/standards; DQ issue management; operational adherence.
  • R10: Owner = final business-domain decision accountability; Business Steward = SME defining/controlling subset.
  • R11: Policy = what/what not; Standard = measurable conformance; Procedure = steps/method.
  • R12: replacement, market, opportunity, sale/packaging, risk cost — any four.
  • R13: DM maturity, capacity to change, collaborative readiness, business alignment.
  • R14: practices/issues/risks/benefits + governance requirements tied to value.
  • R15: procurement/contracts, budget/funding, compliance, SDLC/development — plus DQ/Architecture as relevant.
  • R16: Charter, Operating Framework/Accountabilities, Roadmap, Operational-Success Plan.
  • R17: data value, business model, culture, regulation — any four source-supported factors.
  • R18: Awareness, Desire, Knowledge, Ability, Reinforcement.

R19–R36

  • R19: most issues resolve at stewardship/business-unit tactical/operational level; progressively fewer escalate.
  • R20: capture/log/track; action items; viewpoints/options; communicate resolution; neutral facilitation; escalation.
  • R21: authoritative measurable rule supporting consistency; auditable/enforceable.
  • R22: Business Data Stewards generally steward glossary content.
  • R23: glossary terms can carry synonyms, metrics, lineage/context, classification, rules, steward/owner and other Metadata.
  • R24: online presence, Business Glossary, workflow, document management, scorecards.
  • R25: Governance is organizational behavior/authority; requirements should drive tools.
  • R26: what is governed, who is governed, who governs, enterprise scope.
  • R27: maturity/change/collaboration/alignment; determine adoption readiness.
  • R28: current practices/issues/risks/benefits → requirements/business value.
  • R29: integrate Governance with normal enterprise processes rather than isolate it.
  • R30: Charter, Framework, Roadmap, Operational Success.
  • R31: structures, roles, decision rights, interactions, issue pathways fitted to context.
  • R32: communicate, monitor, enforce and re-evaluate guidance.
  • R33: sponsor/business-case/coordinate significant data projects and requirements; not execute them all.
  • R34: sponsorship, stakeholders, training, process integration, feedback, incentives/KPIs and reinforcement.
  • R35: identify, quantify, prioritize, resolve, log, track, communicate, facilitate and escalate governance issues.
  • R36: applicability, compliance meaning, required controls/policies, evidence/monitoring, penalties/risk, reporting/remediation.

R37–R54

  • R37: execute roadmap incrementally; establish foundational capabilities fitted to maturity/priority.
  • R38: communicate, monitor/audit, review/update and enforce standards/procedures.
  • R39: steward shared terminology + rich Metadata/context.
  • R40: stewards + architects align structures/meaning; DGC can review/adopt key artifacts.
  • R41: establish consistent organizational valuation method; no universal formula.
  • R42: ongoing funded, monitored, measured, accepted Governance function.
  • R43: data asset vs technology investment/application/project portfolio.
  • R44: Steering = highest authority/support/funding.
  • R45: DGC = governance initiatives/policies/metrics/issues/escalations.
  • R46: DGO = ongoing definitions/standards/role/program coordination.
  • R47: Stewardship Team = subject-area/project collaboration.
  • R48: Chief Steward = high-level/possible chair/virtual CDO role depending model.
  • R49: Executive Steward = senior manager on DGC.
  • R50: Enterprise Steward = domain oversight across functions.
  • R51: Coordinating Steward = leads/represents steward teams.
  • R52: policies few/brief/direct; detailed rules/steps belong in standards/procedures.
  • R53: Standard = authoritative measurable conformance rule; mandatory/enforceable.
  • R54: Procedure = documented methods/techniques/steps.

R55–R70

  • R55: Business Data Stewards; terms may carry synonyms, metrics, lineage/context, classification, rules, steward/owner Metadata.
  • R56: Glossary = business terminology/context; Enterprise Data Model = structures/relationships; coordinate, don't substitute.
  • R57: contract clauses/data rights for cloud, outsourcing, purchase/sale/licensing, retention/vendor handling.
  • R58: reduce duplicate data acquisition and optimize shared data-asset investment.
  • R59: policies/standards, architecture, DQ, SOR and regulatory requirements early in planning/design.
  • R60: data value, business model, culture, regulatory environment — among context factors.
  • R61: Charter WHY; Framework WHO/HOW; Roadmap WHEN; Operational Success HOW IT ENDURES.
  • R62: Figure 16 is generic/adaptable, not mandatory org chart.
  • R63: operating models are alternatives fitted to context, not maturity stages.
  • R64: narrow upward: most issues resolve low; progressively fewer reach senior governance.
  • R65: log/track; actions; viewpoints/options; resolution communication; facilitation; escalation.
  • R66: applicability/meaning, controls/evidence/monitoring, penalties/risk, reporting/remediation.
  • R67: website, glossary, workflow, document management, scorecards; tools support, never replace authority/accountability.
  • R68: scorecard reports governance activity/performance/policy compliance; cannot replace governance authority.
  • R69: maturity, engagement, funding and priorities vary; rollout should be incremental/tailored.
  • R70: Community of Interest can build awareness/collaboration/vocabulary/evidence; it lacks formal decision rights unless explicitly granted.

Classification key

C1 Steering Committee · C2 DGC · C3 DGO · C4 Business Data Steward · C5 Data Owner · C6 Centralized · C7 Replicated · C8 Federated · C9 Policy · C10 Standard · C11 Procedure · C12 Collaborative readiness · C13 Discovery/Business Alignment · C14 Operating Framework · C15 Implementation Roadmap · C16 Escalate to Steering Committee.

Changed-fact key

  1. Federated — new central coordination is decisive.
  2. Data Owner — final business decision accountability is now the role clue.
  3. Standard — mandatory measurable rule, no procedural steps.
  4. Discovery/Business Alignment — focus moved to current problem/risk/business benefit.
  5. No — resolve at the lowest appropriate level; escalate only when necessary.
  6. Governance authority/accountability/operating framework — tooling cannot supply decision rights.

Repair protocol

  • Role confusion: redraw body/role matrix; classify two new examples.
  • Operating-model confusion: draw all three; underline the coordination clue.
  • Artifact confusion: rebuild Charter vs Framework vs Roadmap, then Policy vs Standard vs Procedure.
  • Activity confusion: return to the 17-activity recognition map; state one purpose sentence per activity.
  • Figure confusion: explain the relationship the figure teaches rather than memorizing geometry.
  • Confident miss: mark for spaced retesting because confidence without accuracy can hide a durable misconception.

Source boundary: DAMA-DMBOK2 Revised, Chapter 3, pp. 69–98.

← Blank-page drills · Chapter 3 home