Data governance as a growth enabler, not a tax

Governance usually arrives as a playbook. In my case it literally did — a procedure handed down from regional headquarters, clear on why data had to be controlled and what good looked like in principle. That playbook was correct. On its own, it was also inert.

The part almost nobody talks about is the gap between a governance framework on paper and a governance system that actually runs. Writing that data must be controlled is the easy sentence in the job. Making it true is where the real work is — and it is harder than the writing by an order of magnitude.

Turning the playbook into something that runs

When I became Data Governance Officer for the consumer banking of an entire country, my job was not to author theory — theory already existed. My job was to make it operate. That meant doing the unglamorous, technical work the playbook assumed was already done:

• Identifying the critical data elements — not a few dozen, but thousands, each one tied to a decision the bank actually makes.
• Mapping data lineage — where each element is born, how it transforms, where it lands, and where it can quietly break.
• Naming an owner for every metric — a person, not a committee, who answers when the number is wrong.
• Writing the validation rules — the checks that turn “we care about quality” into a mechanical, repeatable test.

None of this is paperwork. To set it in motion you have to understand the data structures and the algorithms underneath them, because the rules only hold if they’re written against how the data actually flows. And none of it earns its keep until you can show the payoff — faster reporting, fewer reconciliation fire-drills, numbers people can decide on without a second guess. Governance gets adopted when the people it protects can feel the value.

Turning regulation into a language people can run

The second time this gap mattered most was when new local regulation landed. The law said what had to be true. Acting as lead methodologist for the corporate bank, my job was to say how — in the language of data and in the language of the business, so that the people responsible for reports understood what was now expected, how to control the metrics, and why it mattered.

A regulation becomes real only when the owner of a report can repeat, in their own words, what changed and how they prove it. So we ran workshops and worked through real cases — taking the statute apart line by line and translating each obligation into a control the owner could actually operate. The methodology was the bridge; the workshops were where the bridge got walked across.

The leadership lesson

Both projects taught the same thing: governance is a leadership decision before it is a technical one. A framework owned far from value creation becomes a brake. A framework that meets people where they work — grounded in the data, owned by name, measured, and shown to pay off — becomes infrastructure for speed. The CDOs who get this right don’t sell governance as compliance. They sell it as the foundation that makes scale possible.

If your governance programme is making people slower, the programme is the problem, not the people.