Why Most SharePoint Intranets Fail — and How to Build One 200+ People Actually Use
Lessons from a decade of SharePoint portal projects: the governance, information architecture, and adoption practices that separate thriving intranets from digital ghost towns.
Hammad Shahid
Power Platform, SharePoint & Copilot Studio Consultant · Microsoft Certified Trainer
I’ve built SharePoint portals since the 2010 era — on-premises farms, hybrid setups, and modern SharePoint Online. The technology has improved enormously. The reason intranets fail hasn’t changed at all: they’re built as IT projects instead of communication products.
The failure pattern
A typical failed intranet goes like this: IT provisions sites, migrates the file shares, announces the launch — and six months later everyone is back to email attachments. The intranet becomes a place where documents go to die.
The root causes are predictable:
- No information architecture. Sites mirror the org chart instead of how people actually look for things.
- No content ownership. Nobody’s job is to keep the news fresh or the policies current.
- No governance. Anyone can create anything, and within a year there are 400 sites and nobody knows which HR policy is the real one.
What works instead
Design around tasks, not departments
People don’t think “I need to visit the Finance department’s site.” They think “I need to submit an expense.” Your navigation and search should be organized around the top 20 tasks — which you discover by actually asking users, not by workshopping with stakeholders only.
Make the homepage earn its traffic
The homepage needs a reason to visit daily: targeted news, quick links that actually match each role, and the tools people use every day. SharePoint’s audience targeting makes this practical — use it.
Governance that enables, not blocks
Good governance is invisible: sensible site provisioning, clear content lifecycle rules, retention policies that run automatically. In my projects, a one-page governance model agreed before build beats a 40-page document nobody reads.
Launch is the beginning, not the end
The 200+ user portals I’ve delivered stayed alive because we planned for the second month: content owner training, a feedback channel, usage analytics reviews, and a steady drumbeat of improvements.
The modern advantage
Today, a well-structured SharePoint intranet has a bonus payoff: it becomes the knowledge base for AI. Copilot and Copilot Studio agents are only as good as the content they’re grounded in. A governed, well-organized intranet is the foundation for every AI initiative that follows.
Planning an intranet build or rescue? Get in touch — I’ve probably seen your exact situation before.