Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Data

Data governance: roles, catalogue and compliance

Data governance is not judged by the thickness of its charter, but by whether a question about a piece of data finds an owner and an answer. Our consultants help your teams establish it domain by domain, starting from real decisions.

Our principles

  • Owners and stewards named for each domain
  • A catalogue fed by tools, enriched by the business
  • Policies translated into effective controls
In brief

Data governance is the set of roles, rules and governance bodies that determine who is accountable for a piece of data, who may use it and under what requirements. Management Square consultants help set it up domain by domain, with named owners and stewards, a catalogue, lineage and policies that are actually applied, including for GDPR compliance.

Scope

How we contribute

  1. Current-state review and priority scope

    Review of existing roles, governance bodies and tools, then choice of a first domain and its critical data. Governing everything at once amounts to governing nothing.

  2. Roles and governance bodies

    Definition of the owner, steward and technical custodian roles, mission statements, allocated time and an arbitration body. We reuse existing committees wherever possible.

  3. Business glossary and catalogue

    Approved definitions of terms and indicators, an inventory of datasets with their owner and classification. The catalogue is fed automatically, then enriched by the stewards.

  4. Data lineage

    A trace of the journey of critical data, from the source application to the report or model, extracted as far as possible from transformation code rather than drawn by hand.

  5. Data policies

    Rules on classification, access, retention and sharing, written in such a way that they can be translated into technical controls on the platform.

  6. GDPR compliance and AI Act readiness

    Coordination with the data protection officer, support in maintaining the record of processing activities and documentation of the datasets used by AI systems.

Page contents

Why data governance so often remains a dead letter

Many organisations have already launched data governance. What remains is a charter, a committee that meets less and less often and a catalogue filled in once, then left as it was. The concrete questions, meanwhile, go unanswered. Who approves the definition of an ‘active customer’? Who authorises access to this table? Who corrects this anomaly?

The causes can be identified. The approach targeted the entire data estate at once, with no priority. Roles were assigned on paper, with no allocated time or decision-making power. The catalogue was entrusted to the technical team, which knows the tables but not their business meaning. Finally, no rule was translated into a control: the policy specifies who may access the data, the platform lets everyone in.

The test of useful governance is simple. When a question arises about a piece of data, it finds an owner and an answer within a reasonable time.

Who is accountable for what: the roles to establish

Governance rests on a small number of roles, held by named people. Their titles vary from one organisation to another; their distribution much less so.

Role Held by Accountable for
Data owner A business manager in the domain The definition, rules of use, expected level of quality, access authorisations
Data steward A business or functional expert close to operations Documentation, investigation of anomalies, maintaining the glossary
Data custodian The team that operates the systems Storage, security and technical application of the rules
Data protection officer The person designated under the GDPR Advice and oversight on the processing of personal data

Two clarifications avoid many misunderstandings. The owner does not own the data in the legal sense: they are accountable for it to the organisation. And stewardship is not a full-time job in most domains, but an explicit part of an expert’s role, recognised by their line management.

An arbitration body completes the arrangement. It settles disagreements between domains (two competing definitions of the same indicator, for example) and approves common policies. It does not need to be new: an existing committee can carry this mandate.

Glossary, catalogue, lineage: three instruments, three uses

The business glossary fixes meaning. It contains the definitions of terms and indicators, approved by the owners. It is what puts an end to debates about what an order, a contract or a customer is.

The data catalogue says what exists. It lists datasets, their description, their owner, their classification and their known level of quality. A catalogue maintained by hand ages quickly: technical metadata must be collected automatically, with the stewards adding meaning and context.

Lineage says where a piece of data comes from and where it goes. It is used to explain a figure, to measure the impact of a change in a source application and to prove, during an audit, the journey of a piece of information. It is reliable when extracted from transformation code, much less so when reconstructed through interviews.

Policies that apply, the GDPR included

A data policy only has an effect if it translates into a control. Four families are enough to begin with: classification (what level of sensitivity), access (who, for what use, with what approval), retention (for how long, then what deletion) and sharing with third parties.

For personal data, the GDPR, Regulation (EU) 2016/679, gives these policies a mandatory basis. Its Article 5 sets out in particular the principles of purpose limitation, data minimisation, accuracy and storage limitation. Its Article 30 requires a record of processing activities to be kept. The catalogue and lineage do not replace this record, but they provide the material that makes it possible to keep it up to date and to respond to requests to exercise rights. We work with your data protection officer, without taking the place of either them or your legal advisers.

AI adds a requirement. Article 10 of the AI Act, Regulation (EU) 2024/1689, subjects the training, validation and test datasets of high-risk AI systems to data governance practices. Our entry on the AI Act presents its overall logic, and the subject continues in our AI governance offering.

Our approach: one domain, real cases, then extension

Our consultants work within your teams; decisions remain yours.

Choosing a domain and its critical data. Together we select a domain where the stakes are visible: data that feeds a leadership indicator, a regulatory report or an AI project. The scope is deliberately narrow.

Establishing the roles. Owners and stewards are named, their mandate is written down, their time is negotiated with their line management. Without this step, everything else remains theoretical.

