Every community has them: the handful of members who reply before you do, who welcome newcomers without being asked, who quietly keep a thread alive when nobody else is watching. You probably know their names already.
Most hub owners notice these members and think: I should thank them. Fewer think: I should give them a job.
That second instinct is the one that actually changes how your community scales.
Why Recognition Alone Isn't Enough
A member spotlight tells someone their contribution was seen. That matters—but it's a one-time acknowledgment, not an ongoing structure. The members doing the most unpaid facilitation work in your community deserve more than an occasional shout-out. They deserve a defined role that makes their contribution official, not incidental.
Without that structure, two things tend to happen. Either the member keeps contributing informally until they burn out, unsupported and unrecognized in any lasting way—or they quietly stop, because helping never seemed to be part of any real relationship with you, just something they did on their own time.
Both outcomes are avoidable. The fix isn't more gratitude. It's a role.
What "Giving Someone a Role" Actually Means
This doesn't require a formal ambassador program, a title with a stipend, or an HR-style onboarding process. It can be as simple as naming what someone already does and asking if they'd like to keep doing it, visibly, with your support.
A few examples of lightweight roles that require no new infrastructure:
Thread starter. A member who's good at sparking conversation gets a standing invitation to post one discussion prompt per month, credited under their name.
Welcome crew. A member who naturally greets newcomers gets tagged whenever someone new joins, so the welcome comes from a peer, not just from you.
Resident expert. A member with deep knowledge in one area of your community's focus gets flagged as the go-to person for questions in that specific topic.
Co-host. A member who's comfortable on camera or in live chat helps run part of your monthly session—even something as small as reading questions aloud.
None of these require a job description. They require you noticing a pattern that already exists and giving it a name.
Ask Before You Assign
The instinct to reward a great member by handing them more responsibility can backfire if it isn't actually wanted. Some of your most valuable contributors like helping precisely because it's informal—no pressure, no expectation, just genuine participation.
Before offering a role, ask directly. Something as simple as: "I've noticed you always make new members feel welcome—would you be interested in being an official part of our welcome crew? No pressure either way." This respects that contribution and structure are two different things, and not everyone wants the second.
Keep the Load Genuinely Light
The fastest way to lose a great volunteer is to let a small role quietly expand into a large one. A member who agreed to post one prompt a month should never end up moderating disputes or handling support requests they never signed up for.
Set the scope explicitly when you offer the role, and revisit it after a month. "Is this still feeling good, or is it more than you expected?" is a question worth asking directly rather than assuming silence means everything's fine.
A member who volunteers for something small and enjoys it is worth far more, long-term, than a member who takes on something large and quietly resents it.
What You Get in Return
Distributing small roles across engaged members does more than lighten your own load, though it does that too. It changes the texture of the community itself.
When members see that other members—not just you—are welcoming newcomers, starting conversations, and answering questions, the community stops feeling like a broadcast from one person to many. It starts feeling like a place with its own internal life, one that would keep functioning even on a week you're unavailable.
That resilience is not a small thing. A community that only functions when the founder is actively present is fragile. A community with two or three people quietly holding pieces of it together is not.
Watch for the Next Generation of Roles
As your community grows, the roles that made sense at 50 members won't necessarily fit at 500. A welcome crew of one becomes a welcome crew of four. A resident expert in one topic might need a counterpart for a second topic that's emerged as your community's interests have broadened.
Revisit your role structure the same way you'd revisit any other part of your community—every quarter is a reasonable cadence. Ask which roles are working, which have quietly become too much for the person holding them, and where a new gap has opened up that a member might be excited to fill.
Put It Into Practice
Name one member who already does something valuable for your community without being asked—welcoming people, answering questions, starting conversations.
Reach out this week and ask, directly, if they'd like that to become an official, lightweight role. Keep the scope small, and check in with them after a month.
Key Takeaway
The members already doing unpaid work to keep your community alive deserve more than a thank-you. A small, well-defined role turns informal generosity into something sustainable—for them, and for the community they're quietly holding together.
