Write about your community, not for them
When companies asked me why their community had stalled, I would usually find the same scene. Product updates, feature announcements, and carefully curated posts filled the feed. Members had joined, but they weren't talking to each other. They were waiting for the company to give them something to respond to.
I've built communities that grew to hundreds of thousands of members, and I've consulted with dozens of companies whose communities were stuck. The community manager was often working incredibly hard. That was part of the problem. Every new post taught members that the company would keep the room going for them.
When the company carries the conversation
I think of these as branded communities. The company creates the content, sets the agenda, and controls the narrative. Engagement can look fine on paper, but most of the conversation points back toward the brand.
That model tends to hit a ceiling. Conversations get stale, engagement drops, and the community manager works even harder to feed the content machine. I've watched that loop wear people out more than once.
The communities that kept growing worked differently. Members brought the conversation, while the company made room for it and helped good contributions travel further. When the company stepped back, people still had reasons to be there.
Put a member in the story
On community sites I worked with, we asked the community managers to change one small thing. Instead of writing, "Here's how to use our new feature," they would write, "Sarah figured out a clever way to use our new feature. Here's what she discovered."
The information barely changed. The center of the story did.
It took some convincing. Community managers are used to being the expert and creating the content. Once they saw how members responded, they got it. People wanted their work to be featured. They shared what they'd discovered, and even started competing to show the cleverest uses.
The change brought more members into the conversation. We hadn't added more content. We'd started paying attention to what members were already doing.
From communicator to facilitator
The change also gave the community manager a different job. A communicator creates content and speaks for the company. A facilitator notices useful work, removes friction, and helps members speak for themselves.
Facilitation is quieter. It means asking for feedback when a feature is still taking shape, finding members who are using the product in interesting ways, and bringing their work into view. The test is what happens when the community manager steps away. Do members continue the conversation, or does the room go silent?
I watched a developer community flip this way. The company stopped posting tutorials and started documenting what members built. It stopped announcing features and started sharing how members used them. Members created more, and the company's job gradually shifted from producing to curating. It was less work and much more sustainable.
Some companies do need a branded community. Some audiences genuinely want a curated channel from the company. That's fine.
If you want members to feel ownership, look at who fills the feed and who keeps it alive. Members show ownership when the conversation keeps moving after the company steps away.