The Data Governance Podcast What is the Difference Between a Data Governance Policy and an Operating Model?
Oct 7, 2025
Discover the crucial differences between a data governance policy and an operating model. Learn why a policy focuses on high-level goals while the operating model details the processes. Find out how to adapt terminology to fit your organization and keep policies stable for efficient updates. Explore the benefits of iterative changes without cumbersome approvals, ensuring a flexible approach to governance. This insightful discussion is a must-listen for those navigating data governance landscapes.
AI Snips
Chapters
Transcript
Episode notes
Policy Overload Killed Approvals
- Nicola recounts that stuffing every detail into a single data governance policy made it unreadable and hard to approve.
- She solved this by keeping policy high-level and moving detailed processes into a separate operating model.
Split Policy And Operating Details
- Do keep the data governance policy focused on the high-level 'what' rather than detailed 'how'.
- Put processes and role descriptions in a separate operating model, framework, or collection of documents instead.
Name It To Fit Your Culture
- Calling a document an 'operating model' helps if the organization already uses that concept.
- But using different labels (framework or collection of documents) avoids resistance where the term feels unfamiliar.