Building a Data Governance Operating Model

Opening Scene

A newly written charter sits untouched in a cathedral archive for a generation, beautifully worded but functionally powerless, because no court was ever convened to hear disputes under it, no magistrate assigned to enforce its clauses, and no office established to record who had sworn to follow it — until a new ruler finally builds the courts, offices, and appointed officials the document always assumed would exist.

In Plain English

An operating model is the actual machinery that makes a governance framework function: the standing meetings, escalation paths, decision rights, and working relationships between owners, stewards, and the council that oversees them. It’s the difference between a policy document existing and a policy document actually shaping what people do.

The Old Way

Before organizations designed the machinery deliberately:

Governance frameworks were published as PDF documents, then never connected to any recurring process that referenced them.
Roles like owner and steward existed on paper without any scheduled forum where they actually met to make decisions together.
Escalation paths for disputes were undefined, so unresolved data disagreements simply lingered indefinitely or got settled informally by whoever was loudest.

Designing the operating model — the recurring meetings, decision rights, and escalation paths — is what turns a charter from a document into a functioning government.

What’s Changing (and Why AI Is the Reason)

Organizations increasingly design the operating model at the same time as the policy content, rather than treating structure as an afterthought to be figured out later.
This connects to this content library’s dedicated data cataloging and lineage series, since the operating model typically depends on a working catalog to know which domains exist and who’s assigned to them.
AI governance requirements are adding new decision points — model approval, training data sign-off — that only function well if the underlying operating model already has clear escalation paths and meeting cadences to route them through.

The Metaphor, Fully Extended

The Cathedral Archive vs. the Functioning Court	The Charter vs. the Operating Model
A beautifully worded but unused charter	A well-written but unenforced governance policy
Building actual courts to hear disputes	Establishing escalation paths for data disputes
Appointing magistrates to enforce clauses	Assigning stewards with real enforcement authority
A recurring calendar of court sessions	A recurring cadence of governance council meetings

For Beginners: What to Actually Do

Look for whether your organization’s governance policy has an actual recurring meeting attached to it, not just a document.
Ask what happens, step by step, when two teams disagree about a data definition — if there’s no clear answer, the operating model is missing.
Get familiar with your own role’s place in the operating model, even if it’s just “I flag data quality issues to the steward.”

For Practitioners and Leaders: The Deeper Layer

Design decision rights and escalation paths explicitly, naming who has final say when owner, steward, and council disagree.
Build the operating model’s cadence around existing meetings where possible, rather than adding entirely new recurring obligations to already full calendars.
Treat the operating model as a living structure to revisit annually, since the right cadence and escalation paths change as the organization grows.

Quick Recap

An operating model is the machinery that makes a governance framework actually function.
Frameworks without an operating model behind them tend to sit unused as documents.
Escalation paths and decision rights are the operating model’s most important components.
AI governance decisions add new load to the operating model that needs clear routing.

Where This Fits in the Series

Article 4 established the owner and steward roles at the heart of governance. Article 5 shows how those roles connect into a working operating model with real decision rights and escalation paths. Article 6 zooms into the most visible piece of that machinery: the governance council itself.