An intranet can become the best reference point for a growing company. It can also become a document graveyard, a never-opened homepage, and an internal communication promise that dies three months after launch.
An intranet can become the best reference point for a growing company. It can also become a document graveyard, a never-opened homepage, and an internal communication promise that fades away three months after launch.
This risk doesn't just come from the tool. Most "ghost towns" stem from poor framing: we want to centralize, but no one knows what to centralize. We want to inform, but teams keep searching in Teams, Slack, Google Drive, Notion, their inbox, or asking the colleague "who knows." We want to build connections, but the intranet becomes a top-down showcase, disconnected from real work.
Useful intranet communication cannot simply be decreed. It must be designed as an internal product, with users, priority problems, content rules, owners, and adoption metrics. For a structuring SME or a scale-up starting to multiply its teams, this is often what makes the difference between a living portal and a forgotten space.
A ghost intranet isn't necessarily empty. It can contain plenty of news, files, HR pages, and links. The problem lies elsewhere: employees don't trust it, don't consult it spontaneously, or don't know what it's for compared to other tools.
The most frequent causes are almost always organizational before being technical.
Visible symptom | Probable cause | Priority fix |
|---|---|---|
Few logins after launch | The intranet isn't linked to daily tasks | Start from the teams' recurring needs |
Contradictory information | Multiple tools remain sources of truth | Clarify which channel is authoritative by topic |
Outdated pages | No content owner is appointed | Assign an owner and a review date |
Too much top-down news | The intranet mostly talks about the company, not the work | Add useful access points, procedures, and decisions |
Ineffective search | Structure designed by department, not by usage | Organize content around on-the-ground questions |
The classic trap is believing that adoption will come with the launch communication. However, a nice "our new intranet is available" email is not enough. If the space doesn't resolve a concrete friction within the following week, users will return to their old habits.
Before choosing the sections, you must answer a simple question: at what moments should employees say to themselves, "I'm going to check the intranet"?
Effective intranet communication generally fulfills four missions. It helps find reliable information, understand what has been decided, access the right processes, and know who to contact. If it only publishes internal news, it competes with the newsletter, team meetings, or instant messaging.
In a growing company, the challenge is often to reduce repetitive requests. HR shouldn't have to answer the same question about time off ten times. Managers shouldn't have to search for the latest version of a procedure every week. Newcomers shouldn't rely solely on a colleague's availability to understand tools, rules, and priorities.
That's why it's better to frame the intranet in terms of internal "jobs to be done":
Find the official version of a document.
Understand the quarter's priorities.
Know how to request a purchase, an absence, or access.
Identify the right point of contact for a topic.
Consult important decisions without digging through conversations.
This approach avoids designing an intranet like a corporate tree structure. It transforms it into a navigation tool, which is much more useful for the teams.
If you are still at the stage of choosing functional building blocks, the article on the features that matter for an internal communication intranet can help you distinguish the essential from the superfluous.
An intranet becomes a ghost town when it lacks a clear territory. If the same information can be found in an email, a Teams channel, a Drive folder, and an intranet page, no one knows which version to believe.
The solution is not to delete all tools. A modern company often needs multiple channels. The difficulty lies in giving a specific function to each one.
For example, instant messaging works well for quick exchanges and coordination. The project management tool is used for task tracking. The drive is used for storage and document collaboration. The intranet, on the other hand, must become the source of truth for durable information: internal policies, processes, organizational charts, structural decisions, useful links, onboarding resources, and operating rules.
This distinction becomes even more important with remote work. When teams are distributed, implicit rules are no longer enough. Employees need to know where to find information without waiting for someone online to answer them. On this point, a clear framework for remote work and internal communication prevents the intranet from being just another tool in an already confusing stack.
A practical rule of thumb works well: if the information needs to remain valid for more than a few days, it probably deserves a place on the intranet. If it calls for a short discussion or immediate action, it belongs instead in a conversational or operational channel.
The homepage is often where the intranet loses its way. Many companies put news, a banner, a few buttons, and a message from management there. It's not useless, but it's not enough.
A homepage must answer the question: "What can I do here right now?"
To avoid the showcase effect, it must highlight the most useful access points: frequent requests, key documents, search, directory, procedures, internal tools, business shortcuts, and the latest important decisions. News can exist, but it shouldn't take up all the space if it isn't the teams' primary need.
In an SME or a scale-up, the homepage must also evolve according to profiles. A manager, a newcomer, a sales team, or an operational team don't always have the same urgencies. It's not necessary to personalize the entire space from the start, but you must at least avoid a generic page that speaks to everyone and truly serves no one.
A good test is to observe an employee who doesn't know the intranet and ask them to perform three common actions. If they hesitate, use the search unsuccessfully, or end up asking someone, the architecture needs to be reviewed.
The ghost intranet often appears after the launch, not before. The first few weeks are lively, then the content ages. Pages are no longer updated, news becomes irregular, owners change, and no one dares to delete old information.
Editorial governance doesn't need to be heavy. Above all, it must be explicit. Every important space must have an owner, a review frequency, and a validation rule. Without this, the intranet becomes an unmanaged archive.
Three questions are enough to frame any durable content: who is responsible for it, when should it be reviewed, and how do we know it's still true?
In some sectors, this logic isn't just a matter of convenience. For an industrial, food processing, or logistics company, obsolete internal information can have a direct impact on quality, safety, or compliance. Organizations working with specialized processes, such as cleaning and contamination control solutions for production lines, need reliable, accessible, and up-to-date procedures. The intranet must then function as a controlled access point for instructions, not just a simple news feed.
Governance must also include the right to delete. A living intranet isn't the one that accumulates the most pages, but the one that keeps the right information visible and removes the noise.
Many intranet projects fail because they want to cover everything from the start. As a result: the launch takes too long, needs change, teams lose interest, and the first version looks like a compromise between all requests.
A better approach is to launch a reduced but truly useful scope. For example: onboarding, directory, most requested HR processes, decision base, tool links, and an actionable homepage. Once these uses are adopted, you can expand to business content, team spaces, internal FAQs, or automations.
This product logic allows you to learn quickly. You observe what is consulted, what is searched for, what is missing, and what remains ignored. You improve the intranet based on real behaviors, not just from design workshops.
To avoid adding a platform that duplicates others, it's useful to map your ecosystem before deciding. The article on choosing an internal communication tool without stacking solutions provides a complementary framework to make this clarification.
An intranet doesn't become central just because it exists. It becomes central when managers, HR, leadership, and teams use it as a reference in their routines.
Practically, this means that important decisions must be published on the intranet, then relayed elsewhere with a link to the source. Answers to recurring questions must point to the official page, not to an improvised explanation in a private message. Team meetings must rely on the priorities and documents available in the shared space.
Adoption depends heavily on these micro-behaviors. If a manager continues to send documents as attachments, employees won't go looking for the official version. If HR answers every question without redirecting to the resource, the knowledge base will never become a reflex. If news published on the intranet is never mentioned during collective gatherings, it will remain invisible.
You must therefore plan a change management strategy, but also simple rules for contributors. For example: any new procedure must be published on the intranet, any document shared in a channel must link back to its source page, and any frequently asked question must enrich an internal FAQ.
Login statistics are useful, but they can be misleading. A traffic spike after launch doesn't prove that the intranet is creating value. Conversely, a highly consulted page can signal a problem if users keep returning to it because the information is confusing.
Good indicators combine usage, quality, and operational impact.
Indicator | What it reveals | Positive signal |
|---|---|---|
Searches with no results | Missing or poorly named content | Volume drops with improvements |
Outdated pages detected | Governance quality | Reviews are done on time |
Repetitive questions to HR or managers | Lack of informational autonomy | Recurring requests decrease |
Usage rate of key shortcuts | Homepage utility | Frequent access points are used regularly |
Qualitative feedback | Trust placed in the intranet | Teams say "I found it on the intranet" |
The most important phrase to hear isn't "I saw the intranet." It's "I know the reliable information is there."
You can also analyze the content that creates friction. If a procedure generates a lot of questions despite being on the intranet, it might be poorly written, too long, misplaced, or disconnected from the users' vocabulary.
AI won't save a poorly framed intranet. However, it can accelerate certain uses if the document base is clean and governed.
It can help rephrase procedures, summarize decisions, suggest answers from a knowledge base, detect similar content, flag potentially outdated pages, or facilitate natural language search. For a growing organization, these gains can be significant, especially when internal requests increase faster than support teams.
But AI amplifies the quality of the existing system. If the content is contradictory, unvalidated, or scattered, it risks producing unreliable answers. The priority therefore remains structuring: sources of truth, access rights, validation, content owners, and integration with tools already in use.
This is precisely where an audit can be useful. Before developing an intranet or adding an AI layer, you must understand information flows, pain points, tool duplications, and processes to automate.
What is a ghost town in intranet communication? It's an intranet that exists technically but is hardly used or isn't considered a reliable source. It may contain pages and documents, but employees continue to look for information elsewhere.
How do you get teams to adopt an intranet? Adoption comes first from utility. The intranet must solve frequent problems, like finding a procedure, understanding a decision, or accessing a tool. Then, managers and contributors must use it as a reference in their daily practices.
Should you prioritize news or practical resources? Both can coexist, but practical resources should often come first. If the intranet helps employees work faster and with less ambiguity, they will naturally return to check the news.
How often should an intranet be updated? Critical content must have a defined review date, for example, quarterly or biannually depending on the topic. News requires a regular editorial rhythm, but it's better to publish less often with consistency than to publish a lot and then stop.
Is a custom intranet better than an off-the-shelf tool? That depends on your use cases, your existing tools, and your integration constraints. An off-the-shelf tool may suffice for simple needs. A custom intranet becomes relevant if you need to connect specific processes, roles, data, or user journeys.
Avoiding a ghost town isn't about adding more features. You must define a clear mission, eliminate duplicates, assign responsibilities to content, create usage rituals, and measure the teams' actual trust.
For a structuring SME or a scale-up wanting to gain clarity, the intranet can become a concrete productivity lever. Provided it is treated as an internal product, not as a one-off communication project.
Impulse Lab supports companies in auditing their AI opportunities, designing custom web and AI platforms, automating processes, integrating with existing tools, and training teams. If you want to create a truly used intranet, or modernize an internal space that has become too vague, you can start with a simple diagnostic with Impulse Lab to identify high-impact uses before developing the solution.
Our team of experts will respond promptly to understand your needs and recommend the best solution.
Got questions? We've got answers.
Leonard
Co-founder
