Governance Guide Law 25

Data Governance: Complete Guide 2026

Data governance is no longer a luxury. With Law 25, GDPR, and the rise of AI, it's a legal obligation and a competitive advantage. Here's everything you need to know — without jargon.

OC

Oleg Chitic

· 12 min read

TL;DR

Data governance is the set of policies, roles, and processes that determine how an organization collects, stores, uses, and protects its data. In 2026, with Law 25 in Quebec and GDPR in Europe, it's no longer optional. This guide covers the fundamentals, key roles, 7 fatal mistakes, and a 5-step method. The CQSEV framework is presented as a diagnostic tool.

⏱️ 12 minutes

Key vocabulary in this article

Data Owner — the person responsible for a data domain (the owner)
Data Steward — the day-to-day guardian of data quality (the caretaker)
KPI — a measurable indicator that tracks a concrete outcome
Pipeline / ETL — an automated workflow that moves and cleans data
Law 25 — Quebec's privacy protection law
Lineage — traceability: where data comes from and where it goes

What is data governance?

Data governance is the set of policies, roles, processes, and standards that determine how an organization collects, stores, uses, shares, and protects its data. It's the decision-making framework that answers the question: "Who is responsible for what, and according to which rules?"

Think of the Highway Code. It doesn't drive for you. It sets the rules: speed limits, right of way, red lights. Without it, every driver would invent their own rules — and accidents would be inevitable.

Data governance is the Highway Code for your data.

You can also think of it as a library. Imagine thousands of books with no organization:

The best governance is the kind people follow naturally because it makes their life easier.

Without governance

  • × 15 versions of the same file
  • × "What is this field?"
  • × Contradictory data between departments
  • × Nobody knows who has access to what

With governance

  • A single source of truth
  • A clear data dictionary
  • Reliable, consistent data
  • Controlled and traceable access

Concrete value:

  • Faster decisions — a single version of the truth
  • Fewer costly errors — data is verified
  • Legal compliance — Law 25 met
  • Customer trust — their data is protected

What it is

Defining who is responsible for customer data. Writing quality standards. Setting access rules.

What it is not

Buying a $500K tool. Creating 200 pages of policies. Naming a committee with no decision-making power.

What it should be

A pragmatic framework. 3 policies that work. Clear roles. Concrete measurements.

Why it's critical in 2026

1. Regulatory pressure

In Quebec, Law 25 (Act to modernize legislative provisions as regards the protection of personal information) came into full effect in September 2024. It requires organizations to:

Fines can reach $25 million or 4% of global revenue.

2. AI needs reliable data

An AI model trained on incomplete, duplicated, or incorrect data produces dangerous results. "Garbage in, garbage out" — at AI scale, the consequences are amplified:

Simple rule:

Before deploying an AI model, ask yourself the 5 CQSEV questions about the data feeding it. If you can't answer "yes" to the Compliance and Quality axes, your model is a risk.

3. The cost of poor quality

According to Gartner, organizations lose an average of $12.9 million per year due to poor data quality.

Essential components

Policies

The rules of the game: quality, access, retention, classification. 3 clear policies are worth more than 200 pages.

Roles

Who is responsible for what: the Data Owner, the Data Steward (day-to-day guardian), the Data Custodian (technical lead). Names, not vague job titles.

Processes

How rules are enforced, verified, and improved. Audit, measurement, escalation, correction.

Tools

Data catalog, business glossary, data lineage (traceability — where it comes from and where it goes). Tools come AFTER processes, never before.

Key roles

Role Responsibility Analogy
Data Owner
Data responsible
Sets the rules for their data domain. Has the authority to say "yes" or "no."The building owner
Data Steward
Data guardian
Enforces the rules day-to-day. Checks quality, fixes anomalies.The building caretaker
Data Custodian
Technical lead
Manages the technical infrastructure: storage, security, access, automated processing pipelines.The maintenance company

The 7 fatal mistakes

Mistake 1 — Too much bureaucracy

A large Montreal-based insurer produced a 247-page governance document. Result: nobody read it. Start with 3 one-page policies.

Mistake 2 — No executive sponsor

Without a VP or senior executive carrying the message, the governance committee meets, discusses, and then nothing changes. The sponsor should not be the CTO — ideally a business leader who understands the operational impact.

Mistake 3 — Starting with the tool

"Let's buy Collibra / Informatica / Alation." The tool costs $200K to $500K per year. Six months later, nobody uses it because the processes were never defined. The tool is there, but it's useless.

Mistake 4 — Ignoring the field

Perfect policies in a shared folder that nobody opens. If the Data Steward doesn't check every week, the rules don't exist in reality.

Mistake 5 — No measurement

