I have experienced many orginisations, where governance is treated as a box to tick. Committees are formed, roles are defined, frameworks deployed. Yet despite the structure, data problems persist. Why? Because governance often overlooks the realities of how work actually happens.

Governance is not about committees, frameworks, or endless policies. It’s about protecting the business from the moments where failure matters most. By adopting a process-driven, targeted approach, you make governance practical, visible, and most importantly effective.

Start small, start smart, and let process guide you.

The truth is simple: data doesn’t fail randomly. It fails in predictable moments which is shaped by processes.

• When data is created
• When it is approved
• When it is enriched or transformed
• When it is handed over between teams
• When it is reused for a new purpose

These moments are where the business lives, where impact happens, and where mistakes matter. Minimum governance starts here.

Identify the Pain Points

The first step is brutally honest: figure out where failure hurts the most. Not every missing field or duplicate record is equally important. Ask yourself:

• Which data errors cost money, slow operations, or create risk?
• Which processes rely on timely and accurate information to function?
• Where does bad data cascade downstream, amplifying impact?

Focus governance effort on these areas. Less critical issues can be monitored lightly or deferred. This is not laziness; it is efficiency.

Here is the catch. Most organisations claim to do pain point analysis, but how often is it real? Too often, the exercise consists of interviewing the people we already talk to, mapping out issues that support the solutions we were planning anyway. Rarely is there a real effort to quantify the cost, to measure the impact downstream, or to track improvement once governance interventions start changing processes.

I would argue this happens so infrequently that most so-called pain point analyses never actually steer priorities. They become justification documents rather than instruments for decision-making. Real pain point analysis should create a clear line from problem to cost to improvement potential, so that governance effort lands where it actually matters. Anything else is just paper exercises in looking busy.

Make Governance Visible Through Process

A process-driven approach turns governance from abstract to practical. By mapping the flow of data through the business, you can see where controls are needed and where accountability sits. Process provides two things governance frameworks cannot: visibility and context.

• Visibility tells you exactly where errors occur.
• Context tells you why they occur, and who has the power to prevent them.

When you embed governance in the process, it becomes part of daily decision-making, not a separate layer of oversight.

Minimum Governance in Practice

• Targeted Controls: Apply stricter rules where errors are most costly. Lax standards elsewhere.
• Data Ownership by Process: Assign clear responsibility at the point of data creation and handover. Don’t just assign a role; make accountability part of the process.
• Feedback Loops: Track issues and feed them back to the process owners. Continuous learning beats static rules.
• Benchmarking Compliance: Measure how well actors in the process maintain data quality. Make it visible who consistently produces good or bad outcomes.

Minimum governance doesn’t mean minimal effort, it means maximum impact. By focusing on process-critical points, you protect the business while avoiding bureaucratic waste.