Somebody said it in passing, in a thread about something else, and you almost missed it. "I could probably do a session on that if people wanted."
You replied with a nice emoji and moved on, because you were tired and because the idea of coordinating somebody else's session felt like more work than just running it yourself.
Go back and find that message. That person just offered you the single best structural upgrade available to a small community, and it costs you about ninety minutes to set up.
What changes when a member hosts
The obvious benefit is your calendar. A member-led session is an hour of programming you did not have to prepare, and if you build a rota of four hosts you have covered a third of your year.
But the calendar is not the interesting part. Here is what actually changes.
When you run every session, the community is a place people come to receive things from you. Attendance is a form of consumption. However warm it is, the shape of the relationship is one to many, and the ceiling on it is your energy.
When a member runs a session, the room becomes a place where people contribute. Everybody watching learns something new: that this is a room where you can stand up. And the host themselves is transformed. Somebody who has hosted a session in your community will almost never quietly cancel their membership. They have skin in the place now.
Also, and this genuinely matters, your members are often better than you at specific things. You built the room. You do not have to be the most knowledgeable person in it about every subject, and pretending otherwise is exhausting and a bit sad.
The two ways this goes wrong
Before the how, the two failure modes, because both are avoidable.
The first is the session held in thin air. You put out an open call, one enthusiastic member says yes, you announce it vaguely, and four people show up to a talk that runs forty minutes over. The host feels humiliated. You feel guilty. Nobody volunteers again for a year.
The second is the pitch. A member hosts a lovely session that spends the last ten minutes selling their coaching package to your members. Everybody feels used. Twice as bad because you invited it.
Both come from the same root cause, which is not writing anything down. So let us write things down.
Start with one format, not an open call
Do not announce that members can host events. That produces silence, and then it produces one person you cannot say no to.
Instead, invent one small format and personally invite specific people into it.
Formats that work reliably at small scale: a twenty minute "how I actually do this" walkthrough, where somebody shows their real process rather than a polished presentation. A member hot seat, where one person brings a problem and the rest of the room helps. A "what I got wrong" session, which is consistently the most loved format in any community I have seen. A regional coffee call hosted by whoever lives in that time zone. A book or resource discussion where the host has done the reading and prepared four questions.
Notice these are all small, short, and low production. Twenty minutes with no slides is much easier to say yes to than "would you like to run a masterclass," which sounds like a month of work.
Pick one format. Give it a name. Then ask three specific people, privately, one at a time.
Ask in a way that is easy to accept
The invitation matters more than anything else here. Two rules.
Be specific about what you are asking for. Not "would you like to host something." Instead: "Would you run a twenty minute walkthrough of how you handle client revisions? Thursday the fourteenth, no slides needed, I will host the room and handle everything else. You just talk and answer questions."
And give them an easy exit. "Completely fine to say no or not now, it will not be weird." People say yes far more often when refusing is genuinely painless.
The person to ask first is not your most confident member. It is the one who explains things well and clearly enjoys the subject. Confidence is the thing the format is going to give them.
The one page host brief
Write this once and reuse it forever. It should take a host four minutes to read.
What the session is: format, length, and the one thing an attendee should leave with.
The date, the time with a time zone written out, and where it happens.
What you handle: the announcement, the reminders, opening the room, timekeeping, moderating questions, and dealing with anything awkward. All of that stays with you. Say so explicitly, because the fear of having to manage a room is what stops most people from volunteering.
What they handle: turning up prepared and talking about the thing.
What is not allowed: no selling, no discount codes, no "I have a course on this if you want the full version." One clean sentence about it, framed warmly. "You are welcome to say what you do for a living in one sentence at the start. Please do not pitch anything, and I will happily plug your work myself if it comes up naturally."
That last construction is the trick. You are not just banning promotion, you are offering to do the promoting on their behalf, which is more effective for them anyway and removes the temptation entirely.
The rules that protect everybody
A few lines that belong in every brief, and that most people only add after something has gone wrong.
Recording is not automatic. Ask the host first, in writing, and tell attendees at the start that it is being recorded. If anybody objects, either do not record or record only the host's portion. Someone who came to ask a vulnerable question in a private room did not agree to be in a library.
The attendee list is not the host's to keep. This one comes up more than you would think. A host does not get a list of who attended, does not get anyone's email address, and does not follow up with attendees individually unless a specific person asked them to. If a host requests the list, the answer is a friendly no. Your members joined your community, not the host's mailing list.
The host gets no special access to member data. Hosting a session is not a moderator role. It does not come with admin permissions, a view of anybody's billing, or your login. Especially not your login, ever, for any reason.
And you stay responsible for conduct. If somebody is unpleasant during a member-led session, you handle it, not the host. Make that explicit so the host never has to weigh whether to intervene.
What you still own
Three things do not delegate.
The announcement. You write it, in your voice, and you make it sound genuinely exciting, because a member's session announced flatly by you will feel second tier. Announce it exactly as warmly as you would announce your own.
The audience. You bring people. If four people show up because you posted about it once, that is your failure and not the host's, and you will feel awful. Post about it three times, mention it in your newsletter, and personally message five people who would love it. A member's first hosting experience should be a good one.
The thank you. Publicly, specifically, immediately afterwards. And privately as well, the following day, with one concrete detail about what worked. That private message is what turns a one time host into somebody who offers again in six weeks.
Should you pay hosts?
For a short, informal, member-to-member session inside a community they already belong to, a warm thank you and genuine visibility is usually the right exchange, and most people are delighted by it.
Once it becomes bigger than that, pay. If somebody is preparing a real workshop, doing hours of work, or hosting on a repeating rota that has become a commitment, then it is labour and it should be recognised as such. A fee, a free or reduced membership for a defined period, whatever is honest and sustainable for you. Say what the exchange is up front rather than letting a fuzzy gratitude arrangement drift into resentment.
And keep it consistent. Paying one host and not another for the same work is the kind of quiet unfairness that people notice and never mention.
The first one will be smaller than you hope
Expect it. The first member-led session in a community's history usually draws fewer people than your own sessions, because members have not learned yet that these are good.
Do not read that as a verdict. Run three. By the third, attendance normalises and something else has happened: two more people have quietly decided they could do one too.
Ending a format gracefully
If a format stops working, retire it cleanly and say why, in one warm sentence, and thank everybody who hosted. "We are going to rest the walkthrough series for a while and try something new in the autumn." No format needs to run forever, and a community that can retire things without drama is a healthy one.
The mistake is letting it fade out, so the last host is left wondering whether theirs was the one that killed it. That is a small cruelty and it is easy to avoid.
Do this this week
Invent one format. Name it. Twenty minutes, low production, no slides required.
Write the one page host brief. What it is, when, what you handle, what they handle, no pitching, no attendee lists, recording only with consent.
Go back and find the member who said "I could do a session on that." Ask them, specifically, with a date, and make refusing easy.
Then over-promote it, thank them publicly and privately, and watch what happens to the room. There is a particular energy in a community the first time a member runs the session, and you will feel it immediately. It is the feeling of the place becoming theirs, which is what you were building the whole time.