The problem of data models that don’t match reality
A gap between how the business thinks and how the data is designed and built
Data Teams model data to achieve the goal of using that data to deliver an Information Product.
This modeling process is constrained by a number of physical limitations. And that is ok.
But it also means that often the physical model itself does not match the business reality of how the business actually operates and what things are actually called.
Problem Statement
Option 1:
Option 2:
We need a way to create a shared language that both Stakeholders and Data Teams understand.
A language which provides a map of the reality of the business. And a map data teams can use to build the physical data structures they need to deliver the Information Products.
This shared language, this visual map, is called a Business Concept Map.




The stakeholder problem for me is "the data model doesn't describe how the business works" - the data team's response is for me "but that's how your business systems were designed"
I think I prefer option 2