Discovery by Question: Designing Social Discovery Around What Members Ask
Most conversations about social discovery start with reach: how many people can find a community, and how quickly. A different starting point is more useful for community builders. Instead of asking how to be seen, ask what questions your members are trying to answer when they look for other people. A person browsing a creator community is rarely looking for a crowd. They are usually looking for someone who has run into the same problem, works in a similar context, or wants the same kind of conversation. When discovery is designed around those questions, members meet each other with a reason, and the connection tends to hold after the first introduction. This article walks through a question-led approach to discovery, how to map the questions your members already ask, and how to check whether your discovery paths answer them.
Start With the Questions Members Bring
Before changing anything about how people find each other, collect the questions they actually bring to your community. These usually appear in introduction posts, direct messages to moderators, comments on shared work, and the first thing a newcomer asks in a thread. Write them down verbatim. Phrases like 'has anyone else tried to price a small digital product,' 'I'm the only designer on a team of engineers,' or 'where do people who edit short video talk shop' tell you far more than a count of followers ever will.
Group these questions into a handful of clusters. Common clusters include shared craft (people doing similar work), shared circumstance (people at the same stage or facing the same constraint), shared audience (people who serve the same kind of reader or viewer), and shared values (people who make similar choices about how they operate). Most communities have three to six clusters that cover the majority of introductions. Those clusters become the backbone of your discovery design, because they describe the reasons members have for wanting to meet someone.
Turn Clusters Into Discovery Routes
A discovery route is a path a member can follow to find people who fit a question. It might be a shared tag on introduction posts, a standing thread for each cluster, a short prompt that appears during onboarding asking which questions the newcomer has, or a themed circle where people with a common circumstance can speak. The key test is whether a member can state, in one sentence, why a given route would connect them to someone useful. If the route only offers 'more people,' it is a feed, not a discovery path.
Keep routes few and legible. Three well-labeled routes are easier to use than twelve overlapping ones. Label each route with the question it answers, written in the member's language rather than internal jargon. A route called 'Pricing and offers' is clearer than 'Monetization vertical,' because the member recognizes their own question in the first one.
A Comparison of Two Discovery Designs
Consider two ways a community might surface people to one another. In the first design, the community highlights whoever is most active or most visible this week. New members see a rotating set of prominent names and are invited to follow them. This design is easy to build and feels energetic, but it answers the question 'who is popular here,' which is rarely what a newcomer needs. Members who arrive with a specific problem may follow a few popular accounts, find none of them relevant, and leave.
In the second design, the community asks each newcomer one or two questions during onboarding, then routes them to the cluster threads and introduction prompts that match. The highlighted people are those who have answered similar questions recently, not those with the largest audience. This design takes more setup and produces smaller, slower gains in raw activity. What it produces instead are connections with a stated reason behind them, and those tend to lead to repeated conversation. When you audit your own community, ask which of these two logics your current surfaces follow.
A Checklist for Reviewing Your Discovery Paths
Use the following questions to review existing discovery paths. Each one points to a specific fix if the answer is no.
Can a new member name the question each discovery route answers? If not, relabel routes using the member's own wording. Does every route have a clear entry point that a newcomer can find within their first session? If a route exists only in an archived post, most members will never reach it. Do the people surfaced to a member share at least one cluster with that member? If overlap is thin, tighten the matching criteria rather than adding more people. Is there a way for members to say what they are looking for, and does that input change what they see? A discovery system that never asks is guessing. Finally, do the connections made through discovery produce follow-up conversation within a few weeks? If introductions happen and then nothing follows, the routes may be connecting people by surface similarity rather than by a real question.
Review these answers on a regular schedule, such as once per quarter. Member questions shift as a community matures and as the work in it changes. A cluster that dominated last year may now be a minor thread, and a new concern may need its own route. Treat the question map as a living document, updated from what members actually say rather than from what the community assumes they want.
Keeping Discovery Honest
Question-led discovery works best when members can see why they were connected. Show the shared cluster or stated question in each introduction, so the other person knows what the connection is for. This small habit reduces awkward first messages and makes it easier for members to decline a match that does not fit. It also gives you a signal: if members routinely decline matches or ignore them, the matching logic needs adjustment.
Finally, be wary of letting discovery become a substitute for the conversations themselves. Routes and prompts should lower the cost of starting a conversation, not replace the conversation. A community where every member is routed to a neighbor and no one speaks to anyone else has built a directory, not a community. Check periodically whether the paths you have designed lead to real exchange, and adjust when they do not.