Every game studio has one. The person who wakes up at 6 AM to check Discord. Who reads every Reddit thread. Who knows, viscerally, what players feel before any dashboard catches up.
That person is usually called a "community manager." They sit in marketing, or support, or sometimes in a department that doesn't quite have a name. They rarely attend leadership meetings. Their compensation reflects a "soft skills" role, not the strategic function they actually perform.
The data says otherwise
At every studio we've worked with, the community team's qualitative insights predicted churn signals 2-4 weeks before analytics dashboards flagged them. Not because the dashboards were wrong — because community managers read the texture of player sentiment that numbers flatten.
What we've seen work
The studios that get this right do three things: they give the community lead a seat at the product table (not as a guest — as a peer), they resource community tooling the way they resource game infrastructure, and they measure community health with the same rigour they measure DAU.
The studios that don't? They lose players to silence. Not bugs, not content droughts — silence. The feeling that nobody is listening.
The uncomfortable question
When was the last time your community manager presented directly to your CEO? If the answer is "never," you're leaving retention on the table.