Delete It All And Start Again

Ask Gemma Saint what she’d do with an intranet heading into Copilot, and the answer is not a tidy-up. She’d spin up a whole new SharePoint intranet and start again.

Gemma has spent around twenty years in comms and channels, starting her career in IT and moving into intranet management via a web server and FrontPage. She’s worked at B&Q, Virgin Media O2 and Carnival UK, spent the last four years at SWOOP Analytics covering North America and then Europe, and is now going out on her own to help comms teams bridge the gap between IT, comms and AI.

She joins David Bowman and Jarbas Horst to continue Season 3’s theme of ownership, and her position is blunt. Most organisations are about to lay Copilot across ten or fifteen years of accumulated content with no control over what any of their channels were ever for. One organisation she spoke to this week has seventeen thousand documents on its intranet. Documents alone, before you count pages.

The conversation covers who actually owns the digital employee experience, why moving off SharePoint won’t solve a mess that will simply regrow somewhere else, what a real channel strategy looks like when agents are reading everything, and why she’d take news off the intranet entirely.

Listen on your favourite podcast app

YouTube Spotify Apple Podcasts

David Bowman

Product Director, Fresh
Connect

 

Jarbas Horst,

Senior Product Manager, Fresh
Connect

Gemma Saint,

Co-Founder, Signal Intent
Connect

How to get your intranet ready for Copilot

Someone in your organisation is going to ask an agent how much paternity leave they get.

The answer will come back in seconds, fluent and confident. It will be assembled from whatever your content currently says on the subject, which might include the policy page HR updated last year, an older version somebody saved as a PDF in 2019, and a line in a project site that was never meant to be readable outside that project. You didn’t write that answer but you’re still accountable for it.

This is the part of Copilot readiness that tends to get skipped. Most of the preparation guidance covers licensing, pilot groups and prompt training. The harder problem is that your intranet has quietly become an answer engine, and it will answer from your worst content as readily as your best.

Here’s how to get ahead of it.

What actually changes when an agent starts answering

Internal communications has always been a publishing discipline. You write something, it gets approved, you put it somewhere specific, and what people see is the thing you made. Governance meant controlling what went out.

An agent breaks that model in one move and nobody is reading your page. They’re asking a question, and the response is assembled at that moment from whatever is reachable.

So your accountability quietly expands from the content you published to every answer your content can produce. That includes material you didn’t write, didn’t know about and would never have approved.

It’s worth sitting with the questions people will actually ask. Like, how many holidays have I got left, what’s the policy on carer’s leave, what did the CEO say about the restructure, how much does the exec team get paid. Some of those pull on content that is out of date and some pull on content that should never have been reachable in the first place.

As Gemma Saint, who has spent around twenty years in comms and channels at organisations including B&Q, Virgin Media O2 and Carnival UK, put it on our podcast recently: if you’re going down the Copilot route, you have to take everything off and start putting stuff back in.

That sounds extreme. It’s worth understanding why she lands there.

Why a content cleanup isn’t enough

Most organisations respond to this with a tidy-up. Archive the obviously old pages, fix the broken links, ask site owners to review their content.

Three things make that insufficient.

The scale is bigger than you think. One organisation Gemma spoke to recently had seventeen thousand documents on its intranet. Documents alone, before counting SharePoint pages. Her view is that this isn’t unusual, and most intranet managers who hear that number recognise it immediately. Content accumulates when nobody owns the job of removing it. You end up with file one, file two, file three and file four, all the same document, because somebody didn’t know how to overwrite or didn’t want to delete.

Permissions are messier than your diagram says. You can set guardrails, and you should. But guardrails sit on top of an estate nobody has fully audited. You don’t know whether someone opened their OneDrive to the whole organisation. You don’t know whether a file from a confidential project got saved somewhere it shouldn’t be. Those are exactly the items an agent will surface when somebody asks the right question.

Nobody decided what the channels were for. Most organisations have accumulated ten or fifteen years of content across an intranet, Teams, Viva Engage and email, with the same message often appearing in all four. There was never a decision about what each one was supposed to do. Laying an answer engine across that produces answers that are confident and wrong, because the source material contradicts itself.

A tidy-up fixes the visible symptoms but it doesn’t address any of the three.

Start with an audit you’re willing to act on

Before you change anything, find out what you’ve actually got.

The useful audit answers four questions:

  • How much is there? Pages and documents, counted separately. The number is usually a surprise and it’s a useful one, because it makes the scale of the problem legible to the people who need to fund fixing it.
  • When was it last touched? Pages that haven’t been updated or opened in years are the highest-risk items in your estate, because they’re the ones most likely to contradict current policy.
  • Who owns it? Not who created it. Who is accountable for it being correct today. Most organisations find a significant proportion has no living owner at all.
  • What can be reached by whom? This is the one people skip and the one that causes the incidents.

Use your analytics rather than your instincts here. If you have usage data, it will tell you what’s genuinely being used and what has quietly died.

