Intranets and frontline teams: why the classic intranet fails

Does an intranet work for frontline teams?

Rarely — and it’s not a configuration flaw: it’s a matter of design. The classic intranet was built for a person seated at a desk, with an open session and a few minutes to browse the company news. A housekeeper between two floors, a cook in the middle of a rush, an order picker in a warehouse, or a nursing assistant on rounds has none of those three things. The tool isn’t hostile to them; it was simply never meant for them.

The numbers bear out this intuition. According to Arctus’s 2023 Observatoire de l’intranet — a benchmark study in France since 1999, conducted with 377 companies representing 4.2 million employees — 51% of organizations have unconnected employees, and 93% of those employees don’t feel the intranet concerns them. The top barrier to adoption isn’t resistance to change: it’s lack of time (48%), ahead of training (28%), skills (20%), and access (18%).

In other words, the intranet doesn’t fail on the frontline because teams are averse to technology. It fails because it asks them to stop, sit down, and read — when their whole job is precisely to keep moving. That’s the point of this guide: to understand why the classic company intranet fails frontline teams, what it still does well despite that, and which intranet alternative to replace it with for deskless workers.

Before criticizing, let’s set the definitions. A debate about the intranet quickly runs in circles if you conflate intranet, digital workplace, and enterprise social network.

What exactly is an intranet?

An intranet is an internal website, accessible only to members of an organization, designed to centralize company information: news, a directory, HR documents, memos, business resources. Its logic is first and foremost top-down and informational — the company publishes, employees consult. Historically, it opens in a browser on a workstation connected to the internal network.

It’s an old and useful category. For a support function, a head office, or a leadership team that wants to circulate a policy, a well-kept intranet remains a relevant tool. The problem isn’t the intranet as such; it’s the intranet turned into the backbone of work for people who don’t work at a desk.

Three neighboring terms are worth distinguishing, because they’re often used interchangeably:

• Intranet — an internal, top-down, informational site. You read on it. See the full definition in the glossary: intranet.
• Digital workplace — an integrated digital work environment where you both consult AND act (collaboration, tasks, processes, business apps). You work in it. See glossary: digital workplace.
• Enterprise social network (ESN) — a conversational, community layer centered on peer-to-peer exchanges. You talk on it. See glossary: enterprise social network.

These three objects partly overlap, and many modern platforms claim to cover all three. But the confusion has a cost: you buy “an intranet” thinking you’re equipping day-to-day work, and you end up with an information site nobody opens. So the useful question isn’t “do we have an intranet?” but “where does the work actually happen, and with which tool?”

What’s the difference between an intranet and a digital workplace?

An intranet broadcasts information; a digital workplace supports action. It’s the most important distinction in this guide, and it’s also the one most organizations haven’t yet crossed.

The number is clear. According to Arctus’s 2023 Observatoire de l’intranet, only 25% of companies have deployed a true digital workplace. The majority stay on older models: 37% run a classic information-and-communication intranet and 27% a community-based model. The digital workplace is gaining ground (+2 points in the 2025 Observatoire), but it remains a minority.

The decisive point lies elsewhere. In Arctus’s 2025 Observatoire de l’intranet augmenté (568 professionals, more than 500 companies), 94% of respondents rate their intranet as “necessary” or “indispensable” — a stable, high score. But when you look at what the intranet can actually do, the picture changes: operational functions (onboarding, workflows, embedded training) are present in fewer than 50% of organizations, and engagement functions (recognition, ambassadors, gamification) remain marginal.

Read those two numbers together. Everyone rates the intranet as necessary; but in more than one organization in two, it carries no real work function. It’s an accepted paradox: the intranet is judged indispensable the way a notice board at the factory gate is judged indispensable. You wouldn’t want to do without it. You don’t use it to do your job.

As the analyst Bertrand Duperrin, a French authority on employee-experience topics, puts it, “the intranet hasn’t disappeared, but it hasn’t reinvented itself yet either”. It’s still, he wrote in 2025, “conceived from headquarters for white-collar workers, with a digital-office logic that isn’t very inclusive”. That sentence holds the entire frontline problem in one line: the intranet is a thing designed from headquarters, for people who look like headquarters.

