Applied Data · Module 2

Data governance and stewardship

Governance is agreeing how data is handled so people can work quickly without being reckless.

20 min 4 outcomes Data Intermediate

Previously

Data architectures and pipelines

Data architecture is how data is organised, moved, and protected across systems.

This module

Data governance and stewardship

Governance is agreeing how data is handled so people can work quickly without being reckless.

Interoperability and standards

Interoperability means systems understand each other.

Progress

Mark this module complete when you can explain it without rereading every paragraph.

Why this matters

If a team shares a spreadsheet called “final_final_v7”, that is governance, just done badly.

What you will be able to do

1 Explain data governance and stewardship in your own words and apply it to a realistic scenario.
2 Governance works when it connects policy to enforcement and evidence.
3 Check the assumption "Policies are enforceable" and explain what changes if it is false.
4 Check the assumption "Stewards have authority" and explain what changes if it is false.

Before you begin

Foundations-level vocabulary and concepts
Confidence with basic diagrams and section terminology

Common ways people get this wrong

Policy without tooling. Policies that rely on memory fail. Build guardrails into systems.
Approval bottlenecks. Governance that blocks delivery creates shadow systems. Design for flow.

Main idea at a glance

Diagram

Stage 1

People

Define accountability and decide what data means.

I think clarity of who owns what prevents problems from living in the gap between teams.

Governance is agreeing how data is handled so people can work quickly without being reckless. Ownership is the person or team that decides purpose and access. Stewardship is the day to day care of definitions, quality, and metadata. Accountability means someone can explain how a change was made and why.

Policies are not paperwork for their own sake. They are guardrails. Who can see a column, how long data is kept, what checks run before sharing. Even a shared spreadsheet is governance in miniature. Who edits, who reviews, what happens when something looks off.

Trust grows when policies are clear, controls are enforced, and feedback loops exist. If a report is wrong and nobody owns it, confidence collapses quickly.

Worked example. The spreadsheet is still governance

If a team shares a spreadsheet called “final_final_v7”, that is governance, just done badly. There is still access control (who has the link), retention (how long it stays in inboxes), and change control (who overwrote which cell). The only difference is that it is informal, invisible, and impossible to audit.

My opinion: governance should feel like good design. It should make the safe thing the easy thing. When governance feels like punishment, teams route around it and create risk you cannot even see.

Common mistakes (governance edition)

Governance failure patterns

Governance fails when policy and operating reality diverge.

Policy disconnected from reality

Exceptions become standard practice when policies ignore day-to-day constraints.
Ownership without time allocation

A title alone does not deliver accountability unless operational time is assigned.
Manual checks for repeatable risks

Automate schema and row-count drift detection to reduce silent failures.
Temporary access with no expiry

Unbounded temporary access becomes a persistent security and compliance risk.

Verification. Prove it is not just words

Governance verification drill

Turn governance language into checks that can be executed.

Define accountability envelope

Write purpose, owner, steward, retention period, and access scope for one dataset.
Add one breaking-change guardrail

Define an automated check that catches schema breaks before release.
Write an accountability sentence

State what investigation and response should look like if a report is wrong.

Mental model

Governance as an operating model

Governance works when it connects policy to enforcement and evidence.

1

Policy
2

Tooling
3

Process
4

Evidence

Assumptions to keep in mind

Policies are enforceable. If a policy cannot be enforced or measured, it will become optional under pressure.
Stewards have authority. If stewards cannot stop harmful changes, governance becomes symbolic.

Failure modes to notice

Policy without tooling. Policies that rely on memory fail. Build guardrails into systems.
Approval bottlenecks. Governance that blocks delivery creates shadow systems. Design for flow.

Check yourself

Quick check. Governance and stewardship

0 of 6 opened

Why does governance exist

To balance safe data use with speed and clarity.

What does ownership mean

Deciding purpose and access.

What does stewardship mean

Caring for definitions, quality, and metadata.

Why are policies useful

They are guardrails that prevent accidental misuse.

Scenario. A team asks for full access “temporarily” to ship a feature. What is a safer governance response

Grant least-privilege access for the minimum time, log it, and require justification and review. Temporary access without expiry is permanent risk.

What happens without governance

Confusion, rework, and falling trust in reports.

Artefact and reflection

Artefact

A one-page decision note with assumption, evidence, and chosen action

Reflection

Where in your work would explain data governance and stewardship in your own words and apply it to a realistic scenario. change a decision, and what evidence would make you trust that change?

Optional practice

Choose policies and see how risk, access, and usability shift for a sample dataset.