Decide what your intranet is for, then enforce it

The single most useful thing you can do before switching on an agent is to make a decision about each channel and hold to it.

A channel strategy that works, broadly along the lines Gemma described:

  • The intranet holds the content people need to do their job. Accessible to everybody, with nothing locked down. Someone in finance can read HR content and probably won’t need to, but nothing is restricted. This is also where your agent should be pulling from, which makes it where the governance effort belongs.
  • Teams is the place to work. Projects, collaboration, the material that genuinely needs restricting. When someone asks for a departmental site, this is usually where it belongs.
  • Viva Engage is for conversation across the organisation. Two-way, open, community-focused. It works when people have a voice and hierarchy breaks down, which is exactly what it stops doing once it becomes another broadcast pipe.
  • Email is reserved. Board-level announcements, or something on the scale of a crisis. Nothing else.

Reserving email does something that’s easy to miss. If email is rare, an email arriving tells people it matters. If it isn’t rare, people build rules to filter you out. Plenty of organisations already have employees auto-deleting their announcement emails, which means the channel is dead and nobody has told the comms team.

For agents specifically, there’s a practical reason to concentrate effort on SharePoint. It’s currently the most cited source for Copilot and agents, so that’s where your content needs to live, where your guardrails need to be, and where the maintenance has to happen.

Take the news off

This one divides opinion, and it’s worth taking seriously.

Nearly every intranet has a news archive. Almost none of them should. An intranet was never meant to be an archive, and old news is some of the most dangerous content you can leave reachable, because it reads as authoritative and describes a world that no longer exists.

The practical approach is to use your analytics to find the point where a news item stops being read, and remove it at that point. If something inside an old story still matters, such as a policy change or a process, give it a proper home as a page or a policy document. The rest goes.

The same logic applies to files. If a significant chunk of your intranet is PDFs, those are documents your agent will happily quote from and your people have to download to read. Gemma ran a project at one organisation converting every PDF into a web page, on the simple basis that you’d never visit a website, click to read a news article, and be handed a PDF.

Give deletion a deadline and a consequence

Here’s the part that determines whether any of this actually happens.

Deleting content is socially expensive. Nobody has ever been resented for publishing a page. Everybody who deletes one becomes the person who deleted it, and they hear about it from whoever owned it.

So the incentives point one way in every organisation, and content accumulates by default.

The only thing that works is a process with a deadline and a real consequence attached. Tell content owners their content needs reviewing. Give them three months. Then two. Then one. Then delete it.

That requires air cover from someone senior, and it’s worth getting that agreed before you start rather than halfway through. The argument has become considerably easier to make than it was two years ago: this is no longer about tidiness, it’s about what your organisation is about to start telling people automatically.

Why switching platforms doesn’t solve it

A tempting alternative, and one that comes up constantly at internal comms events, is to abandon a messy SharePoint for a third-party product. Empty, clean, controllable. There’s two problems with that.

The mess developed once because nothing in the organisation was preventing it. Move to a new platform and, over time, the same mess develops there, because the underlying ownership question hasn’t been answered.

And all the original content still exists in SharePoint. Your agent can still reach it. You haven’t removed the problem, you’ve added another place for content to live, which makes the duplication worse rather than better.

The work is the same either way. Decide what should exist, remove what shouldn’t, and give someone clear ownership of keeping it that way.

Who should own this

Which raises the question most organisations still haven’t answered: who owns the digital employee experience?

IT typically owns the platform and the Microsoft 365 estate. Comms typically owns the message. Neither on its own owns whether the thing works.

What’s needed is the role in the middle. Someone who understands what makes the business tick and can also hold a credible conversation with IT about permissions, architecture and rollout. IT teams have the tools but don’t always understand what it takes to make them work. People in the business understand what it takes but often lack the language to connect with IT.

In practice, the organisations getting this right have a partnership rather than an owner. And there’s a straightforward way to open that conversation: go to IT and say you want to help them leverage the Microsoft 365 investment. They’re already paying for it, and it needs to be adopted.

Where to start this month

If you do nothing else:

  1. Count your documents and pages. Separately. Share the number.
  2. Pull a list of everything not updated in two years and find out whether it has an owner.
  3. Pick one high-risk topic people will definitely ask an agent about, such as leave, pay or a current change programme, and trace every piece of content that could feed an answer.
  4. Write down what each of your channels is for, in one line each, and get it agreed.
  5. Get agreement, in advance, on what happens when a content owner doesn’t respond.

None of that requires a licence, a budget or a project. It requires someone deciding to own it.

The alternative is finding out what your content says one wrong answer at a time.

Gemma Saint joined David Bowman and Jarbas Horst on the Fresh Perspectives podcast to talk through what she’d do with an intranet heading into Copilot, including why she’d start hers again from scratch.

Watch the full episode here

Follow and subscribe

If you enjoyed this episode and want to stay updated on how to optimize your SharePoint intranet and enhance employee experience, follow and subscribe in your podcast app.

Follow