SharePoint Intranet Adoption: Why Intranets Stall and What Fixes Them

An intranet that has stalled is rarely broken. It is still there, still technically functional, and still occasionally updated. What has gone is the habit.

The signs are recognisable. Traffic concentrates on a handful of pages, usually the ones linked from an email. Search returns results nobody finds useful, so people stop searching. Teams create their own document stores because they cannot find the shared one. And the phrase that gets repeated in meetings is some version of “it’s on the intranet somewhere”, which is the point at which the intranet has become a filing cabinet rather than a communication channel.

None of that is a platform failure. It is the accumulated result of decisions that were never made, usually because the project ended at launch.

The single most common cause of poor SharePoint intranet adoption is that the intranet has no owner.

Intranets are typically delivered as projects, with a budget, a team and a go-live date. Once that date passes, the team disperses. There is often no named person responsible for the intranet as an ongoing product, no content review cycle, and no budget for continued development.

Content then ages in the way content does. A policy is updated but the intranet copy is not. A team restructures and the page still lists the old contacts. Nobody removes the announcement about the 2024 Christmas arrangements. Individually these are trivial. Collectively they teach people that the intranet cannot be relied upon, and once that lesson is learned it is very hard to unlearn.

The fix is ownership rather than technology. Somebody needs to be accountable for the intranet, with time allocated to it and a review cycle that actually runs. That is a resourcing decision, and it is the one most organisations skip.

People cannot find things

The second cause is structure, and it usually traces back to a decision made early in the build.

Intranets are frequently organised around the organisation chart, with a section per department. That makes sense to the people building it and very little sense to the people using it, because staff do not arrive with a departmental question. They arrive wanting to book leave, find a policy, submit an expense claim or work out who to ask about something.

When the structure does not match the task, people give up quickly. The realistic tolerance is a click or two before someone decides it is faster to ask a colleague, and once asking a colleague becomes the default, the intranet has lost.

The same discipline that makes document libraries usable applies here, which is planning findability deliberately rather than relying on folders and hierarchy. Our post on why SharePoint metadata matters more than folders covers the underlying principle.

The third cause is reach, and it is the one that most often goes unrecognised because the people affected are not in the meetings where intranet performance gets discussed.

Microsoft’s Work Trend Index research into frontline workers, based on a survey of 9,600 employees across eight industries, found that 63 per cent said messages from leadership did not make it to them, with the figure rising to 69 per cent among frontline managers reporting on communication from their own superiors. That is a communication failure, and for many organisations the intranet is where that failure lives.

The mechanics are straightforward. Frontline staff may not have a desk, may share a device or have none, may not have a Microsoft account at all, and are rarely in a position to sit and browse. An intranet designed around a desktop browsing session simply does not reach them, so their usage never appears in the figures and their absence is read as low engagement rather than as exclusion.

If a substantial part of your workforce is deskless, adoption figures for the whole organisation are close to meaningless until you know whether those people can access the intranet at all. That is worth establishing before drawing any conclusions about whether the intranet is working.

This is the question organisations reach for once adoption has stalled, and the honest answer is that it depends on which of the three causes above is actually the problem.

If content is stale because nobody owns it, and the structure was built around the org chart, a new platform will not help. The same content and the same ownership gap will be carried across, and in twelve months the new intranet will be in the same state as the old one, with the added cost of the licence and the migration.

Where a product such as Powell Intranet genuinely earns its place is where the problem is capability rather than discipline: ready-made structure and templates that prevent the org-chart mistake, stronger mobile and frontline experiences out of the box, and built-in governance that makes the content lifecycle harder to ignore. Our comparison of Powell Intranet and out-of-the-box SharePoint works through where that line sits.

The test is straightforward. If you would not fix the ownership and content problems on a new platform either, do not buy one.

The interventions that work are unglamorous and mostly organisational.

Give the intranet a named owner with time allocated to it, not a committee. Build the structure around what people are trying to do rather than around who reports to whom. Establish a content review cycle and enforce it, so pages have a review date and an owner attached. Surface the intranet inside Microsoft Teams through Viva Connections, so people reach it in the app they already have open rather than having to remember a separate destination. And check honestly whether your frontline staff can reach it at all, on the devices they actually have.

Then measure something meaningful. Not page views, which flatter, but whether people find what they came for. If search terms are returning nothing useful, that is the most direct evidence available of what the intranet is failing to provide.