While collide is perhaps a strong term to use to describe the key area where Data Architecture and Data Governance interact, it does provide motivation to perhaps calm the traffic and avoid further collisions. In order to harmoniously interact, architecture and governance must literally be working from the same diagram (singing from the same sheet of music). The worst time to try to accomplish this is on a short-term decision. Better still to educate each group to the function of the other and major issues upcoming. A shared Data Literacy exercise can provide a good starting point.
Learning objectives:
- Gaining a good understanding of both important topics, each’s relationship to the other, and what is required for each to be successful
- Not to have the first conversation be the important one
- Coordination is key requiring necessary interdependencies and sequencing
- Integration challenges can be valued, assisting shared priority development
4. 3
Cloud Platforms
Martech
SaaS Apps
Mobility & Devices
Customer / Partners /
Suppliers
Packaged Apps
Databases
Today, data is highly siloed and fragmented
Jane Smith
Opted in for
marketing
Jane Smith
Renewed
policy
John
Smith
Same
household
Jane E
Smith
Called
support
Jane E
Smith
Filed auto
claim
5. 4
Unmanaged data leads to poor business decisions
Low quality data creates
inaccurate insights
Data issue identification is
inconsistent and lacks visibility
Data issue resolution is
irregular, highly manual, and
prone
to errors
6. 5
Customer / Partners / Suppliers
Cloud Platforms Martech
Analytics, ML & AI
3rd Party Data Sources
Packaged Apps
Mobility & Devices
Custom Apps Databases
SaaS Apps
Modern MDM turns policy into action
Automated data
unification
Continuous curation
Flexible stewardship
workflow
Attribute level
permissions
Full audit logging