Depth Beats Reach

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

For a small game team, being everywhere is not a neutral strategy. Every new channel creates another place to listen, respond, moderate, adapt content, learn norms, and close the loop when players offer their time.

The cost is not just the next post. It is the care that participation creates.

That is why this Community Driven exercise ends with focus. You define the likely players, find the campfires where relevant activity may already exist, and look for evidence of conversation, recurring relationships, and player contribution. Then you choose one place where your team can learn by participating well.

Depth is a practical constraint here, not a universal law. A broad distribution campaign may fit a reach objective. A larger team may already have the capacity to care for several spaces. But when attention is limited, shallow activity across every plausible channel can make it harder to learn what actually works.

The goal is not to crown a permanent winner. It is to make a reasoned choice, run a bounded test, and revise the choice with better evidence.

Sort the work into three Hunt Zones

The Hunt Zones are working categories. They describe your current level of evidence and commitment. They do not score the worth of a community.

Primary Hunt Zone

Choose Primary when you have the strongest relevant evidence and a credible way to participate consistently. You may see recurring player conversation, useful contributions, or a clear match between the space's interests and the experience your game offers.

Primary does not mean "post the most." It means this is the first place where you will listen, participate, test, and learn. Your team should be able to follow the space's norms, respond to people, and maintain the activity it starts.

Growth Hunt Zone

Choose Growth when the fit looks promising but the evidence or momentum is incomplete. You may see related conversations, a creator or organizer who reaches relevant people, or a contribution pattern the game could support. A focused test can help you decide whether deeper participation is warranted.

Explore Hunt Zone

Choose Explore when the connection is plausible but early or weakly evidenced. This is not a rejection. It is a decision to observe at a lower level while you invest more effort elsewhere.

Exploration might include following public conversations, noting relevant creators or events, or returning after a development milestone. Give the exploration a review point so it does not become an indefinite list of channels nobody evaluates.

For this exercise, choose one focus campfire and assign the Hunt Zone that best matches the evidence you have now. It may be Primary, Growth, or Explore. The label describes your current evidence and capacity, not the community's worth and not a permanent platform decision.

Make the reason inspectable

"Everyone is there" is not enough. Neither is "another studio is doing well there." Write the choice in a way that connects evidence with team capacity:

I chose [space] as Primary because I observed [specific conversation, relationship, or contribution signal], and our team can [credible participation behavior] during [time window].

This sentence creates a decision that can be discussed. A teammate can challenge the observation, the fit, or the capacity assumption without arguing over a vague preference.

Capacity belongs in the decision because community participation has consequences. If you invite feedback, someone needs to acknowledge it and explain what happens next. If you start a recurring discussion, the team needs to return. If you feature player work, the team needs to handle permission and credit with care.

Choosing a space you can support is part of choosing well.

Validate an approach, not a platform

The next step is not to declare that the chosen Hunt Zone is "the right channel." It is to test a way of participating there.

A useful quick-win test has five parts:

1. Action: What will the team do?
2. Space: Where will it happen, and what local norms apply?
3. Window: When will you observe the response?
4. Expected result: What concrete signal would support the hypothesis?
5. Next decision: What would make you continue, adjust, or stop?

The action should be small enough to run and specific enough to review. You might share a short gameplay clip and respond to substantive comments you can responsibly address. You might join an existing discussion and ask one focused question that contributes to the topic. You might run a poll tied to a real design choice, then explain how the result will be used. You might feature a player contribution after receiving permission and giving clear credit.

Match the expected result to the question. If you want to learn whether a mechanic creates discussion, look for questions, comparisons, and follow-up conversation. If you want to learn whether people enjoy creating with a system, look for examples, remixes, or requests for tools. A welcome increase in followers would not answer either question by itself.

One attempt rarely proves that a channel is right or wrong. Its value is that it gives the next decision better evidence.

Close the loop with the people who respond

Participation includes response. If people ask questions, offer ideas, identify problems, or make something, acknowledge the effort and continue the useful exchange. Do not ask for feedback your team has no intention or capacity to consider.

At the end of the observation window, record what happened, what surprised you, which signal supported or challenged the hypothesis, and whether you will continue, adjust, or stop. Then name the next test.

This review protects the team from two common errors. The first is treating a positive response as permanent proof. The second is treating a quiet first attempt as a permanent rejection. A bounded test supports a bounded conclusion.

Complete your Hunt Map

Use the final Hunt Map step below to choose a campfire and mark it as Primary, Growth, or Explore. Explain the reason, choose one action, set an observation window, and name the result you expect to see.

If you completed Parts 1 and 2, the same browser-local draft will carry your player hypothesis, candidate campfires, and evidence into this step. If you started here, add what you know and return to the earlier sections when useful. The tool does not send your written answers through the Academy link.

Your finished summary follows six headings:

1. Define Your Players
2. Find Their Campfires
3. Listen for Signals
4. Choose Your Hunt Zone
5. Set a Quick-Win Goal
6. Define the Win

This browser summary is a strong artifact draft, not an automatic transfer or a finished strategy. Pack 1 helps you review the evidence gaps, make the decision rule explicit, and refine the summary before saving it to your Academy account.

Copy or print the summary before moving on. Keep it as a one-page decision record for the team, then return after the observation window and update what happened, what you learned, and what you will do next.

Continue in Pack 1

Continue in Pack 1: Find Where Your Players Gather to work through the complete method, move through its three mini-lessons, and take the Pack quiz.

The handoff is intentionally simple. Your Hunt Map stays in this browser. Use Copy Summary, open Pack 1, sign in when you are ready to save your work, and paste or rewrite the summary in the private Hunt Map artifact. Review it before submitting. No Hunt Map answer text belongs in the Academy URL.

The artifact is a working document, not a prediction that you found the perfect community. It should show who you are looking for, where you listened, what you observed, why one place deserves focus, and what your team will test next.

That is the practical case for depth. It gives a small team enough focus to participate with care and enough structure to learn from the response.