Why does the classic intranet fail on the frontline?

For five structural reasons that can’t be fixed by adding features. They stem from the tool’s starting point — the desk — and surface the moment you ask deskless teams to adopt it.

1. It assumes a workstation the frontline doesn’t have

The classic intranet assumes you open it on a screen, in a quiet moment. The frontline offers neither the screen nor the quiet. 91% of French people own a smartphone (CREDOC/ARCEP, 2025 Baromètre du numérique) and 80% use one daily; for a deskless worker, the smartphone isn’t a secondary channel, it’s the only device available. And making an intranet “responsive” doesn’t make it mobile-first: it’s a resized desk site, not a tool built for a hand holding a tray or pushing a cart.

2. It informs; it doesn’t drive action

The frontline doesn’t need to “read the company news.” It needs to know, at the start of a shift: what to do today, where the right version of the job aid is, and who to call if something goes wrong. A top-down intranet answers those three questions poorly, because it was designed to publish, not to frame a workday. When operational functions are absent from more than one organization in two (Arctus 2025), the intranet stays an internal newsletter — useful for the employer brand, useless in the rush.

3. It’s top-down, while the frontline is lateral

Operational information doesn’t only flow from headquarters to the frontline. It flows between locations, between teams, between the kitchen and the floor, between the night warehouse and the day warehouse, between the morning care team and the afternoon one. A purely top-down model ignores this lateral flow — which is exactly where the most information gets lost. See our pillar guide on internal communication for frontline teams on this point.

4. Nobody configured it for their job

The intranet is structured by a communications department or an IT team, along a tree that makes sense seen from headquarters. The frontline team inherits a structure it didn’t choose, in a vocabulary that isn’t its own. It doesn’t recognize itself in it, so it doesn’t make it its own. It’s the opposite of the “IKEA effect”: you don’t adopt a space you didn’t help build.

5. It competes with faster tools

While the intranet waits to be opened, information goes elsewhere: to WhatsApp for anything urgent, to the Drive for files, to email for memos. As a result, the intranet becomes the last place people look for information, because it has already circulated three times elsewhere. Average intranet user satisfaction, in fact, tops out at 6.5/10 (Arctus 2023) — a score that isn’t disastrous, but that describes a tolerated tool, not a loved one.

These five reasons share a common denominator, and it’s that denominator that really matters.

Three frontline scenes, the same failure three times

To make these five reasons concrete, take three situations in three different sectors. In a logistics warehouse, the night team needs to know the urgent shipping instruction left by the day team: it will never open an intranet to find it — the instruction ends up in a WhatsApp group, then gets lost. In a clinic, a nursing assistant needs the up-to-date protocol sheet before rounds: if the reference version lives on the intranet but the “real” latest version circulates by email, she’ll use the one she has at hand, not the right one. In a hotel, a seasonal hire brought on the day before has to figure out in ten minutes who to contact and where the service instructions are: an intranet structured by headquarters, in corporate vocabulary, is no help to him on his first day.

Three sectors, one and the same mechanism: the information exists somewhere in the organization, but not where the frontline looks for it, nor in the form it needs. The intranet didn’t lose the information — it filed it where the frontline never goes.

The real problem isn’t the intranet: it’s the patchwork of tools

The barely-used intranet isn’t an isolated anomaly. It’s one piece of a patchwork no one chose together, and that ends up coexisting without coherence. In a multi-location organization with a large frontline, you typically find, in parallel:

• WhatsApp for emergencies — where what’s said disappears, outside any framework, on personal accounts;
• a Drive for sheets and procedures — but the right version is on the account of someone who’s out sick;
• Excel for schedules — the up-to-date version is on the computer of a manager who’s off;
• email for memos — read by a fraction of the recipients;
• an intranet you open three times a year;
• paper — the staff photo board, checklists, instructions — that’s out of date.

