Why Does It Look Like You’re Not Doing Anything?

If community just runs itself, what exactly are you for?

There’s a specific compliment that community managers receive sometimes, usually from a well-meaning stakeholder who has just spent fifteen minutes poking around the platform. It goes something like this: “Wow, the community is so active. It really just runs itself!”

They mean it kindly. They are beaming at you. And somewhere behind your professional smile, a small part of you is screaming. For multiple reasons.

One because we’re terrible at taking compliments.

Two… because you know what runs itself: a rock. A parking lot. A PDF. Communities do not run themselves. They run because someone is running them, and that someone has spent years getting good enough at the job that it no longer looks like a job. Congratulations. You have achieved professional invisibility.

This is not a metrics problem, exactly. We’ve been told for years that the solution is better measurement: track response times, post volume, engagement rates, NPS scores. And look, metrics matter. But dashboards haven’t solved the core issue, because the core issue was never about data. It’s alwways been translation.

The invisibility of community labor isn’t a measurement problem. It’s a legibility problem. The solution isn’t more dashboards; it’s learning to speak your organization’s language instead of asking your organization to learn yours.

Think about the building superintendent. In a well-run building, you never think about the super. The heat works. The pipes don’t rattle. The lobby is clean. The super is invisible by design, because the super is doing their job. But the moment the boiler breaks, suddenly everyone knows exactly who they are and what they do and why it matters.

Community managers are the super. Except we don’t usually have to deal with heating, cooling, or rattling pipes literally and unless things really go sideways leadership doesn’t always fully register that someone is down there running it. The better you perform, the more you disappear. It is a genuinely perverse incentive structure and I think about it more than is probably healthy.

So what do you do with that?

First, stop documenting only what happened and start additionally documenting what didn’t. A post count tells your leadership how many conversations occurred. It says nothing about the conflict that got quietly defused before it became a thread, the new member who almost churned after an awkward first post but didn’t, the question that got answered in four minutes instead of four days. Near-misses are data. Start treating them that way.

Second: stop asking leadership to learn community vocabulary. They won’t. Not because they’re incapable, but because they already have a vocabulary that works fine for them. If your organization is obsessed with churn, your community work is a retention play. If they care about pipeline, your users are warm leads. If they track support ticket deflection, your peer-to-peer answer threads are saving someone real money. The translation is your job. I know that’s annoying. But alas… it’s also true.

Third, make your labor visible before you need it to be. The worst time to explain what community management actually involves is during a budget review or, worse, a reduction in force. By then you’re playing defense. The case for your work - and YOU - should be ambient, woven into regular reporting, mentioned casually in team meetings, present in the room before anyone thinks to question whether you should be.

Here’s the part that’s hardest to say: a lot of us were trained, explicitly or culturally, to make hard work look effortless. To handle the crisis gracefully, clean up quietly, and never let them see you sweat. That norm made us better at the job and worse at keeping it. The community that “runs itself” is also the community that leadership looks at and thinks, hm, do we really need a full-time person or team for this?

The answer is yes. Obviously yes. But invisible labor doesn’t argue for itself. Don’t hide in the boiler room. Go introduce yourself. Tell someone what’s down there.