Community and UGC

Many companies' community efforts start the same way: a Slack or Discord channel opens, forty people join in week one, three questions are asked in month one, and by month two the channel is silent. The team concludes “community doesn't work for our audience.”

But that is a question about why the door was opened, not about community. People do not come to a room a company opened; they come to a place that serves their own problems, their identity or each other. The company's job is not to fill the room but to make the room's reason for existing belong to the users.

When you need it

A community creates value when users have something to tell each other. Signs:

• Users push the product's limits, build their own solutions or templates, and share them without your knowledge.
• They keep asking the support team the same questions, most of which another user could have answered.
• Using the product is tied to a skill or professional identity (designers, developers, accountants, sales teams).
• Users meeting each other increases the product's value.

Where it is too early: with fewer than a thousand users and no shared identity among them, building one-to-one relationships is often more efficient than opening a community platform. In the early stage a community is intensive manual work; without someone who runs it, knows members by name and drops into the room every day, resources are wasted. Giving this job to someone part-time, as “whoever has time can look after it,” is the shortest route to a silent community.

What most teams miss

Seeing community as an acquisition channel is the most common mistake. A community is first a retention and attachment engine; acquisition is the result. When a user finds an answer in the community, helps someone else, or makes the product part of their own identity, the cost of leaving stops being a lost feature and becomes the loss of a network of relationships.

UGC (user-generated content) is the second layer of that bond. Content produced by the company does not scale; once users start producing help, templates, recipes, workflows, case studies, content volume becomes independent of your team's capacity. But there is a subtlety: people do not like working for free, they like being recognized. What pushes a user to create content is not a reward but visibility, status and the pleasure of being useful.

Users do not create content. They create it when they find a place where their identity, expertise or effort can be seen.

There is also the reality of participation distribution. A widely cited rule in online communities (90-9-1) says roughly 90% of participants read and stay silent, 9% contribute occasionally, and 1% produce most of the content. The numbers vary from community to community, but the logic holds: your community stands on that small active core. So success depends not on making the silent majority speak but on feeding the core properly. The difference from the referral piece: referral rewards an action, community nurtures a relationship.

The playbook

1. State the community's purpose in one sentence

“Members reach Y by helping each other with X.” Your product's name does not have to appear in that sentence; its absence is sometimes healthier. People come for their own development, not for your product.

2. Hand-pick the founding core

Invite your 30 to 50 most active users one by one and tell them why they matter. Instead of a big launch, focus on the quality of the first forty people in the room. A person arriving in an empty room leaves; a room where forty experts are talking is one they stay in.

3. Design the contribution ladder

Reading, liking, asking, answering, sharing content, guiding others, moderating. For every rung there should be an easy next step. A new member should be able to do something small on day one (introduce themselves, flag a question); big steps come only after small ones. Look at which rung loses the most people: there is often a wall between reading and asking, or between asking and answering, and one small fix there opens the whole flow.

4. Give UGC a template and a frame

A blank page is frightening. Provide structures like “describe the problem you solved this week in three sentences” or “share your workflow.” Republish the best content inside the product, newsletter or documentation, with attribution. Attribution is the strongest reward.

5. Set moderation and culture early

Write down behavior rules, who can do what, and how expertise is recognized, from the start. Culture forms from the behavior of the first hundred members; changing it later is hard.

6. Connect the community to the product and to feedback

Make it visible that ideas from the community reach the roadmap. A “you said, we did” message builds loyalty inside and trust outside.

What to measure

• Active participant rate: The share of members who contribute at least once a month. A leading indicator.
• Retention gap between community members and non-members: Separation shows the community genuinely creates attachment.
• UGC's contribution to support and acquisition: The share of questions answered by users, organic traffic from UGC content.
• Core health: The share of the first 30 to 50 active members still active after three months.

Pitfalls

Turning the community into an announcement channel. The company talks, members listen. If most of the conversation is not between members, it is a newsletter channel, not a community.

Leaning on rewards too early. Points, badges or gifts inflate participation artificially before a bond exists and collapse when the reward ends. Recognition first, rewards later.

Not sharing ownership. If the company makes every decision, community leaders burn out and real participation dies. Give moderators and senior members real authority.

Start this week

1. List your 30 most active users and write each a short, personal message about why they are valuable.
2. Write the community's purpose in one sentence and check whether it still makes sense without your product's name.
3. Take the ten most common support questions and republish three of them this week with a real user's own answer.