4 min read · 2 September 2026
Every intranet launch starts the same way: a homepage with a hero banner, a welcome note and high hopes. Six months later traffic is a trickle and the project is quietly defended in meetings. The cause is rarely SharePoint. It is the design: the structure mirrored the office politics instead of the way people actually find things. This guide covers the decisions that decide whether your intranet becomes the first tab people open or another forgotten site.
Why intranets die quietly
An intranet dies when the cost of using it is higher than the value of what is on it. Users hit a search that returns nothing useful, or dig through five levels of sites to find the holiday form, and they learn to bookmark a direct link or ask a colleague instead. Once people stop using it, content goes stale, and stale content drives the rest away. The death is quiet because nobody formally cancels the project. They simply stop opening the site, and a month later the usage report confirms it.
Start with information architecture
Structure the intranet around tasks, not departments. People come to an intranet to do something: book leave, find the expenses policy, read this week's news, download a logo. Name things after those tasks and put them at the top level, so any common task is reachable in one or two clicks. Nothing should live deeper than three clicks without a clear reason. Test the structure with real people early, because a menu that makes sense to the project team rarely makes sense to everyone else, and renaming sections after launch is far cheaper than rebuilding the whole tree.
Branding that feels like yours
Vanilla SharePoint looks like vanilla SharePoint, and visitors read that as temporary or unfinished. A little custom branding changes the impression: your logo, your colours, your fonts, consistent headers and a homepage that looks deliberate. It does not need to be elaborate. Consistent visual identity is what tells staff this is the company home rather than a test site. Branding also covers tone: a single owner for announcements, clear titles, and site names that match what people actually call things rather than what the org chart calls them.
News, policies and expiry dates
News pages fill up fast and go stale faster. Put an expiry date on every news item so it archives itself when the date passes. Policies need a review date and a named owner, so nothing stays online wearing last decade's rules. A policy page that shows when it was last reviewed builds more trust than fifty old PDFs that may contradict each other. If the intranet cannot tell you which version of a policy is current, the intranet is part of the problem, and expiry dates are the cheapest way to keep it honest.
Permissions and governance that scale
It feels fine at first to give everyone edit rights. It stops feeling fine when someone deletes a site. Decide early who creates sites, who approves new content areas and who owns each site's content. Use SharePoint groups tied to roles rather than granting individual access. Governance does not mean bureaucracy for its own sake; it means the site stays trustworthy as it grows. A simple rule, such as every site must have a named owner and a review date, prevents most of the problems that kill intranets later.
Search and knowing it is working
Search is the front door of the intranet, so set it up before launch: metadata on documents, clear titles, and the most used pages promoted to the top of results. But adoption does not end at launch. Watch the usage reports, see which pages get opened and which get abandoned, and act on the pattern. Measure what matters, such as how long it takes a new starter to find the expenses process. The fixes are usually small: a rename here, a promoted result there, an owner appointed for a neglected section.
A SharePoint intranet is not a project that ends on launch day. It is a service that needs structure, ownership and a little attention every month. If you would like help with the architecture, the branding or the governance, see what we cover on our services page, and book a free assessment to talk through your site. For the scope of a typical engagement, our pricing page gives fixed packages rather than surprises.