Employee App vs Intranet

The "mobile intranet" concept has sold well and delivered poorly for a decade, because the assumption behind it — that a shrunk desktop experience works on a phone — is mostly wrong. The employee app is a different product, shaped by different constraints (short sessions, shared devices, offline tolerance, bilingual needs, no company email). Companies that buy "one thing" expecting coverage on both populations end up with an intranet that a plant operator never opens and an app the corporate office finds limiting. Clarity on this distinction saves a tool-stack restart.

Take a 9,000-employee manufacturer. Corporate and engineering (1,800 people) need a traditional intranet — documents, collaboration, team spaces, project rooms, a searchable policy library on a laptop browser. The plant floor (7,200 people) needs an app — today's shift assignment, safety bulletin acknowledgment, a 30-second pulse, a shift swap request. The content shared between the two (company news, benefits, major announcements) can flow to both. The workflows specific to each don't cross. Teams that buy both and make the shared content layer consistent end up with 75% active usage on the plant app and 60% on the corporate intranet. Teams that buy one and try to force it across end up with 40% / 20%.

The honest trade-off: buying one unified platform saves on vendor management and creates a single place for company-wide content. Buying specialized tools per population produces better outcomes for each but higher coordination cost. The right answer depends on company size and workforce mix. Under 500 employees, a unified platform usually wins on cost. Over 3,000 with more than half deskless, specialized + integration usually wins on usage. The mistake is pretending the trade-off doesn't exist and choosing based on "what the RFP asked for" rather than the usage reality.

In healthcare, the distinction is nearly absolute. The clinical staff experience on a shared tablet at a nurse's station — quick handoff, patient alerts, shift-swap, immediate messaging — has almost no overlap with the corporate HQ's intranet experience (benefits admin, policy library, committee spaces). The hospitals that treat these as one project end up with a nurse-hostile clinical tool and a corporate-bloated intranet. The ones that treat them as one content layer with two optimized front ends — same source of truth, different experience for the two populations — get both to work.

By 2027, the AI assistant layer narrows the distinction somewhat. A plant operator asks "what's my schedule, and where's the current version of the torque spec SOP for line 6" and gets both answers from the same agent. A corporate engineer asks the same agent "what's the benefits enrollment deadline and can you show me the Q3 engineering all-hands deck" and also gets both. The AI interface is the same; the underlying content and permissions are the same. What still differs is the primary front end — a phone versus a laptop — and that difference stays material even in a copilot-first world.

• Shrinking the intranet homepage for phones. The phone's context is different enough that a responsive version of a laptop homepage is almost always wrong.
• Treating "one platform" as an absolute goal. The unified- platform preference is a tool-management preference, not a user-experience outcome.
• Measuring success by corporate usage only. Frontline and corporate adoption rates look different. One number hides the other half's failure.
• Ignoring the shared-device question. Intranet logins assume one user per account. Employee apps need a different identity model for shared tablets.
• Content team mismatch. The intranet content team writes corporate content. The employee app needs content designed for a 5-inch screen and a 30-second window. Same team, different craft.