Here’s the thesis of this guide, and it shifts the debate: the problem isn’t a missing tool, it’s that there are too many. A patchwork of tools doesn’t make a system. Adding “a better intranet” to this list solves nothing: you add a seventh place to search, when you should be removing six.

That’s why the right question isn’t “how do we modernize our intranet?” but “how do we consolidate into one place what’s scattered across six today?” The answer isn’t an intranet 2.0. It’s a change of category. And that’s where we have to talk honestly about the platforms that dominate the market.

Should you choose LumApps, Staffbase, or Workvivo?

These are excellent platforms — for a certain population, which isn’t necessarily yours. Let’s be fair: LumApps, Staffbase, Workvivo (by Zoom), Simpplr, Unily, Interact, and Firstup are among the Leaders in the 2025 Gartner Magic Quadrant for Intranet Packaged Solutions [international data]. Staffbase, Workvivo, Simpplr, and LumApps were already named Leaders in the Forrester Wave: Intranet Platforms, Q2 2024 [international data]. These products are mature, robust, and they do very well what they were designed for.

What they were designed for is internal communication at scale in large organizations. Broadcasting a company magazine to 20,000 people, orchestrating a multi-country HR campaign, measuring the engagement of a white-collar community: on that ground, these platforms are remarkable. Microsoft observes, in fact, that frontline workers’ use of digital tools jumped by +400% between March 2020 and November 2021 (Work Trend Index 2022) [international data] — the demand is real, and these vendors meet it at enterprise scale.

The point, then, isn’t that these platforms are bad. The point is that they’re poorly calibrated for the multi-location mid-market frontline, for three reasons:

1. They remain fundamentally top-down. Their native model is headquarters → employees: excellent for broadcasting, weak at getting a team working locally.
2. They assume a dedicated communications function and IT department. Their rollout is a project: editorial governance, integrations, change management. A mid-sized group of 8 hotels or a group of 15 restaurants doesn’t have that structure — and doesn’t want it.
3. Their richness becomes weight. What makes these platforms valuable to a large group (campaign modules, fine-grained segmentation, engagement analytics) is precisely what slows down and weighs on a frontline rollout that needs to be operational in two weeks.

If you’re seriously evaluating these options, our dedicated pages compare them point by point: Roomee vs LumApps and Roomee vs Workvivo. Our comparisons page lists all the evaluations.

The conclusion is simple: if your population is mostly office-based and you want to broadcast corporate communication at scale, these corporate intranets are a good choice. If your core works on the frontline, they answer the wrong question. What remains is to see what the right answer looks like.

What’s the alternative to an intranet for deskless workers?

A mobile-first operational workspace that each team configures itself and opens at the start of a shift. It’s a change of category, not an improved version of the intranet — and it’s exactly Roomee’s positioning: not an intranet, but an alternative to the classic intranet built for multi-location frontline teams.

The difference boils down to one sentence. An intranet answers the question “what’s the company news?” An operational workspace answers three concrete questions, the ones a frontline team actually asks:

• Where do I find the information I need right now?
• What do I do today, at the start of my shift?
• Who’s responsible for what, if something goes wrong?

It’s an operational promise, not a feature catalog. And that’s what sets a workspace apart from a mere aggregator: it doesn’t just gather tools together, it makes the team self-sufficient in its work. Concretely, this rests on four principles.

Natively mobile-first, not “responsive”

The tool is designed first for the smartphone — the frontline’s only device (91% ownership, CREDOC/ARCEP 2025). That changes everything: useful notifications rather than intrusive ones, access in a few seconds, sign-in without a work email (the frontline often doesn’t have one), no imposed MDM install. It isn’t a resized intranet; it’s an app built mobile-first for people on the move. See Roomee on mobile.

Configured by the team, no IT

Rather than a tree imposed by headquarters, each team configures its own space: it chooses its tabs, names its drives (“Job aids,” “Hygiene,” “Service instructions”), structures its org chart. It’s the IKEA effect applied to work: you adopt a space you helped build. And since nothing goes through an IT ticket, deployment is counted in days, not months. See Roomee Studio.

A place to act, not just to read

