A SharePoint intranet usually fails for organisational reasons, not technical ones. Nobody owns the content, the navigation mirrors the org chart instead of what people look for, search returns old files, and the launch has no plan for the first ninety days. Fix those five things and the technology rarely gets in the way.
1. Nobody owns the content
An intranet with no named owners fills up with stale pages within months. HR assumes IT owns it. IT assumes communications owns it. Policies go out of date and employees learn to ignore the site.
Fix: give every site and every page a named owner and a review date. Put the owner and "last reviewed" on the page itself. If a page is not reviewed by its date, flag it to the owner automatically.
2. Navigation copies the org chart
Staff do not think in departments. They think "how do I book leave" or "where is the expense form". A menu built on department names makes them guess which team owns the answer.
Fix: list the twenty tasks people perform most often and build the top navigation around those. Keep departments for team sites. Test the menu with five real employees before launch, asking each to find three things without help.
3. Search cannot be trusted
If the first result is a 2019 policy, people stop searching and start emailing colleagues. Poor search is mostly a content and metadata problem rather than a product fault.
- Archive or delete outdated files before migration, not after.
- Use managed metadata (document type, department, effective date) instead of relying on folder names.
- Add promoted results for the ten most searched terms.
- Review the search analytics monthly and fix the queries that return nothing.
Planning a SharePoint project? Talk to an expert
4. Permissions are either too tight or a mess
Two opposite problems appear. In the first, everything is locked down and people cannot find what they need. In the second, permissions were broken at item level so many times that nobody knows who can see what. The second is also a security risk, and it becomes serious once you switch on an AI assistant such as Microsoft 365 Copilot, which can surface anything a user is allowed to open.
Fix: manage access through groups, not individuals. Break inheritance rarely and record why. Run an access review before launch and again every six months.
5. The intranet is not where work happens
If people must leave Teams or Outlook to visit the intranet, they will not. News posts that nobody sees in their normal flow of work get no readers.
Fix: surface the intranet inside Teams as a tab or app, use the SharePoint news web part with email digests, and put the three most-used tools (leave, expenses, helpdesk) one click from the home page.
6. Mobile and frontline staff are forgotten
Field teams, factory staff and drivers often do not have a desk. If your intranet only works well on a large screen with a company login, a large part of your workforce is excluded.
Fix: test every key page on a phone, use the SharePoint mobile app, and decide early how staff without company email will sign in.
7. Launch is treated as the finish line
Most intranet budgets stop at go-live. The first three months decide whether habits form, yet that is when nobody is looking after the site.
- Week 1: a short announcement from a senior leader, and a quick-start guide.
- Weeks 2 to 4: weekly check of search terms and top pages, and fix what is missing.
- Month 2: interview ten users, retire what nobody opens.
- Month 3: publish what changed because of their feedback.
Want a second opinion on your intranet?
We will review your current site against these seven points and send you a short written summary.
Talk to usA pre-launch checklist
- Every page has an owner and a review date.
- Top navigation is built from tasks, and tested with five staff.
- Outdated content is archived before migration.
- Search has metadata, promoted results and analytics.
- Permissions use groups, and an access review has been done.
- The intranet is available in Teams and on mobile.
- A ninety day support and review plan has an owner.
If you are planning a SharePoint project in the Gulf, we cover bilingual and compliance points on our UAE SharePoint page. For approval flows on top of an intranet, see our guide to expense approval workflows.
Frequently asked questions
How long does a SharePoint intranet take to build?
A focused single-site intranet is measured in weeks. A multi-department or multi-language build takes months. Scope, content clean-up and approvals usually take longer than the build itself.
Is SharePoint a good choice for an intranet?
Yes, if you already use Microsoft 365, because identity, Teams, search and permissions are shared. It is less suitable if the main goal is a highly branded public-style site or if nobody will own the content.
Why do employees stop using the intranet?
The most common causes are out-of-date content, navigation that does not match how people look for things, and poor search. A visit to the site must save time compared with asking a colleague.
Do we need a custom design?
Usually not. The modern SharePoint templates cover most needs. Spend the budget on content structure, search and governance first, and add custom branding after.
A starting point is our intranet portal built on SharePoint.
You may also like

What a SharePoint intranet improves for a company on Microsoft 365: documents, approvals, search, security and reach. Plus where it falls short.

Practical SharePoint Online best practices: site structure, hub sites, permissions, metadata, the limits that matter and how to recover deleted files.

Modern SharePoint intranet solutions drive employee engagement, simplify collaboration, and maximize Microsoft 365 ROI for enterprises.
