Reach Is Not Community

Community Driven, Part 2 of 3. Build one Hunt Map across the series. Your draft stays in this browser. New here? Start with Part 1.

A post travels farther than usual. An account has a large follower count. An announcement collects a fast stream of reactions. These can all be useful outcomes, especially when the goal is distribution.

They are not, on their own, proof of community.

Reach tells you that something was seen. A living community asks a different set of questions. Do people talk with one another? Do relationships and shared context develop over time? Do players contribute something that other people can use, enjoy, or build on?

This distinction is not an argument against reach. A team may have a valid reason to distribute an announcement widely. It is an argument for matching the evidence to the decision. If you are deciding where to invest community attention, audience size alone leaves too much unanswered.

The first post in this series asked you to define a working player hypothesis and identify one to three candidate campfires. You can also start here. A campfire is simply a place where relevant people may already return to talk, help, create, organize, or make meaning together. Your next job is to look for signs of life without turning a short observation into a sweeping claim.

Signal 1: Active conversation

Active conversation goes beyond replies directed at the studio, creator, or organizer. Look for people responding to one another, asking follow-up questions, comparing experiences, disagreeing constructively, sharing context, and carrying an idea forward.

Useful observation questions include:

• Are most replies aimed only at the original account, or do participants talk with each other?
• Do questions receive useful answers?
• Does a topic develop over several exchanges?
• Do people return after the first reaction?

A fast stream of short reactions can support a content goal. For community research, player-to-player exchange is stronger evidence that the space supports participation rather than distribution alone.

Be specific when you record what happened. "There was good engagement" hides the evidence. "Three participants compared approaches and answered a new participant's question" describes a pattern a teammate can inspect. You do not need to identify the people involved.

Signal 2: Recurring relationships

Communities gain continuity when people recognize one another and develop shared context. Look for recurring participants, informal helpers, references to earlier discussions, collaborative routines, and signs that newcomers can learn how the space works.

This signal is easy to miss if you only inspect the largest post. It often appears across time. The same person returns to help with a familiar problem. Members refer back to an earlier event. A routine gives people a reason to reconvene. Someone explains a norm to a newcomer without being asked.

Also look for stewardship. Moderators, organizers, creators, and community members may guide discussion, reinforce norms, answer questions, and make participation easier. The appropriate cadence depends on the space. A fixed daily posting rule is not a universal measure of care.

A small group can show strong continuity. A large audience can show very little member-to-member interaction. Neither size is automatically good or bad. Judge the activity against the outcome your team wants and the care your team can provide.

Signal 3: Player contribution

Contribution shows that people are investing effort beyond a reaction. The useful form will vary by game and community. It might include:

• Guides, FAQs, build notes, maps, or tutorials
• Fan art, screenshots, clips, stories, or memes
• Mods, tools, custom levels, challenges, or events
• Bug reports, accessibility observations, or structured feedback
• Suggestions that other members refine together
• Welcoming, mentoring, or organizing work

Do not treat every healthy space as if it should produce all of these. Look for contributions that make sense for the game and the local norms. If your team later features a contribution, ask permission where appropriate and give clear credit.

Player contribution can also reveal what people value. A stream of build guides suggests a different participation pattern from a gallery of expressive creations. The observation gives you a better question for the next test. It does not reduce the community to a content supply.

Two cues that cut across the signals

The Hunt Map also lets you record active stewardship and shared feedback. Stewardship includes moderation, guidance, regular prompts, and other signs that someone is caring for participation at a cadence that fits the space. Shared feedback includes recurring frustrations, requests, or questions that people develop together rather than isolated reactions aimed only at the studio.

These are not separate scores. They add context to the three main signal families. Stewardship can make conversation and contribution easier to sustain. Shared feedback can show what people are trying to understand or improve together. Record only what you observed, and leave room for more observation when the pattern is not clear yet.

Keep the evidence narrow

Community evidence is often incomplete or mixed. A space may look quiet because you observed at the wrong time, because activity gathers around events, or because the relevant conversation happens somewhere else. A sudden burst may reflect a launch, update, or controversy rather than an ongoing pattern.

Use language that preserves the boundary between observation and inference.

Write, "I did not observe recurring conversation during this window," rather than, "This community is inactive."

Write, "This clip generated questions about the mechanic," rather than, "Players want this feature."

The narrower statement is more honest and more useful. It shows a teammate what happened, what remains uncertain, and what another observation could clarify.

A simple evidence log can include the observation window, one example of player-to-player conversation, recurring participants or routines, one contribution if present, signs of stewardship, and one question you still cannot answer. Use public and appropriate information. Do not copy private messages, collect personal member details, or place non-public invite links in your notes.

Add signals to your Hunt Map

Use the Hunt Map below to review each candidate campfire. Mark only the signals you actually observed and add a short evidence note. If you have not looked closely enough yet, choose More observation needed and name what you will look for.

If you started the Hunt Map in Part 1, your candidate campfires should already be waiting in this browser. If you entered the series here, you can name and scan one campfire below. Start with Part 1 when you are ready to build the player hypothesis or add more candidate campfires. The tool uses descriptive states, not a numerical community score.

Turn observation into a focused decision

Evidence is useful when it helps a team decide where to invest its limited care. It is not a contest between communities, and it is not a promise that one platform will always work.

In Part 3, Depth Beats Reach, you will choose one focus campfire and assign its current Hunt Zone as Primary, Growth, or Explore. Then you will define one bounded participation test with an observation window and an expected result.

Continue to Part 3: Depth Beats Reach

You can also continue in Pack 1: Find Where Your Players Gather for the complete process. Pack 1 adds three guided mini-lessons, five objective check questions, and a private place to review and save your Hunt Map. Your answers stay in this browser, so copy the summary and paste or rewrite it after signing in.

Reach can help people discover a game. Community becomes visible in what people do with one another after the message arrives. Look for that activity, record it carefully, and let it shape the next decision.