Community as an Operating System: How I Structure 100 People Across Four Disciplines

When people hear “community team,” they usually picture a few social media managers with a scheduling tool and a crisis playbook. When I tell them I run a community organization of around 100 people, full-time staff and dedicated contractors, the first question is always the same. What do they all do?

The honest answer is that they run a growth engine. Not a channel, not a support desk, not a megaphone. An operating system that sits between Supercell’s games and the millions of people who play them, and turns player passion into superfans, and superfans into growth.

Here is how it is built, and why I would build it this way again from scratch.

The channel trap

Most companies structure community as a channel. It reports into marketing or support, it owns some social accounts and a Discord, and it gets measured on response times and sentiment. The people are often brilliant. The structure guarantees they stay reactive, because a channel can only ever carry what other teams decide to put through it.

The insight that changed everything for us is that community is not a channel. It is a relationship. And a relationship with millions of players needs more than communicators. It needs people who can decide what the moment should be, people who can produce it, people who can deliver it, and people who can amplify it. In most companies those capabilities live in four different departments with four different roadmaps. Every community moment becomes a negotiation.

So we brought them under one roof.

The four disciplines

Community. The strategic core. Our community managers set the standard for how Supercell’s games talk to their players, across the whole portfolio. They are not ticket-handlers. They are the people closest to player sentiment, and their job is to feed that signal into everything: what we make, what we say, and increasingly what ships in the games themselves. When players influenced Brawl Stars maps, modes, and skins, that was community managers doing their actual job, translating passion into product.

Creators. The creator and influencer ecosystem, from the program I built from zero to more than 290,000 creators to the partnerships that scale it. Creators are not a marketing channel we rent. They are partners whose success and ours are the same event. The program gives them revenue sharing, in-game visibility, training, and a real platform, and in return the games get reach we could never buy. Squad Busters drove more than 40 million pre-registration signups through this network alone.

Content. An in-house studio that produces the moments players actually want to watch. This is the discipline most community teams never get, and it changes everything. When the idea, the script, and the production sit next to the people who know the players best, you get formats like Brawl Talk, which started as an experiment with a community manager on camera and became core to how every Supercell game speaks.

Technology. An engineering and product team building the in-game surfaces that connect us directly to players. This is the part that surprises people most. We build software. The Community Hub puts our content, our creators, and our moments inside the game, in front of every player, with no algorithm in between. Owning that surface is the difference between hoping players see the moment and knowing they will.

One loop, not four teams

The structure only matters because of what it enables. It runs as one loop.

We shape the moment, produce it, deliver it to players inside the game, and creators carry it to the world.

Community decides what the moment should be, grounded in what players actually care about. The studio produces it. Technology delivers it in-game, to everyone, instantly. Creators amplify it to billions of combined subscribers. Then the loop closes: the reaction flows straight back to the community managers, and the next moment starts smarter.

When those four capabilities live in separate departments, the loop takes quarters. Under one roof, it takes days. That speed is not a nice-to-have. It is the whole advantage, because player passion is a real-time phenomenon. You either meet the moment or you watch it pass.

There is a number that keeps me honest about whether the loop works: engaged players show around two times the day-30 retention of players we never reach. The loop is not a brand exercise. It shows up in the metrics the business actually runs on.

What I would tell you if you have five people, not one hundred

You do not need 100 people to run this operating system. You need the four capabilities, at whatever scale you can afford, pointed at the same loop.

One person who owns player signal and decides the moment. One who can produce content players want, even if it is filmed on a phone. Whatever surface you control to deliver it, even if it is just the game’s news screen and a Discord. And a handful of creators treated like partners rather than a media buy.

The mistake is not being small. The mistake is splitting those capabilities across departments that each own a fragment of the relationship, then wondering why the community “channel” underperforms.

Community is not a support function, and it is not a channel either. Built properly, it is the operating system for the relationship between a game and the people who love it. Player passion goes in. Superfans, and durable growth, come out.