"Our data quality is fine." Really? What's the duplicate rate? What percentage of addresses is invalid? Without a measurable indicator (KPI), it's opinion, not governance.

Mistake 6 — Trying to govern everything at once

Start with ONE critical domain — usually customer or financial data — prove the value, then expand. Rome wasn't built in a day.

Mistake 7 — Forgetting the automated systems

Policies are defined but the automated pipelines processing your data (ETL pipelines) keep loading invalid data. It's like having traffic laws without speed cameras. That's why CQSEV includes a third layer: transformation.

How to get started in 5 steps

Step 1 — Identify 3 concrete problems

Don't start from theory. Start from pain points:

Step 2 — Appoint the responsible people

For each data domain, appoint a Data Owner and a Data Steward. No need to hire — these are often people already doing this work informally.

Step 3 — Write the 3 critical policies

A quality policy (what makes data "good"?), an access policy (who can see what?), and a retention policy (how long do we keep data?). Each policy fits on a single page.

Step 4 — Measure your starting point

Before improving, measure where you stand today: duplicate rate, number of undocumented fields, who has access to sensitive data. This baseline will let you demonstrate progress.

Step 5 — Assess with CQSEV

Use the CQSEV matrix (5 axes × 3 layers) to evaluate each dimension. For each cell, ask: does the rule exist? Is it enforced? Is it automated? The empty cells are your priorities.

The role of the CQSEV framework

The CQSEV framework solves the fundamental problem: the gap between rules and reality.

Here's how it compares to other reference frameworks:

Aspect DAMA-DMBOK
Global standard
DCAM
Financial sector
CQSEV
Scope11 knowledge areas8 capabilities5 axes × 3 layers
Includes field verificationPartiallyPartiallyYes (Manage layer)
Includes automated systemsNoNoYes (Transform layer)
Diagnostic timeWeeksDays½ day to 2 days
SMB-friendlyDifficultModerateYes

💡 DCAM = Data Management Capability Assessment Model, an assessment framework developed by the EDM Council, primarily used in the financial sector.

→ Learn more about the CQSEV framework

Key takeaways

Data governance in 2026 is no longer a "nice to have" project. It's a legal obligation, an AI prerequisite, and a competitive advantage.

But it doesn't have to be complex. 5 principles after 15 years in the field:

  1. Pragmatism before perfection — 3 policies that work beat 200 pages
  2. Value before control — If people don't see the benefit, they'll work around the rules
  3. Adoption before technology — A tool without human buy-in collects dust
  4. Measurement before opinion — Without a KPI, it's a belief, not a fact
  5. One domain before all — Prove the value on a concrete case, then expand

"Data governance is not a destination. It's an organizational habit that is built one axis at a time."

📊 Assess your data governance

The CQSEV grid (5×3) in Excel. 15 checkpoints. 30-minute diagnostic.

Download the grid (Excel)

Frequently asked questions

What is data governance?
The set of rules, roles, and processes that determine how an organization collects, stores, uses, and protects its data. Think of the Highway Code — it doesn't drive for you, it sets the rules so everyone drives safely. Or think of a library — without classification, without a catalog, without a section manager, it's chaos.
Is data governance mandatory in Quebec?
Yes, indirectly. Law 25 (Act to modernize legislative provisions as regards the protection of personal information) requires protecting personal information, appointing a responsible person, and reporting privacy incidents. Without formalized governance, compliance is practically impossible. Fines can reach $25 million or 4% of global revenue.
What is the difference between data governance and data management?
Governance defines the rules — it's the "what" and the "who." For example: "Only managers have access to salary data." Management enforces those rules day-to-day — it's the "how." For example: "Every quarter, we verify that only managers still have access." CQSEV evaluates both — plus a third layer, transformation, which checks that automated systems also follow these rules. Read the dedicated article.
What do Data Owner and Data Steward mean?
The Data Owner is like a building owner — they set the rules for their data domain. The Data Steward is like the building caretaker — they enforce the rules day-to-day, check that everything is in order, and fix problems. These are not positions to create: they're often people already doing this work informally.
How do you measure governance maturity?
Use the CQSEV matrix. For each axis (Compliance, Quality, Security, Efficiency, Value), rate from 0 to 5 in each layer (Govern, Manage, Transform). Total score out of 75. The lowest cells are your action priorities. Download the free grid.
How long does it take to set up governance?
Initial diagnostic: half a day to 2 days. First policies and roles appointed: 4 to 6 weeks. But keep in mind — governance is not a project with an end date. It's an organizational habit that takes hold gradually, one domain at a time.
OC

Oleg Chitic

Creator of the CQSEV framework. 15+ years of experience in digital transformation, data governance, and data management within public sector, retail, and technology organizations in Montreal.

Follow on LinkedIn