Build Governance Bundle
When to Use
- User needs a full governance package, not a single artifact.
- Domain governance must be replicated from a reference pattern.
- Artifacts must stay consistent in scope, terms, roles, and metrics.
Orchestration Order
- Apply
question-driven-data-projectsto anchor work on business questions and decision value. - Apply
data-management-foundationsto set DMBOK context and boundaries. - Apply
data-governanceto define operating framework and decision rights. - Apply
governance-writing-style-guide. - Draft core governance flow with
process-and-procedure-writing. - Draft controls-level steps with
sop-writing. - Draft decision-level narrative with
executive-summary-writing. - Build terminology base with
business-glossary-management. - Define KPI governance with
metric-governance. - Define trust controls with
data-quality-controls. - Score current data quality and prioritize defects with
data-quality-assessment. - Capture traceability using
metadata-and-lineage. - Create leadership narrative structure with
governance-ppt-deck-writing.
Required Inputs
- Domain name
- Business function
- Governance objective
- Primary audience
- Reference pattern or source material
- Required outputs
- Known metrics
- Known systems
- Known roles
- Known risks/issues
- Governance maturity level
- Tone
Bundle Outputs
- Executive summary
- Governance policy or addendum
- High-level governance process
- Detailed SOP
- RACI / roles and responsibilities
- Business glossary
- Metric definitions
- Data quality rules
- Data quality assessment
- Metadata and lineage template
- Issue management procedure
- Adoption/training notes
- PPT deck outline or draft
- Version history/change log
Output Template
# Governance Bundle: [Domain]
## 0) Bundle Inputs
- Domain:
- Business function:
- Objective:
- Audience:
- Maturity:
## 1) Executive Summary
...
## 2) Policy or Policy Addendum
...
## 3) High-Level Governance Process
...
## 4) Standard Operating Procedure
...
## 5) RACI
...
## 6) Business Glossary
...
## 7) Metric Definitions
...
## 8) Data Quality Rules
...
## 9) Data Quality Assessment
...
## 10) Metadata and Lineage
...
## 11) Issue Management
...
## 12) Adoption and Training Notes
...
## 13) Deck Outline
...
## 14) Version History
...
Quality Checklist
- All artifacts align to the same purpose and scope.
- Terms are consistent with the glossary.
- Metrics and controls are consistent across policy/process/SOP/deck.
- Ownership is explicit for each control and action.
- Decision asks are clear for executive audiences.
- Governance choices are traceable to DMBOK-aligned activities and maturity goals.
- Initial business questions and stage-gate decisions are traceable through every artifact.