Dear reader,
On the day an intranet launches, ownership is never in question. There’s a project team, a project manager, a launch date and someone fielding every “where do I find…” question. Everyone knows who to ask.
Twelve months later, ask the same organisation who owns the intranet and you’ll usually get a pause, then one of three answers: “IT”, “Comms, I think”, or the name of someone who left in March.
The project ends, but the intranet doesn’t
An intranet project has a finish line. The intranet itself doesn’t. Once the launch is done, the project team disbands, the budget closes and everyone goes back to their real job. What’s left is a live system that nobody was formally asked to look after.
Ownership doesn’t disappear in a single moment. It drains away. The person who built the HR site moves teams. The comms officer who updated the homepage goes on leave and nobody picks it up. Permissions get added for a temp and never removed. None of it feels urgent, which is exactly why it compounds.
“Everyone’s job” means nobody’s job
The most common answer I hear is that the intranet belongs to everyone. It sounds collaborative. In practice, it means nobody is accountable when the homepage is six months stale or a document library has three versions of the same policy.
Shared use is good. Shared ownership, with nobody’s name attached, is how a working intranet slowly turns into a place people avoid.
Ownership is really three different jobs
Part of the confusion is that “owning the intranet” isn’t one role. It’s three, and they’re often held by different people:
- The platform owner looks after the whole environment: who has admin rights, how external sharing is handled, what happens when someone leaves. This is usually IT, or whoever is acting as IT in a small team.
- Site owners are responsible for each department or team site. HR owns the HR site, Finance owns Finance. They decide how documents are organised and who gets access.
- Content owners keep the shared spaces current, especially the homepage, news and cross-department resources. This is often comms or the executive office.
When an association says nobody owns the intranet, it’s usually one of these three that has gone missing. Most often it’s the site owners, because those roles were never written down in the first place.
The fix is smaller than you’d think
You don’t need a governance framework or a new committee. You need a short list, kept somewhere people can find it, that names:
- who owns the platform as a whole
- who owns each department and team site
- who owns the homepage and shared content
- who covers each role when that person is away or leaves
Then put a date in the calendar to review it. Once a year is enough for most associations, plus a check whenever someone with an ownership role leaves.
That’s it. A one-page register, reviewed annually, solves most of the drift I see. It also makes the next staff change far less painful, because the handover starts from a list rather than from memory.
Where to start
If you’re not sure who owns what in your intranet right now, that’s the place to begin. My free SharePoint Health Check walks you through six areas where association intranets quietly fall apart, including ownership, permissions and what happens if your most SharePoint-literate person leaves tomorrow. Most associations find at least one surprise.
And if you’d rather talk it through, I’m happy to give you an honest opinion on where your intranet stands.
Until next week,
Brock