Building a Community That Runs Itself: Here's a principle that sounds obvious until you actually try to live by it.
The community that lasts is the one where you talk least. This started because you answered questions well. The moment it becomes your monologue, it stops being a community and becomes a newsletter with extra steps.
That's the whole idea. And it's harder to execute than it sounds, because the instinct to fill silence; to answer, to explain, to add context; is exactly the instinct that built your reputation in the first place. The same quality that made people want to be in the room with you is the one that, left unchecked, will make the room about you instead of for them.
How It Actually Breaks
Let me describe how this plays out, because I think most founders who've hit this wall recognize it immediately once it's named.
You publish a post. It gets some replies. You answer every one. You add context, you clarify, you elaborate. You are being helpful; genuinely, consciously helpful. And somewhere in the process, something subtle happens.
The conversation stops being a conversation. It becomes a call-and-response with you at the center. New members arrive, read the thread, see that you've already answered everything, and have nothing to add. Quieter members; the ones who had something useful to say but weren't sure whether to say it; see the space already filled and stand down.
This is documented in the research on online community design. Kraut and Resnick, in their MIT Press book Building Successful Online Communities, identify contribution as one of the central design challenges for any online group — and their analysis consistently points to the same problem: when the most visible participant in a community dominates the response pattern, it functionally reduces the incentive and the apparent need for others to contribute. The floor is already covered. Why step onto it?
And the inverse is equally well documented. Arguello and colleagues, in a landmark 2006 study published at the CHI conference on human factors in computing systems, analyzed 6,172 messages across eight Usenet newsgroups and found that 27% of posts received no response at all. More importantly: getting a reply — any reply — significantly predicted whether someone continued to participate. The response was the signal that the room was alive and that the person's voice had landed. That signal is what kept people coming back.
Which means the most valuable thing you can do in a thread is often not answer it yourself. It's create the conditions under which someone else does.
The Method: Ask, Then Get Out of the Way
The tactic is specific enough to do this week. It has two parts, and both of them matter.
Part one: publish a post that ends in a real question.
Not a rhetorical question. Not "what do you think?" appended to a paragraph about your own answer. A question you genuinely don't know the answer to, or one where you know there are better answers in the room than the one you'd give. A question that makes it obvious that you're waiting to hear something, not setting up a reveal.
Real questions have a particular quality; they create a gap the reader wants to fill. Generic invitations don't. "What's your take?" at the end of a post where you've already taken a position is not a real question. It's a comment box. Members can tell the difference, and they respond to it accordingly.
Part two: don't answer the first three replies.
This is the harder half, and it's the half that most founders skip. Someone responds. You have something useful to add. You type it. And in doing so, you close the space that was open.
Wait. Count to three responses. Let the members interact with each other before you enter the thread. What you'll find; and this surprises people the first time; is that the room fills what you leave open. Members answer each other. They add angles you wouldn't have thought of. They build on each other's replies in ways that wouldn't have happened if you'd stepped in first.
And here's the second-order effect that matters just as much: the member who answered someone else's question just had an experience of being useful in this room. That experience is not incidental. It's the thing that makes them come back, that makes them identify as a contributor rather than a consumer, that makes the community feel like theirs rather than yours.
What This Looks Like in Practice
Three things that help with the pause, because knowing this and doing it are different.
- Watch for the urge to clarify. The most common reason founders jump in early isn't that they have new information; it's that they're worried the member's reply missed something. Resist that. Let the thread develop. Incompleteness is not an emergency, and your clarification will land better after the conversation has found its own shape.
- When you do respond, respond to the members, not to the original question. By the time you enter the thread, three people have already answered your question. Don't repeat what they said or re-answer it yourself. Respond to them; acknowledge what they added, ask them a follow-up, surface the most useful thing someone said for the members who come in later. Your job in the thread is to circulate, not to close.
- Read what's missing, not what's said. The most valuable thing you can notice in a quiet thread is what nobody said. A topic the room is circling around but not naming. A question implicit in the replies that hasn't been asked directly. That's your next post; not an answer, but the next real question.
The Reframe That Holds It Together
There is a version of running a community where your authority comes from knowing the most and saying it first. And there is a version where your authority comes from being the person who consistently makes room for the smartest thing in the thread to surface.
The second one scales. The first one doesn't; because it puts a ceiling on the community at the height of your own bandwidth and expertise, and eventually that ceiling becomes the reason people leave. They came for a room. They got a lecture series.
The community that lasts is the one where members consistently experience themselves as capable and heard. Not the one where the founder is consistently impressive. Those are not the same community, and you build them with opposite behaviors.
Ask the real question. Then stop. Let the room prove to itself that it can answer.
Sources
Kraut, R.E., & Resnick, P. (2012). Building Successful Online Communities: Evidence-Based Social Design. MIT Press. mitpress.mit.edu
Arguello, J., Butler, B.S., Joyce, E., Kraut, R., Ling, K.S., Rosé, C., & Wang, X. (2006). "Talk to me: Foundations for successful individual-group interactions in online communities." Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI '06), 959–968. dl.acm.org