# Why Governance Before Schema Is a Costly Mistake

A one-page memo for clients who want to start with governance instead of foundational dimensions.

Apache 2.0. Rebrand with your firm's logo. Designed as a leave-behind when a client pushes back on the recommended intervention sequence.

---

## The Pattern

Organizations frequently want to start with governance. The reasoning is understandable: governance is what the board asks about, what regulators examine, and what executives report on. It feels like the highest-priority item.

The Maturity Map assessment revealed that your foundational dimensions - Schema Integrity, Constraint Enforcement, and Semantic Identity - are below Level 3. The floor constraint principle means that no derived dimension, including Governance, can function above the minimum of those three foundational scores.

## What Happens When You Deploy Governance First

**Governance over unstable schemas produces audit findings, not audit confidence.**

When governance rules are deployed over data that lacks structural integrity:

- Governance rules reference field names that change without notice, producing false violations
- Audit trails record events against identifiers that mean different things in different systems
- Compliance reports aggregate data that was never validated at write time, producing numbers that are technically "governed" but structurally meaningless
- Every schema change triggers a governance review cycle that consumes practitioner and stakeholder time without improving data quality

The result is a governance program that generates documentation and consumes budget without producing trust in the underlying data. The board sees "governance in place." The engineers see "governance that breaks every time someone adds a column."

## What Changes When You Fix the Foundation First

When Schema Integrity and Constraint Enforcement reach Level 3 before governance is deployed:

- Governance rules reference stable, versioned schema definitions that do not change without controlled review
- Audit trails record events against identifiers that resolve to the same entity across all systems
- Compliance reports aggregate data that was validated at write time - the numbers are structurally sound
- Schema changes are governed by the same framework, not by a separate process

**The governance work you want to do is correct. The sequence determines whether it produces real enforcement or expensive documentation.**

## The Recommended Path

1. **Schema Integrity to Level 3** (4-6 weeks) - stable, versioned, enforced at write time
2. **Constraint Enforcement to Level 3** (4-6 weeks) - validation rules travel with the data
3. **Semantic Identity to Level 3** (2-4 weeks) - stable identifiers across all systems
4. **Governance deployment** (6-8 weeks) - now operating on a structural foundation that makes the governance enforceable

The total timeline is comparable. The difference is that the governance deployed in step 4 actually works.

---

**[Your name]**
SDC Certified Practitioner
[Your firm name]

---

*SDC Certified Practitioner Template. Apache 2.0. Customize with your firm's branding.*