Three myths about content governance
This is one of those topics that looks small until it costs you something. A few things about content governance that get repeated more often than they get checked.
Content is the part of a project most likely to be underestimated and most likely to delay a launch. Budget a little time for it every quarter and it never becomes a project of its own.
“It only matters for big sites”
Someone must own each page or it rots. There is a version of this that is over-engineered, and it is worth avoiding. Assume whoever inherits this will have half your context and none of your patience.
“We can deal with it after launch”
Sometimes true, usually expensive. The cost of getting this wrong is rarely visible on the day it happens.
“Our platform handles it”
Removing outdated content is maintenance, not loss. Getting it slightly wrong is survivable. Ignoring it entirely is not. Doing this properly once is usually cheaper than doing it approximately three times.
How to tell if yours is fine
Pages that answer a real question outlive pages written to fill a slot in a sitemap. Three things worth confirming about content governance before you move on:
- Someone can say what the current setup is without going to look
- Removing outdated content is maintenance, not loss — and you know whether that is true here
- There is a way to tell whether the last change to this helped
The point is not perfection, it is knowing which of these you have consciously chosen to skip.