Organizational Data Flow Architecture: Now a White Paper
by DL Keeshin
February 18, 2026
Over the past several weeks, this blog has served as a laboratory for ideas that I believe represent something genuinely new in enterprise data management. In my January 26th post, I introduced the Organizational Data Flow Architecture approach—the insight that mapping data flows to organizational structure reveals not just what data exists, but why it exists, what it means to the business, and what problems it is designed to solve. Then in my February 11th post, I explored the deeper dynamic underlying all of this: the bidirectional relationship between organizational structure and data quality, and how each shapes and constrains the other in ways that can either reinforce excellence or entrench dysfunction.
Those two posts generated more reader engagement than anything I've written here, and the conversations they sparked—including a particularly sharp exchange about how chart-of-accounts conventions can fossilize outdated organizational decisions into financial data—made clear that the ideas deserved a more formal treatment.
Today I'm pleased to announce that both posts, along with that subsequent thinking, have been synthesized into a formal white paper: Organizational Data Flow Architecture: A New Approach to Enterprise Data Management.
Read the White Paper
The complete Organizational Data Flow Architecture white paper — including the Newco Foods real-world example, stakeholder perspectives, and the full structural analysis — is now available.
Organizational Data Flow Architecture →What the White Paper Covers
For those who've followed the blog posts, the white paper brings everything together into a single, structured argument. Here's a brief summary of each section:
The Discovery: A Missing Approach
After extensive research, I found that no established approach maps complete data flow topology to organizational structure in a way that captures business meaning. Data Flow Diagrams, lineage tools like Collibra and Alation, RACI matrices, and IBM's Data Topology Framework each address pieces of the problem—but none answer the question enterprises most need answered: why does this data exist and what problem does it solve?
The Core Insight: Data Reflects Organizational Reality
Organizational architecture functions as a Rosetta Stone for data. When you map data flows to the four-level hierarchy—Parent Company, Subsidiary/Legal Entity, Division/Business Unit, Role—each level reveals distinct business context, legal implications, and accountability structures that purely technical tools cannot surface.
Organizational Structure and Data Quality: A Bidirectional Relationship New
This is the section most directly informed by the February 11th post and subsequent reader discussion. Structure drives data quality through governance model choices, silo fragmentation, and accountability gaps. But data quality also shapes structure—poor data spawns shadow systems that become permanent infrastructure, while excellent data enables flatter, more autonomous organizations. The accounting convention case is explored in detail: a chart of accounts is a financial fossil record of past organizational decisions, and when companies resist restructuring to avoid disrupting it, they produce data that passes every validation rule yet misleads every executive reading the report.
A Real-World Example: Newco Foods
The white paper walks through a concrete food manufacturing scenario—three subsidiaries, multiple business units, production quality data flowing through the entire hierarchy. The same data flow looks completely different depending on which level of the organizational architecture you're examining, and the business meaning at each level is invisible to traditional lineage tools.
From Syntactic to Semantic Understanding
Traditional data lineage is syntactic: "Table A joins Table B to create View C." ODFA lineage is semantic: here's why that join exists, which legal boundary it crosses, who depends on it, and what would break if it changed. This distinction is the foundation of the platform's value for compliance, M&A due diligence, and audit readiness.
A New Category in Enterprise Data Management
The white paper makes the case that ODFA represents a genuinely new category—one that speaks the language of business rather than technology, and that addresses the gap between what existing governance tools provide and what enterprise organizations actually need.
An Approach in Progress
I want to be direct about something. The white paper presents ODFA as an approach being proven out, not a finished product. The kDS BETA program exists precisely to test these ideas against real enterprise environments—to learn how organizational architecture actually shapes data architecture, and to discover the cases where our framework needs refinement.
If you're a CDO, CFO, Chief Compliance Officer, or data architect grappling with the challenges this paper describes—fragmented data definitions across silos, unclear ownership, legacy structures that constrain how your organization can evolve—I'd genuinely welcome your perspective. The best contributions to this approach will come from practitioners working with real data challenges in complex organizations.
Read the full white paper here: Organizational Data Flow Architecture: A New Approach to Enterprise Data Management.
As always, thank you for stopping by.