Insights on Data Governance, AI Governance, AI Products, Data Architecture, and Product Strategy. By Vikas Pratap Singh.
The industry is split: 36% centralized, 36% federated, 29% hybrid. Everyone talks about federated Data Governance. Nobody explains how to get there. Here is the migration playbook.
Only 11% of organizations report high Metadata Management maturity. Most Data Catalogs were purchased with good intentions and abandoned within a year. Here is the recovery path.
Data Contracts are technically simple but organizationally hard. The spec is documented. What is missing is how to introduce contracts into an organization that has never had them.
Appendix B of the Knowledge Graph Practitioner's Guide. Decomposes the trilogy cost-and-benefit roll-up from Part 11c into the dollar lines a CFO can defend. Covers per-layer cost decomposition (foundation, operational, governance, agent), license-versus-infrastructure-versus-headcount splits, the build-versus-buy decision per layer, the 24-month team curve from one ontologist to a 12-person multi-discipline platform, the role-by-role compensation reality (ontologist, knowledge engineer, graph platform engineer, entity resolution engineer, governance lead, AI engineer), what ROI looks like at steady state, six failure modes in KG cost modeling, an eight-question budget diagnostic, and a tiered Do Next table for the CFO, the CDO, and the procurement officer.
Most enterprise Data Governance has plateaued at a catalog plus a lineage tool plus a glossary plus a policy register, and four disconnected stores cannot answer the questions a regulator now asks. This article shows how a knowledge graph turns Data Lineage, Critical Data Elements, master data, and policy into one queryable substrate, with the OpenLineage-to-PROV-O bridge from Part 7 as the connective tissue. Worked patterns for BCBS 239, ECB RDARR attribute-level lineage, GDPR Article 30, and EU AI Act Article 10. Part 10 of the Knowledge Graph Practitioner's Guide.
Identity is the load-bearing decision in a knowledge graph. IRIs are identifiers, not URLs. owl:sameAs is not as simple as it looks. Entity resolution is not optional. Inference is what turns stored facts into knowledge, and the choice between forward chaining (materialization) and backward chaining (query rewriting) is the second-most expensive design call after identity. This article gives the working design rules for all three and the W3C reasoning profiles (OWL 2 EL, QL, RL) that production KGs actually pick. Part 5 of the Knowledge Graph Practitioner's Guide.
Essays on thinking clearly, living intentionally, and building a career worth having.
Most people stop at the first consequence. The best decision-makers ask 'and then what?' repeatedly. A practical guide to second-order thinking for career, technology, and life decisions.
You can ignore truth, argue with it, or replace it with a more comforting story. None of that makes it disappear. Reality is patient. And when truth returns after a long period of avoidance, it rarely arrives as information. It arrives as correction.
Current AI can assist with routine cognitive work, but accountable judgment, creative synthesis, and sustained concentration remain human strengths. Deep work is now the scarcest, most valuable skill a knowledge worker can build.
Get new articles on data governance, AI, and engineering delivered to your inbox.
No spam. Unsubscribe anytime.