Most SharePoint intranets fail. Not because SharePoint is bad, but because they are built by IT teams for IT teams, filled with compliance documents nobody reads, and abandoned within six months.
I have built and rebuilt SharePoint intranets for organisations ranging from 50 to 5,000 employees. The ones that succeed share five characteristics. The ones that fail share the same three mistakes.
This guide covers both.
Why Most SharePoint Intranets Fail
Mistake 1: Starting with structure instead of use cases
The first question most IT teams ask is "How should we organise the navigation?" The right first question is "What do employees need to do every day, and how can the intranet make that easier?"
A SharePoint intranet should solve real problems: finding HR policies, submitting IT requests, accessing project documents, onboarding new starters. If it does not solve a real problem, nobody will use it.
Mistake 2: Treating it as a document dump
SharePoint is not a file server. An intranet that is just a collection of folders with PDFs is not an intranet — it is a slightly better shared drive. Nobody bookmarks a document dump.
Mistake 3: No ownership after launch
An intranet needs a content owner. Not IT. A communications or HR person who is responsible for keeping it current. Without this, the intranet becomes outdated within 90 days and people stop trusting it.
The Five Characteristics of a Successful SharePoint Intranet
1. A compelling home page
The home page is the first thing employees see. It should show:
- Company news and announcements (updated at least weekly)
- Quick links to the 5-10 most-used tools and resources
- A search bar that actually works
- A "What's new" section
Use SharePoint's News web part for announcements and the Quick Links web part for the top navigation shortcuts. Keep the design clean — no more than 3 columns.
2. Department hubs, not a flat structure
Organise content by department (HR, Finance, IT, Operations) using Hub Sites. Each department owns their section and is responsible for keeping it updated.
The IT team should own the overall governance and template, but content ownership must be distributed. This is the single biggest factor in long-term intranet success.
3. A working search experience
SharePoint search is powerful but requires configuration. Out of the box, it searches everything — including old files, draft documents, and content nobody should see.
Configure search to:
- Prioritise intranet pages over document libraries
- Exclude archived content from results
- Surface people profiles in search results (employees searching for colleagues)
4. Mobile-first design
In 2026, a significant percentage of employees access the intranet from their phone. SharePoint's modern pages are responsive by default, but you need to test every page on mobile and ensure navigation works on small screens.
Use the SharePoint mobile app to preview your intranet during design. If it is hard to navigate on a phone, fix it before launch.
5. Integration with Microsoft 365 tools
The best SharePoint intranets are not standalone — they are connected to the rest of Microsoft 365:
- Teams: Embed Teams channels in SharePoint pages for department discussions
- Power Apps: Embed apps for IT requests, expense submissions, or leave requests directly in the intranet
- Viva Connections: Surface the intranet in Teams so employees do not need to navigate to a separate URL
A Practical Build Plan
Here is a realistic timeline for building a SharePoint intranet from scratch:
| Week | Activity |
|---|---|
| Week 1 | Stakeholder interviews — identify top 10 use cases |
| Week 2 | Information architecture design — navigation, hub structure |
| Week 3 | Home page build and department hub templates |
| Week 4 | Content migration from old systems |
| Week 5 | User testing with 10-15 employees |
| Week 6 | Refinements based on feedback |
| Week 7 | Launch communications and training |
| Week 8 | Post-launch review and governance setup |
Governance: The Part Everyone Skips
The intranet will decay without governance. Before launch, define:
- Who can create new pages? (Recommended: only department content owners)
- Who approves news articles? (Recommended: communications team)
- How often is content reviewed? (Recommended: quarterly review of all pages)
- What happens to outdated content? (Recommended: archive, not delete)
Document this in a one-page governance policy and get sign-off from department heads before launch.
Ready-Made Templates
Building a SharePoint intranet from scratch takes weeks. I have put together a complete setup guide with templates, governance documents, and step-by-step configuration instructions:
SharePoint Intranet Setup Guide — $39
It includes the home page template, department hub structure, governance policy template, and a launch communications plan. Everything you need to go from blank SharePoint to a working intranet in a week.
AutomateHQ publishes practical Microsoft 365 and SharePoint guides for IT professionals and business owners.