The space brings together what was scattered: the Feed (the day’s briefs and instructions), the Drives (the right version, always in the same place), the Org Chart (who does what), and framed Messaging (urgency, but within a framework, not on personal accounts). You don’t consult the company there: you get through your day.

Opened at the start of a shift, not three times a year

This is the decisive test. An HR intranet, you open three times a year — for your time off, for a management memo, for mandatory training. An operational workspace, you open every day, at the start of a shift, because it holds what you need to work. Usage frequency isn’t a marketing goal: it’s the mechanical consequence of a tool that genuinely helps.

A note on built-in help: Roomee’s Noah assistant can search the space’s content, answer from it (and cite its sources), and translate a piece of content at the user’s request — useful when a team speaks several languages. It’s a tool for reaching existing information, not a substitute for organizing the space.

Classic intranet or operational workspace: the comparison table

The table below sets the two models side by side. It’s not about pitting a good tool against a bad one, but two designs answering two different questions — one built for the desk, the other for the frontline.

The decisive row is “actual usage frequency.” Everything else follows from it: a tool you open every day doesn’t need its adoption forced; a tool you open three times a year will always remain a project to relaunch.

Why a “mobile intranet” isn’t enough

Many vendors now offer an “intranet app” and present it as the solution to the frontline problem. It’s a half-answer, and it’s worth understanding why before you invest.

Making an intranet accessible on mobile solves a device problem, not a design problem. If the model stays top-down — headquarters publishes, the frontline consults — then the app is just a mobile window onto a desk site. You’ve moved the pixel, not the logic. The employee can now read the company news from a smartphone, but still doesn’t find there what’s needed to get through the day.

Three differences separate a “mobile intranet” from a natively mobile-first workspace:

1. The starting point. The mobile intranet starts from a desk site you adapt; the mobile-first workspace starts from frontline use you equip. The two don’t arrive at the same product, because they didn’t start from the same place. That’s the whole stake of mobile-first design.
2. The purpose. The mobile intranet remains a tool for reading; the workspace is a tool for acting. A reading app, however polished, doesn’t become the tool you reach for at the start of a shift.
3. Sign-in. A company intranet often assumes a work account and email. The frontline doesn’t always have them. A tool built for deskless workers has to allow a simple sign-in, with no IT prerequisites, on the person’s own smartphone.

So the question to ask any vendor offering “a mobile intranet” is simple: “is this a resized desk site, or a tool designed for the frontline from the start?” The answer changes everything.

One practical signal settles it: watch the spontaneous open rate. If the app is opened only when a notification pushes you to it, it’s a mobile broadcast channel — an intranet in disguise. If the team opens it on its own at the start of a shift, without being made to, it’s because they find there what they need to work: it’s a workspace. This distinction isn’t theoretical. As early as 2022, Microsoft observed that 55% of frontline workers had learned to use a new technology with no training at all (Work Trend Index 2022) [international data]: the frontline adopts quickly what serves it, and just as quickly ignores what doesn’t. No change-management campaign durably makes up for a tool that doesn’t answer a need in the day.

How to move from intranet to operational workspace: the method

Migrating doesn’t mean tearing everything down. Here’s a five-step progression that consolidates the patchwork instead of adding a layer to it. It holds for a group of restaurants as much as for a network of warehouses, a hotel group, or a set of clinics.

Step 1 — Map where the information actually lives

Before buying anything, list every place operational information circulates today: WhatsApp groups, Drives, Excel files, inboxes, the intranet, paper binders. This map almost always reveals the same thing: dispersion, not scarcity. It’s the diagnosis that justifies consolidation.

Step 2 — Identify daily-frequency content

Separate what needs to be consulted every day (briefs, the day’s instructions, job descriptions, schedules, who to contact) from what’s occasional (time off, HR memos, the internal magazine). The daily content should migrate first to the workspace; the occasional content can stay on your existing intranet if you have one. You don’t replace the intranet by force: you take off it what should never have been there.

Step 3 — Let each team configure its own space

