Replace Your Intranet, or Put an AI Assistant in Front of It? A Twenty-Question Test

Do not replace your intranet with a chatbot until you know which problem you have. Take the twenty questions asked most often in your chat channels and look each one up in the intranet as an ordinary employee would. If the answer is missing, no assistant will fix that. If it is there but nobody finds it, put an assistant in front of the intranet and keep publishing in it. If it is found but old or ownerless, fix ownership first. Replace the platform only when it cannot be a trustworthy source.
Sort twenty real questions
Pull the twenty questions that repeat most in your HR, IT and operations help channels. Search for each answer in the intranet as an ordinary employee and not as an administrator, and sort what you find:
| What you find | What it means | What to do |
|---|---|---|
| The answer is missing, or lives only in chat | A content gap: the knowledge sits in people | Write the page and name an owner. No tool change helps. |
| The answer exists but nobody finds it | A retrieval problem: titles, folders or search | Put an assistant in front of the intranet and keep publishing in it. |
| The answer is found but old, or has no owner | A trust problem | Give the page an owner and a review date before any assistant cites it. |
| The answer is found and right, yet people still ask in chat | A habit or placement problem | Answer in chat with a link to the page, or bring the assistant to the chat tool. |
Only the second and fourth rows are jobs for an assistant. A taxonomy shows why the second one happens. HR files the parental leave policy under "Benefits" while the employee searches "Time Off," so the page exists and is never found. An assistant that reads pages by meaning closes that gap, but it cannot write a page that was never written, and it will cite a stale page as confidently as a current one.
Keep the intranet and put an assistant in front of it
We recommend this path for most companies. The intranet is where owners publish, version and permission official content, and an assistant that retrieves from it inherits that structure. Replacing the platform moves the content without fixing it, and an unowned page stays unowned in the new tool.
If your intranet is SharePoint, fronting it can mean using what Microsoft is rolling out inside SharePoint itself. Copilot in SharePoint lets people ask questions about SharePoint content in natural language, and it requires a Microsoft 365 Copilot license. Run your twenty questions through it before you evaluate anything else. For a wiki and Drive folders, use an assistant built on retrieval-augmented generation, which looks up the relevant pages and answers from them, so it can show the page it used and the reader can check it.
Write each answer once, in the intranet, and link to it from chat. GitLab describes the habit in its handbook usage guide: communicate a change by changing the handbook and not by presentation, email or chat message, and cross-link instead of repeating content, so there is one copy to keep current.
Before you connect an assistant, remove contradictions. If three pages give three expense policies, the assistant will quote all three. Archive duplicates and superseded versions, but ask the owner before archiving a page nobody opens, because rarely opened pages often cover annual or emergency work. Name a canonical owner per topic, such as HR for the handbook, Engineering for architecture and Sales for pricing. Kipwise's internal knowledge base guide lists an efficient structure and a culture of feedback among its maintenance practices, and owners with review dates are what make both real.
Then connect the sources people actually use: the wiki, Drive or SharePoint, the chat tool and the ticketing system. Ask the vendor how fast an edit reaches the assistant, and test it by changing a page and asking again. Put the assistant where people already ask, in Slack or Teams, so that nobody has to visit a new portal.
When to replace the intranet
Replace the platform when it cannot serve as a trustworthy source for people or for an assistant: pages cannot be restricted by group, so confidential and public content mix; content is scattered across several portals with no way to search them together; or the product is being retired or costs more than the problem it solves. Even then, move the pages that answer your twenty questions first and rebuild them with owners and review dates, and archive the rest. A migration is the one moment when every page gets looked at, so use it as the review.
Run it safely
- The assistant must read with the permissions of the person asking. If a page is restricted in the intranet, it stays restricted: a finance projection the employee cannot open must not shape an answer.
- When it cannot find an answer, it should say so and offer to route the question to a person, such as the IT helpdesk, and not guess.
- A downvote on an answer should reach the page owner, because repeated failures on one topic show which page to fix.
- Check that your vendor does not use your internal data to train its models and that prompts and retrieved documents are encrypted in transit and at rest.
Measure against your own baseline
No resolution rate is right for every company, so set yours from a baseline. Before you change anything, count the repeat questions in your help channels for two weeks and note the intranet's zero-result searches if it reports them. After the assistant is live, re-run the twenty questions and recount. Falling repeat questions mean it is working. The questions it cannot answer are your documentation backlog, and when it fails, the cause is often a missing or poorly structured page and not the model.
Do not spend another quarter redesigning your intranet homepage. Pull the twenty questions this week and sort them into the four rows above.
-p-1080.jpg)


