Internal communities: why the spaces employees create themselves work

The moment an intranet stops being an HR noticeboard and genuinely becomes "our place" is the moment employees can create their own spaces. A running group, a book club, a chess tournament, a corner for one city's office — none of it contributes to a business process, but all of it brings the system into daily life.

Why management shouldn't create them

Communities created top-down usually stay flat. The reason is simple: nobody makes time for a hobby that was assigned to them. Management's role here is not to create but to permit and to stay out of the way.

That doesn't mean abandoning control. A workable balance: anyone can create a community, membership is self-service, but an administrator can remove a community or a post when needed. Moderation exists but stays invisible; there is no approval process.

Why self-service membership matters

If joining requires asking someone's permission, most people won't join. Groups you can enter and leave with one click keep membership numbers honest: nobody stays because "it would look bad if I left".

That has a useful side effect: member counts measure real interest. An active running group of fifteen is a more valuable signal than a silent group of ninety.

Moderation: light but present

The most commonly voiced concern about communities is uncontrolled content. In practice the risk is overstated — in an environment where people post under their real corporate identity, they are already careful. Still, three plain safeguards are sensible:

1. Removal rights. An inappropriate post should be removable by its author and by an administrator. In a system where only the author can remove it, there is no way to clear inappropriate content.
2. Archiving. A dead community isn't deleted but archived; it stops cluttering the list while the history remains.
3. Clear rules. What isn't acceptable is written once and lives on the community page.

More than that does harm: a community where every post needs approval isn't a community.

Where it should stop

There are two kinds of content communities cannot carry. The first is official information: a policy change cannot be announced in a community post, because it won't reach everyone and won't be archived. The second is complaints and misconduct reports: those belong in a channel with genuine anonymity, not an open space — we cover it in our ethics hotline article.

Being clear about that boundary is also what keeps communities free. If official communication lives elsewhere, it's easy to keep the rules here loose.

Geographic and functional groups

The two most used community types come from work rather than hobbies. Location communities: a space where people in the same city or building share practical information — shuttle times, nearby places, building notices. Practice communities: people doing the same job across different departments — all store managers, all project leads.

The second is especially valuable: it cuts the vertical structure of the org chart horizontally and lets knowledge travel between departments.

Remote work and communities

Communities matter more in remote-heavy teams, because there is no corridor conversation. In companies that work mainly remotely, community participation correlates strongly with broader engagement measures.

The practical advice here is to make room for community activity in the calendar: a half-hour meet-up inside working hours gets far higher attendance than one scheduled after work.

Clearing the starting threshold

An empty community list is as discouraging as an empty wiki. Opening three or four communities during setup and seeding each with a post clears that threshold. Ideally they're opened by volunteer employees rather than HR — the tone of the first post sets the tone of everything after.

Budget and support

Most communities can live without a budget, but small support markedly raises participation: a few books for the book club, shirts for the running group, a prize for the chess tournament. The cost per person is low and the return is visible.

The governance question is how the budget is allocated. The most practical method is a transparent, small ceiling: requests up to a set annual amount are approved quickly. Support that requires a long approval process means most communities never ask.

Measurement

Three numbers show the health of communities:

• Active community ratio — the share with at least one post in the last thirty days.
• Breadth of participation — the percentage of employees who belong to at least one.
• Spread — how many different people the posts come from. A community written by one person isn't a community.

If all three are low, the answer isn't opening more communities but giving the existing ones time and visibility. General methods for sustaining participation are in our engagement article, and the rollout order in the 90-day plan.