Five user groups: production, office, field staff, warehouse, and management. A new employee app launches with enthusiasm, featuring a polished onboarding process and a well-stocked feed from day one.
Six months later, usage declines. The communications team is puzzled. The personalization works. The app functions as intended. The oversight? No one asked how much content each user group needs to keep their feed engaging.
The math nobody runs
In a unified feed, one message reaches everyone. Whether it reaches a hundred or ten thousand employees, the effort remains constant. This was the efficiency of internal communications for years.
Personalization disrupts this model. What matters to production is irrelevant to office staff. What leadership needs doesn’t resonate in the warehouse. Segmentation demands separate feeds for each user group, all needing regular updates.
The arithmetic is clear: five user groups, evenly distributed workforce, and a consistent content frequency goal. The team must produce five times the content to maintain the same density as a single unified feed. Add more variables like role, department, and region, and the demand multiplies.
Internal comms teams aren’t equipped to scale rapidly. They never were.
Decisions made in planning
The error occurs not in production, but earlier, before technology is even introduced.
Before architecture and design start, three critical questions require concrete answers:
How many user groups are necessary? Broad segmentation is tempting, but each additional group increases the content burden. Fewer groups result in denser, more valuable feeds, often a better decision.
How much content does each group need daily? This isn’t a guess. It’s a specific number. Teams that bypass this question end up scrambling to address it later, when metrics are already slipping.
Where does the content originate beyond the central editorial team? Department news, HR updates, curated external sources, user-generated contributions. Relying solely on the internal editorial team leads to a dried-up content stream.
Fast app launch, slow content production
Technically, personalization is quick to set up: configure user groups, assign channels, define permissions. This takes days, not months.
Content is trickier. Who in production has the time and access to contribute regularly? Who manages external content streams? How do you ensure feeds stay active after the initial launch excitement fades?
These are not IT issues. They involve editorial structure and organizational ownership.
The app launches well. that’s the problem.
Launches typically succeed. Teams prepare, fill channels, and early engagement numbers look promising. Then usage declines, steadily, because ongoing operations can’t sustain the initial launch effort.
This isn’t a platform failure. It’s a structural issue created during planning, which can’t be resolved in production without rethinking both content strategy and channel architecture.
Personalization suits organizations with diverse, distributed workforces. But it alters the foundational economics of internal communications. Teams that anticipate this and plan accordingly gain a significant advantage. Those who realize it too late struggle with declining engagement, using tools that perform exactly as designed.
