The intranet isn’t dead. The old mental model is.

Every couple of years, someone announces that the intranet is dead.

Sometimes the killer is Teams. Sometimes Slack. Sometimes Jive (remember that?) or whichever employee platform happens to be spunking VC money on the conference circuit that year. The announcement tends to arrive with the confidence of a vendor keynote and the shelf life of a yoghurt. The names change. The argument doesn't. And a few months later, most organisations are quietly still doing the thing an intranet does, on something that looks suspiciously like an intranet, under a name nobody can quite agree on. The technology moves on. The need does not.

The intranet is a function, not a tool

The case for the intranet was never really a case for the technology. It's a case for somewhere – anywhere – that final content lives, owned and current, with one version of the truth and a person whose job it is to keep it that way. Every organisation needs that. What you call it is a separate argument, and a less interesting one.

What's dying is the old mental model: static pages, broken search, abandoned content, and a homepage that exists mostly to broadcast things nobody asked for. What isn't dying is the underlying job. People still need one place where they can stop guessing.

That’s why Publish carries so much weight in the five-layer model we introduced in an earlier post – Plan, Collaborate, Publish, Distribute, Discuss. Publish is the load-bearing layer in that stack. Collaborate is where drafts and working conversations happen. Discuss is where people respond, question and make sense of things. Distribute is how content reaches people. 

But Publish is where ambiguity is supposed to end. It’s the trusted source of truth. If Publish fails, the whole ecosystem wobbles. 

As we argued in our earlier post on intranet audits vs discovery, the problem is often not the platform itself, but starting with the wrong assumptions about how people actually work.

What is an intranet anyway?

The intranet isn't the whole digital workplace. It's the front door to it. The digital workplace is everything employees use to get work done – chat, HR, learning, service tools, the document factory, the dozens of SaaS apps someone bought in 2019 that nobody can quite explain anymore. The intranet (or hub, or app, or whatever it's branded this quarter) is the bit that organises that sprawl. The more apps multiply, the more important that organising role gets, not less.

This is also why a modern publishing platform cannot just be a news site with better branding. 

In Chapter 4 of Digital Communications at Work, we describe it as a graphic-equaliser – four sliders every organisation has to set: news and communications, knowledge content, applications and transactions, communities and collaboration.

The point isn't that one configuration is correct. The point is that different organisations should set those sliders differently, deliberately, and notice when they've drifted. A heavily regulated firm will turn up knowledge and task completion. A dispersed frontline workforce will lean hard on apps and mobile. A culture-led organisation will give weight to community. The wrong move is to assume there's a default mix. There isn't.

Killing the intranet just scatters the problem

Seen through that lens, “we’re killing the intranet” is often less of a strategy than it sounds. Seen in that light, "we're killing the intranet" is less a strategy than a relocation scheme. The publishing need doesn't go away when you decide everything will now live in Teams; it just moves house, badly. Policy ends up in a channel somebody pinned in 2023. The "final" version of the brand guidelines is a PDF that has been re-uploaded four times, each with a slightly different filename and none of them current. Decisions live in a Slack thread that two people remember and nobody can find. Ask where the approved leave policy lives and the honest answer is usually "depends who you ask, on which day, in which tool." That isn't a digital workplace. It's a missing persons enquiry. You haven't killed the intranet. You've just made everyone do its job, worse, in seventeen places at once.

None of which is an argument for one giant monolithic platform with every piece of work shoved through it. Large, federated, regulated organisations rarely run on a single tool, and shouldn't try to – that's the fantasy version of consolidation, and it tends to die in procurement. The point is clarity of destination: one place people can reliably go when they need the canonical version of something. The plumbing underneath can be as messy as it needs to be. The front door cannot.

A product, not a project

Whether the answer is a heavily-customised SharePoint, a consumer-grade employee app, a standalone platform, or – and this is a real example, from a real organisation we worked with – a creatively maintained Excel spreadsheet, the technology is genuinely the second question. The first is whether the publishing layer exists at all, whether anyone owns it, and whether people trust it. Get those right and the platform argument resolves itself. Get them wrong and no amount of platform will save you.

Whatever you build it on, a good intranet looks less like a campaign microsite and more like a product. It blends communication with utility and earns attention by being useful. People come for the leadership update, sure – but they're just as likely to come to find a policy, check a process, get to an application, or answer a practical question. That isn't a distraction from communication. It's what makes communication work. And because the systems and behaviours around it keep changing, the publishing layer is never finished. Run it as a product, not a project.

So the better question isn't whether the intranet is dead. It's whether yours can pass a simple test: is there one place people trust, does it have an owner, and does it tell them the truth? If not, you don't have an intranet problem – you have an organisation where people quietly invent their own answers, and hope they're current.

Digital Communications at Work is out in July. Chapter 4 goes deep on the Publish layer – intranet strategy, governance, digital employee experience, content operations, platform choices – for anyone who wants to take this beyond a single blog post.