Ask most hub owners what makes a community feel alive, and live sessions come up almost immediately. A scheduled call, real voices, real-time back-and-forth. It's easy to assume that energy is the thing worth chasing more of.
But a lot of a community's best thinking never happens on a call at all. It happens in a thread that stays open for a week, where people reply when they actually have something worth adding—not when a calendar invite tells them to.
What Live Sessions Are Genuinely Good At
Live conversation has real strengths that nothing else fully replaces. It creates a shared sense of presence—people experiencing something together, at the same moment, which builds a kind of relational warmth that text alone struggles to produce. It's also fast: a complicated misunderstanding that might take three back-and-forth messages to untangle in writing can often be resolved in ninety seconds of actual conversation.
None of this is in question. The issue isn't that live sessions are bad. It's that they're not the only format worth building your community's depth around, and treating them as the default for every kind of conversation leaves a lot of value on the table.
What Live Sessions Are Quietly Bad At
A live call has a hard limit that's easy to overlook: everyone has to show up at the same time, in the same place, ready to think about the same topic, right now. That constraint filters out a meaningful portion of your community before the conversation even starts—people in different time zones, people whose schedules don't align that day, and people who simply think better with time to reflect than they do improvising out loud under mild social pressure.
It also compresses depth. A ninety-minute call might touch on eight different points, none of them explored as fully as they could be, because the format keeps moving whether or not everyone's caught up. A thread has no such clock running.
What an Async Thread Actually Offers
A pinned, open-ended discussion thread solves for a different kind of contribution. Someone can read a question, sit with it for a day, and come back with a genuinely considered answer instead of whatever comes to mind fastest under time pressure. Someone in a different time zone can participate as fully as anyone else, on their own schedule, without ever feeling like they missed the real conversation because they weren't there live.
Depth doesn't always need speed. Sometimes it just needs room.
There's also a compounding effect that live calls don't share. A thread stays visible and readable long after the original conversation happened. A new member browsing your community a month later can read the entire exchange, follow the reasoning, and add their own perspective to something that's technically still open—something a recording of a live call rarely invites in the same way.
When to Reach for Each Format
The choice isn't which format is better in the abstract. It's which format fits the specific kind of conversation you're trying to create.
Reach for a live session when the goal is relational warmth, quick troubleshooting, or a moment that genuinely benefits from real-time energy—a celebration, an open Q&A where speed matters more than depth, a moment where hearing tone of voice adds real information.
Reach for an async thread when the goal is considered input from people who think differently under different amounts of pressure, when time zones would otherwise exclude a meaningful portion of your community, or when the topic benefits from staying open and revisitable rather than concluding the moment the call ends.
Give Threads the Same Intentional Design as a Live Session
Part of why live sessions feel more valuable is that they're usually planned with more care—a topic, a rough structure, sometimes even prepared questions. Threads often get none of that. A vague prompt gets posted and left to fend for itself, so it's no surprise it generates less than a well-planned call would.
Treat a thread you actually want to generate depth the same way you'd treat a live session you're hosting. Give it a specific, well-framed question rather than something broad. Check back in over the following days to add a follow-up or highlight a strong response, rather than posting it once and abandoning it. A thread that gets light, ongoing attention from you stays active far longer than one that's posted and never revisited.
Let Threads Feed Your Live Sessions, Not Compete With Them
The two formats work best as complements, not alternatives. A thread that surfaces genuine disagreement or an unresolved question is often the best possible source material for your next live session—you already know it's something members care enough about to engage with, and the live conversation can pick up exactly where the thread left off rather than starting cold.
This also solves a common problem with live sessions: not knowing what to talk about. If you're paying attention to which threads generate the most thoughtful back-and-forth, you'll rarely run out of material worth bringing to a call.
Put It Into Practice
This week, post one open-ended, well-framed question as a pinned thread instead of saving it for your next live session. Check back over the following days, add a follow-up, and see how the conversation develops without a clock running.
Key Takeaway
A live call isn't the only place real conversation happens in your community. A well-designed async thread often creates more considered, more inclusive depth—and it's worth treating with the same care you'd give a session you're hosting live.
Read Next
If you're still figuring out your community's overall weekly touchpoints before deciding which format fits which conversation, Plan Your Rhythm Around Your Capacity, Not Your Ambition is worth reading first.