Working through real cases. A disputed definition, a sensitive access request, a recurring anomaly: rules emerge from resolving these cases, not from a drafting exercise. Each decision made is recorded and reusable.

Tooling, then extending. The glossary and catalogue are put in place once the roles are working. The following domains adopt the model, adapted to their context. In highly decentralised organisations, this extension takes the form of federated governance, as described by the data mesh: a small number of common rules, applied by each domain.

Five failings that drain governance of its effect

  • Starting with the tool. A catalogue with no owners to feed it becomes an out-of-date inventory.
  • Naming without mandating. An owner who has neither the power to decide nor the time to do so is a name in a table.
  • Housing governance in IT alone. Technical teams apply the rules; they cannot arbitrate the meaning of business data.
  • Writing policies without controls. An access rule that is not configured on the platform binds no one.
  • Confusing governing with correcting. Governance decides the expected level of quality and who deals with deviations. Measurement and controls fall under data quality, which is carried out in parallel.

Measuring that governance is working

The indicators chosen at framing concern the effect of governance, not the volume of documents produced.

  • The share of critical data with a named owner and an approved definition.
  • The time taken to process an access request, from request to decision.
  • The share of exposed datasets that carry a description, a classification and an owner in the catalogue.
  • The number of definition disagreements brought before the arbitration body, and the number actually settled.
  • The use of the catalogue by business users.

The last sign is qualitative. When project teams spontaneously consult the owner of a piece of data before using it, governance has become part of working habits. This change in practice cannot be decreed: it is prepared and supported over time.

Typical work

What our consultants contribute to

Governance model

Roles, governance bodies, decision paths and operating rules approved by leadership.

Responsibility matrix

A named owner and steward for each critical data item in scope, with the corresponding mandate.

Initialised glossary and catalogue

Agreed definitions and described datasets for the first domain, with the procedure for keeping them up to date.

Body of policies

Classification, access, retention and sharing policies, together with the controls that apply them.

See also

Related services

AI governance Knowing which AI systems you use, what level of risk they fall under and who is accountable for them: this is the foundation of compliance, and the condition for quickly authorising what can be authorised. Change management A project delivered and not used has spent its budget without producing anything. Our consultants help your teams prepare for adoption from the framing stage: who is affected, by what, and what they need to work differently. Cyber resilience A recovery plan that has never been run is a hypothesis. Our consultants start from your critical activities and help your teams measure what they actually know how to restore, then reduce the gap, including at your providers. AI strategy An AI strategy is not a catalogue of ideas: it is a short list of funded use cases, each with an owner, an indicator and a stopping criterion. BI and analytics Three dashboards, three revenue figures: the problem does not come from the reporting tool, but from the lack of a shared definition. Our consultants help your teams build a BI where each indicator is defined once and reused everywhere. Data quality and MDM Data is not good or bad in the absolute: it is either sufficient for a given use or it is not. Our consultants help your teams measure quality where it matters, control it automatically and address the causes at the source. PMO and project governance A useful PMO does not produce reports: it gets decisions made. Our consultants help put in place the governance, rituals and indicators that make your projects clear and open to arbitration. Sovereign and hybrid cloud Not all your data requires the same level of protection, and no single provider meets all your needs. We help you classify your uses, choose the right environment for each and keep the option of changing it.

Insights

Further reading

All insights

Management Square in figures

300+
projects completed
43+
clients supported
Since2015
serving our clients
  • Allianz
  • Euler Hermes
  • Groupe BPCE
  • ODDO BHF
  • Candriam
  • Ledger
  • Saur
  • Veolia
  • Voltalia
  • emeis
  • Bonpoint
  • Legal Suite

FAQ

Frequently asked questions

Another question? Ask us

What is data governance?

Data governance refers to the roles, rules and governance bodies through which an organisation decides how its data is defined, protected, shared and used. It answers three questions: who is accountable for this data, who may access it, and what requirements it must meet.

What is the difference between a data owner and a data steward?

The data owner is a business manager who decides: they approve the definition, the rules of use and the expected level of quality. The data steward brings these decisions to life day to day: they document, investigate anomalies and keep the glossary up to date. The former has the authority, the latter the detailed knowledge of the data.

Do you need a catalogue tool to get started?

No. A catalogue deployed before the roles are working gets filled once and then ages, for lack of owners to keep it up to date. We recommend first establishing owners and stewards in one domain, working through a few real cases with them, then choosing the tool that serves this organisation.

Is data governance enough to comply with the GDPR?

No, but it provides direct support. The GDPR, Regulation (EU) 2016/679, contains obligations of its own, for example on the legal basis for processing, informing individuals or impact assessments, which fall to the controller, advised by its data protection officer. Governance provides the owners, the inventory and the lineage that make these obligations manageable.

Who should lead data governance?

An identified function, often a data department, drives the approach and maintains the common framework. Decisions on the meaning and use of data belong to the business, through the owners. The IT department applies the rules technically. Attaching governance to IT alone deprives it of its business authority.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.