Intranet Redesign or Replace: How to Make the Right Decision

It's rarely an obvious call. A redesign is cheaper and faster on paper, but it can be money spent propping up a platform that was never going to carry the next five years. A replacement resets the foundations, but it's a bigger programme and a bigger change to absorb. 

Redesign or Replace: What Actually Differs 

An intranet redesign keeps your existing platform and reworks what sits on top of it: navigation, information architecture, design, content structure, search configuration. It's the right move when the technology is sound, and the problems are ones of experience and organisation. 

An intranet replacement changes the platform itself — the right move when the constraints you keep hitting are built into the product. Integration limits, performance ceilings, a mobile experience that can't reach frontline staff, an inability to support AI-driven search: no amount of redesign work fixes a foundation problem. 

Start With the Evidence You Already Have 

Before commissioning surveys, look at what your intranet already tells you. Zero-result searches show exactly where findability breaks down. The share of pages unviewed in twelve months reveals how much content you're carrying for no reason. Mobile traffic measured against the proportion of employees who don't sit at a desk exposes whether your frontline population is served at all. And the number of people who published anything in the last ninety days tells you whether the operating model still works, whatever the platform does. 

Most organisations can assemble this picture in an afternoon — and it sharpens every conversation that follows. 

Eight checks before you decide :

• Stakeholder feedback. Survey users and look for themes that recur across groups, not the loudest individual complaints. Consistent themes point to structural problems. 

• Usability. Test navigation, search and content organisation. Watch where people give up and ask a colleague instead. 

• Content. Audit for accuracy, duplication and gaps. Poor content follows you onto a new platform if you don't deal with it first. 

• Performance and scalability. If the setup struggles at today's volumes, it won't absorb the next few years of growth. That's a replacement signal. 

• Integration. Assess how well the intranet connects to HR, CRM, project, and document systems. Architectural integration limits are among the clearest arguments for replacing. 

• AI readiness. Can an assistant answer from your content with permissions respected? Is there one authoritative version of each policy, or four competing pages? Where the answers are no, they're usually no for architectural reasons — and this check now settles the decision more often than any other. 

• Cost. Compare both options fully, including the maintenance you already absorb and the replacement you may still have to fund later. 

• Business alignment. Ask not only whether the platform meets today's priorities, but whether it can flex as those priorities shift. 
  

Count what the current situation already costs 

The line most often missed sits outside both estimates: internal time spent maintaining and patching the platform, workarounds built in other tools, duplicated content effort across departments, and the productivity drain of people not finding what they need. Quantify that, even roughly, and the comparison becomes considerably more honest — and far easier to take to a finance team. 

The third path 

In practice, many organisations land between the two, deliberately. A phased replacement moves the highest-value scenarios — news, search, onboarding, frontline access — to a new platform first, spreading cost and change. A bridge redesign invests a contained amount in fixing the interim, which is legitimate on one condition: a decision date and budget line for the replacement, agreed from the outset. Without those, the bridge quietly becomes permanent, and you spend the money twice. 

Governance decides whether any path lasts 

Whichever route you take, governance is what makes the result sustainable. Ownership of the solution, content lifecycle, user experience standards and findability all need a named home and a working routine behind them. This is the step most often skipped, and it's why some intranets need rescuing again within three years of a major investment. It matters more than it used to: once AI assistants draw on your content, unmanaged and duplicated pages don't sit there quietly — they get surfaced as answers. 

Assess deliberately, cost both options honestly, and the decision makes itself. What you're aiming for either way is an intranet that remains a genuinely valuable resource for communication, collaboration and productivity across your organisation.