An internal community rarely fails because of the tool. The Teams channel is created in five minutes, and the kickoff email almost writes itself. It gets hard in the second month, when the initial curiosity is gone and no one does the thankless, recurring work that keeps a community alive. That is what this is about.
A channel is not yet a community
A mistake I made myself: creating a place and hoping that exchange happens on its own. An empty channel is not an offer, it is a debt owed. People come back when they took something away last time: an answer, a shortcut, the feeling of not being alone with a problem. That does not come from the platform, it comes from people who feel responsible.
What holds for us
From the work as a community lead I take away a few things that prove more stable than any tool decision:
- A reliable rhythm carries further than the big event. A short, predictable slot every two weeks does more than an elaborate quarterly highlight. Reliability is what turned spectators into regulars for us.
- Responsibility has a name, not “everyone”. When everybody is accountable, in the end nobody is. It needs one or two people who feel accountable, including for the cleanup and the follow-ups.
- Contributing has to be cheap. Anyone who first has to build a perfect presentation will opt out. A quick question, a screenshot, two lines with a trick: that is what our exchange lives on. Visibly valuing small contributions does more than a formal award.
- Content solves today’s problem. Strategy slides do not help someone who is stuck right now. What counts is the concrete trick that helps somebody this afternoon.
- Backing has to be real. If management wants a community, it has to free up time for it, not just send a greeting at the start. Without that time, the rest is hard to sustain.
Most of it does not come from me anyway but from the group. Everyone brings experience from their own projects, and the sum of that adds up to a fairly useful picture.
What I no longer do
I have dropped a few patterns because they promised more than they delivered:
- The big bang at launch. A loud launch event brought numbers but no attachment. Better to start small and let it grow.
- Forcing participation. People who are there out of obligation contribute nothing and dilute those who show up voluntarily.
- Points and badges. Gamification did not replace the missing value. If the value is missing, no leaderboard will fix it.
- Watching the member count. A large, silent group looks good in the report and still says little about whether exchange is happening.
How I measure success
Not by the number of people who joined, but by a few quiet signals: do the same people come back? Are questions answered by other members instead of always by me? And the most honest test: does the community keep running when I am on holiday for two weeks? If it does, it has become a community and not a channel that hangs on a single person.
Building it is the quick part, keeping it alive is the longer work.
There is more about what I do professionally on the about page. If you are building an internal community yourself, or trying to get a stalled one moving again, I am happy to compare notes, ideally via the contact form.
