Insights
About us
Contact
Français English
My account

Insight Diversity strategy and governance

A policy without governance is a documented intention

A policy can be perfectly drafted and remain almost invisible in daily decisions.

Mosaïca ConseilsAugust 19, 20264 min read

  • The text
  • The owners
  • The decisions
  • The follow-up

WHAT A POLICY ACTUALLY DOES

It sets an intention and closes a debate.

Let us start by giving it its due. Writing a policy forces an organization to settle questions it had been leaving open: what it expects, what it refuses, what it commits to. The drafting process is often worth as much as the text produced.

A policy also gives people a shared reference point. When a disagreement arises, there is now a document to refer to, rather than a personal judgment. That is useful, and it is not nothing.

A policy sets an intention. It does not organize its application.

WHAT THE DOCUMENT IS MISSING

Four questions a text cannot answer for you.

Who is responsible for it? Not “leadership” or “HR”, but a person for whom it is explicitly part of the role, and who has to account for it somewhere.

What gets decided, and where? A policy creates situations that call for a trade-off. If the place for that trade-off is not designated, it will happen in the corridor, case by case, with varying results.

How do we know it is being applied? A policy whose application is measured by nothing stays true in the binder and undetermined in practice.

When is it reviewed? Without a review date, a text ages without anyone noticing, until the day it describes an organization that no longer exists.

WHY THE GAP GOES UNNOTICED

The document produces a sense of completion.

This is the quietest mechanism in the whole question. Adopting a policy is an event: it is prepared, presented to a committee, announced. It looks like the end of a project, and the organization treats it as such. Attention moves on, and so do the resources.

Yet that is exactly the moment the work begins. An adopted policy is a starting point whose effect depends entirely on what comes next: the responsibilities assigned, the decisions made, the gaps noticed and dealt with.

The symptom is easy to recognize. Ask three managers what the policy concretely changes in their work. If the answers diverge, or if they amount to “we talked about it”, the text exists without governance.

WHAT TURNS A TEXT INTO A PRACTICE

The text becomes binding when it enters the systems.

A policy starts to exist the day it changes something operational: a selection criterion, a step in a process, a mandatory field in a system, a question asked in a team meeting, an item on a committee's agenda.

Those translations are rarely spectacular, and that is what makes them effective: they no longer depend on the memory or the goodwill of whoever currently holds the role.

What, in our processes, would be different tomorrow if this policy did not exist?

If the answer is “nothing”, the document is accurate and has no effect. This is not a drafting problem: it is governance that has not yet been built.