An intranet redesign is a complete overhaul of your company's internal platform: information architecture, content, user experience, and often the underlying technology. It becomes necessary when the current intranet is no longer used, no longer maintained, or no longer matches how people actually work. And here is the part most redesign guides skip: a successful redesign is not about rebuilding the same intranet with a nicer interface. It is about not repeating what made the old one fail.
At Jint, we have spent eight years helping companies redesign intranets on Microsoft 365. The same pattern shows up every time: technology alone rarely kills an intranet. The model does. Here is the full method, with real numbers and the traps nobody warns you about.
Intranet redesign at a glance:
- Redesign when your intranet is unused, unmaintained, or impossible to search
- Answer the real question first: fix the existing platform or replace it
- Follow 6 steps: audit, user research, measurable goals, solution choice, pilot, rollout
- Plan 3 to 9 months depending on the scenario; budget depends on the model, not company size
- Avoid trap #1: rebuilding custom when custom already failed
What is an intranet redesign?
An intranet redesign is the structural revision of an existing intranet: how information is organized, what content survives, how the experience works, and which platform runs it all. It goes far beyond a visual refresh. Repainting a building with cracked foundations does not save it; redesigning an intranet means fixing the foundations.
A real redesign covers four workstreams:
- Rethink the information architecture: what employees look for, and how they find it.
- Review the content: archive what is obsolete, rewrite what matters, assign owners.
- Modernize the experience: design, mobile access, personalization by profile.
- Challenge the technical foundation: keep the current platform, or replace it.
That last point shapes everything else. It gets its own section below.
5 signs you need an intranet redesign
How do you know whether your intranet needs a redesign or just a refresh? Five signals leave little doubt:
- People stopped showing up. Monthly visits decline quarter after quarter, and information now travels by email or Teams, bypassing the intranet entirely.
- Finding information is a treasure hunt. The reference figure remains McKinsey's "The social economy" study: employees spend an average of 1.8 hours every day searching for and gathering information, nearly a full workday each week. The study dates back to 2012, but the problem has aged badly in the other direction: with more tools and more content, fragmentation has grown worse.
- Maintenance keeps getting more expensive. Every change requires a developer, every SharePoint update breaks something, and nobody dares touch the code anymore.
- Mobile is missing. Your frontline teams in stores, plants, or on the road simply cannot reach company information.
- AI cannot use it. Copilot and AI assistants find nothing useful in your intranet because the content is unstructured or outdated. In 2026, that is a warning sign in its own right.
Two or more signals? A redesign is no longer optional. The next question is which scenario to choose.
Fix it or replace it: answer this before anything else
Before talking mockups or features, settle the uncomfortable question: should you modernize the existing intranet, or replace the platform? The 2026 ClearBox report, which reviews 37 intranet and employee experience platforms, notes that organizations are taking longer over purchasing decisions as budgets tighten. Good news: a few objective criteria make the call much easier.
A useful benchmark: if your company already runs on Microsoft 365, replacing your intranet does not mean starting from scratch. A solution that plugs natively into SharePoint and Teams builds on what is already there: accounts, security, documents, habits. That is the scenario we defend at Jint, and it changes the budget equation entirely. If your current platform is a legacy SaaS portal, our guide on migrating to a SaaS intranet covers the migration path itself in detail.
The intranet redesign project plan: 6 steps
A successful intranet redesign follows a proven sequence. Here are the six steps we run with our clients.
1. Audit what you have, without complacency
Measure what is actually used: page views, internal searches, most-visited content. Identify the 20% of content that drives 80% of visits; everything else is a candidate for archiving. This audit grounds the debate in facts instead of opinions. Our intranet optimization guide gives you a structure for this phase.
2. Listen to users, not just stakeholders
The steering committee has convictions; users have habits. Talk to both. A handful of targeted interviews per population (HQ, frontline, managers) plus a short survey will surface the real friction points: failed searches, irrelevant news, no mobile access. Those verbatims become your success criteria. Nielsen Norman Group's research on intranet redesign makes the same point: user research upfront is what separates redesigns that stick from redesigns that get redone.
3. Set measurable goals
"Improve internal communication" is not a goal, it is a wish. Aim instead for: 70% monthly active users within 6 months, 80% of searches successful, internal broadcast emails cut in half. Numbers like these drive trade-offs during the project and prove ROI after it.
4. Write the specifications and choose your model
This is the decisive step. Start by formalizing intranet specifications: functional scope, audiences, security constraints, weighted selection criteria. A written spec keeps vendor conversations honest (our sample specifications document is a solid starting point). Then compare the three families of solutions: custom development, standalone platform, or a solution integrated into Microsoft 365. The deciding criteria: integration with your environment, 5-year total cost (licenses + maintenance + evolutions), autonomy for your comms team, and capacity to evolve. Our comparison of the best intranet platforms and our breakdown of what an intranet really costs give you the full grid.
5. Run a pilot before the rollout
Deploy first to a test population: one department, one site, one country. Four to six weeks is enough to validate the architecture, adjust content, and catch friction early. A successful pilot also produces your first internal ambassadors, the single most effective adoption lever we know.
6. Launch, communicate, and keep it alive
Going live is not the end of the project; it is the start of adoption. Plan an internal launch worthy of a product release: a communication plan, team relays, and a steady editorial rhythm from week one. Look at these corporate intranet examples: every successful one has an editorial team that keeps the platform alive.
Budget and timeline: what to actually expect
Let's talk money, since almost nobody does. The budget of an intranet redesign depends primarily on the model you choose, far more than on company size.
- Redesign with custom development: expect tens of thousands of dollars in services, then a recurring maintenance cost that grows with every SharePoint evolution. This hidden cost is what sinks custom intranets.
- Replacement with a standalone platform: add to the license cost the connectors to Microsoft 365, content migration, and double administration.
- Replacement with a Microsoft 365-integrated solution: a per-user subscription, deployment in weeks rather than months, and no technical maintenance, since the vendor ships updates continuously. The SaaS intranet model turns a heavy capital project into a controlled operating cost.
Here are the four redesign scenarios side by side:
One budget note for 2026: Microsoft 365 license costs have risen steadily in recent years. All the more reason to get full value from that investment by building your intranet directly on it, instead of paying for a parallel platform.
Trap #1: rebuilding custom when custom already failed
This is the mistake we see most often. The old intranet was a custom build that became impossible to maintain; and the redesign starts over... with another custom build. More modern, sure. But the cycle restarts: developer dependency, accumulating technical debt, dreaded version upgrades, and another redesign in five years.
The redesign is precisely the moment to break that cycle. An intranet built natively on Microsoft 365 with a software vendor like Jint reverses the equation: Microsoft runs the infrastructure, the vendor ships features and AI continuously, and your communications team gains autonomy. Your intranet CMS should be in the hands of the comms team, not a contractor. The real benefits of an intranet come from this capacity to evolve, not from a prettier homepage.
The test is simple. Ask your future vendor one question: "What happens when Microsoft updates SharePoint?" If the answer systematically involves a quote, treat it as a red flag.
What about AI?
You cannot redesign an intranet in 2026 without addressing AI. ClearBox confirms it in its 2026 report: driven by AI, the intranet is becoming the "front door" of the organization again. But in which direction?
Our position at Jint: a structured intranet is the foundation that makes AI agents work. An assistant like Copilot is only as good as the information it can reach. If your intranet is an attic of outdated content, AI will confidently serve outdated answers. If information is organized, governed, and current, AI becomes genuinely useful: reliable answers, natural-language search, role-specific assistants.
A redesign is the right moment to build that foundation: content governance, named owners, expiry dates, clean metadata. That is exactly how Jint Genius, our generative AI layer, works: it relies on a structured intranet to answer accurately. Priorities in the right order: tidy the house first, then bring in the agents.
Key takeaways
- An intranet redesign is a structural project, not a facelift.
- Decide "fix or replace" first, with objective criteria: platform health, maintenance cost, adoption.
- Follow the 6 steps: audit, user research, measurable goals, specifications and model choice, pilot, animated rollout.
- Judge budgets on 5-year total cost, maintenance included, not on the initial quote.
- Do not automatically rebuild custom: custom is often what made the old intranet impossible to maintain.
- Use the redesign to lay the groundwork for AI.
Is your intranet showing signs of fatigue? The Jinters can audit what you have, pinpoint what is blocking adoption, and show you how to redesign it on Microsoft 365 without starting from scratch. Request a demo.
.webp)
