Somebody writes the policy. Somebody approves it. It gets a version number and a home on the shared drive, and the room relaxes. That relaxation is the thing to worry about.
The document is the easy part
Writing a governance document is satisfying work. You get to be thorough. You name the risks, set the principles, draw the approval matrix, and when it is done you have something you can hold up in a meeting. It looks like control.
I have written documents like this. I have also watched them change nothing, which is the more useful experience to have had.
Regular readers will see the shape of this. The first draft of almost anything is the cheap part now. Governance is no exception. A document is a description of how you intend to make decisions. It is not the decision, and it is not the person who makes it. Those are three separate things, and the document is the only one you can finish in a weekend.
What governance actually is
Governance is what happens when a real decision meets your stated intent and one of them has to bend. Someone wants to ship the thing fast. The policy says slow down and check first. Governance is whether the check actually happens, who has the standing to insist on it, and what follows if it gets skipped.
Strip it down and you need three things a document cannot supply on its own.
The first is a named owner for each decision the policy touches. Not a committee, not a department. A person who answers for it.
The second is a consequence when the policy is ignored. If nothing happens when someone goes around it, you do not have a rule. You have a preference.
The third is a reason to open the document again after it is approved. A policy nobody consults between sign-off and audit is decoration with a version number.
The brand guideline everyone has lived through
Here is an example my field knows by heart. A company invests in a brand guideline. Fonts, colors, logo spacing, tone of voice, all of it documented and genuinely well made. It gets circulated. Everyone agrees it matters.
Then a regional team ships a flyer that breaks half of it, because the deadline was Friday, the guideline was forty pages, and nobody had the standing to hold the launch. No one is surprised. No one is reprimanded. The next quarter, someone proposes refreshing the guideline.
The guideline was never the problem. The missing piece was a person whose job was to catch the Friday flyer, and the authority to make the catch stick. That person is the governance. The forty pages are a reference that person uses, assuming that person exists.
How to tell which one you have
There is a quick test for whether an organization has governance or a document. Pick the policy everyone points to. Then ask three questions out loud and watch how long the pauses run.
Who owns this decision. If the answer is a department rather than a name, you have a document.
What happened the last time someone ignored it. If no one can recall an instance, the policy is either never tested or never enforced, and both should worry you.
When did we last open this for a live decision, not a scheduled review. If the honest answer is the day it was approved, the document is governing nothing.
The pauses tell you everything. The document itself is almost always fine. The three things around it are almost always missing.
None of this is hard to understand. It is hard to do, because the real work of governance is boring and it never finishes. It is a standing meeting. It is an owner who says no at an inconvenient moment. It is a consequence somebody has to apply to a colleague they like. The document is finite and satisfying. The practice is ongoing and slightly unpleasant.
So organizations write the document and call it governance, because the document is the part you can actually finish. Then the next new risk arrives, AI being the current one, and the first instinct is to write another document.
The better instinct is to put the template down and ask who owns the decision. If you cannot name the person, nothing you write will govern anything.
I write about creative leadership, AI adoption, and the parts of the job nobody puts in a keynote. One post every two weeks.