This is the step that determines adoption. Rather than imposing a structure, let each team name its drives, choose its tabs, organize its org chart. A team that built its space opens it; a team that inherited one ignores it. This autonomy is also what makes a fast rollout possible, without a centralized IT project.

Step 4 — Roll out location by location, not big bang

Start with a pilot location, watch the daily open rate (the only indicator that really counts), adjust, then expand. A successful frontline rollout is measured in days per location, not months for the whole. See how other groups did it on the customers page.

Step 5 — Frame urgency to empty WhatsApp

As long as urgency runs through WhatsApp on personal accounts, information keeps leaking and disappearing. Give urgency a framed channel inside the workspace — messaging that stays within the organization’s perimeter. This is often the step that completes the migration, because it dries up the main source of dispersion.

And what about compliance in all this?

It’s a decisive argument for leaving the patchwork, and it’s too often pushed into the background. When operational information circulates on WhatsApp and personal Drives, the organization loses both control and traceability of data that may fall under the French Labor Code (articles L1121-1 and L1222-4) and, in some sectors like healthcare, under professional confidentiality. An employee’s departure then takes with it the history of exchanges and the “right version” of the files.

The legal framework is explicit. The GDPR requires the employer to identify the legal basis and purpose of each data-processing operation; yet professional exchanges that pass through personal WhatsApp accounts inherently escape that control. The French Labor Code also governs the tools made available to employees (articles L1121-1 on proportionality, L1222-4 on prior notice). And the REEN law of November 15, 2021 encourages organizations to rationalize their digital usage rather than pile up tools — a further argument in favor of consolidation over the patchwork.

An operational workspace under the organization’s control restores that framework: the data stays within the company’s perimeter, not on personal accounts. On the hosting side, Roomee’s product data is hosted in Europe (Frankfurt) and the platform is designed to support GDPR compliance. ISO 27001 certification is underway, targeting Q3 2026. This point deserves a page of its own; here it’s enough to remember that getting information out of makeshift workarounds also means putting it back within a framework — and that compliance, far from being a side cost, is one of the soundest reasons to leave the patchwork.

What the classic intranet still does well

To stay fair, it has to be said: the intranet isn’t a bad object, it’s a misplaced one when you make it the backbone of the frontline. For some uses, it remains relevant — and acknowledging that strengthens, rather than weakens, this guide’s central argument.

• Corporate communication at scale. Broadcasting a vision, a policy, an internal magazine to a large office-based population: the intranet — especially the Gartner 2025 Leader platforms — does this very well.
• Reference document storage. The company’s HR, legal, and regulatory documents belong on a structured, governed intranet.
• White-collar sense of belonging. For sedentary teams, the intranet can be a useful cultural rallying point.

So the message isn’t “get rid of your intranet.” It’s: don’t ask a desk tool to carry the work of the frontline. For many organizations, the right architecture combines a lightweight intranet for occasional corporate communication and an operational workspace for the day-to-day of frontline teams. The latter isn’t a version of the intranet — it’s what takes over where the intranet could never reach.

In summary: replace rather than modernize

The classic intranet fails on the frontline not for lack of quality, but for lack of destination: it was designed from headquarters, for white-collar workers, in a desk logic. The Arctus numbers bear it out — 51% of companies have unconnected employees (2023), the intranet is rated necessary by 94% of organizations but carries operational functions in fewer than half of them (2025). The tool informs; it doesn’t get work done.

The real problem, though, isn’t the intranet in isolation: it’s the patchwork — a barely-used intranet, WhatsApp, Drive, Excel, email, paper — that doesn’t make a system. Adding a better intranet to this list, or doubling it with a corporate platform calibrated for large accounts (LumApps, Staffbase, Workvivo), doesn’t solve the dispersion. The operational answer is to consolidate into a mobile-first workspace that each team configures itself and opens at the start of a shift.

That’s the category Roomee stands for — not one more intranet, but the alternative to the classic intranet for multi-location frontline teams. To see the product in detail, start with the product page or Roomee on mobile. And to place Roomee against corporate intranets, browse the comparisons.