Data Governance
Design data governance frameworks: catalog architecture, ownership models, data classification, retention policies, and privacy compliance implementation for data platforms.
Guiding Principle
"Data governance is not bureaucracy — it is the engineering discipline of treating data as a product with owners, contracts, and quality guarantees."
Procedure
Step 1 — Data Catalog & Discovery
- Inventory all data assets: databases, tables, files, APIs, streams
- Design catalog metadata schema: technical, business, operational metadata
- Implement automated discovery and metadata extraction pipelines
- Define tagging taxonomy: domain, sensitivity, PII classification, freshness
- Build search and discovery interfaces for data consumers
Step 2 — Ownership & Stewardship
- Define data ownership model: domain-oriented (data mesh) vs. centralized
- Assign data owners per domain with clear accountability scope
- Define data steward roles and responsibilities (quality, access, documentation)
- Implement ownership metadata in the data catalog
- Establish governance council cadence and decision-making process
Step 3 — Classification & Access Control
- Define data classification tiers: public, internal, confidential, restricted
- Implement automated PII detection and classification scanning
- Design access control model: role-based, attribute-based, or purpose-based
- Implement data masking and anonymization for non-production environments
- Build access request and approval workflows with audit trails
Step 4 — Retention & Privacy Compliance
- Define retention policies per data classification and regulatory requirement
- Implement automated data lifecycle management: archival, deletion, legal holds
- Map data processing activities to privacy regulations (GDPR, CCPA, LGPD)
- Implement data subject rights: access, deletion, portability, correction
- Build compliance dashboards with control effectiveness metrics
Quality Criteria
- Every data asset in the catalog has an assigned owner and classification
- PII detection covers >95% of data stores with automated scanning
- Retention policies enforced automatically with deletion audit trails
- Access control changes are auditable with approval workflows
Anti-Patterns
- Data governance as a documentation exercise without enforcement automation
- Centralized data team as bottleneck for all data access requests
- Classification done once and never updated as data evolves
- Privacy compliance treated as legal checkbox rather than engineering system