May 1, 2026
Things to Decide Before Starting a Community That Is Not "Purpose-First"
A community whose premise is NOT “connection to business KPIs”
Community operation has roughly two starting points.
One is the corporate community, launched by a company for business purposes such as customer loyalty or recruiting branding. The other is a theme-based community, which exists in a place separated from business KPIs.
Operators of theme-based communities start not from “in order to achieve something” but from a feeling like “I want to honor the shared feelings and motives of the people who gather.” Many of the communities Rokuse supports sit in this context.
When you try to launch this type of community, applying the design framework of corporate communities as-is throws the first step out of alignment. What you need before “purpose design” is discovery of a theme.
What are fundamental human motives?
The “fundamental motives” that serve as a starting point for a theme-based community arise from feelings and interests that cannot be reduced to KPIs.
For example, things like the following.
- Loneliness and belonging: “There must be someone out there feeling the same thing.”
- Meaning and expression: “I want to put what I value into words with someone.”
- Growth and challenge: “Things I couldn’t see alone become visible when I talk with others.”
- Continuing inquiry: “It’s fine if no answer comes — but there are things I want to keep thinking about.”
These are not answers to the question “what do I want to achieve by creating a community.” But that’s fine. At the core of a theme-based community is the motive to keep facing interests and desires that have no answer.
Conversely, a theme-based community run under the pressure of “we have to produce results from this community” gradually erodes participants’ motivation. The more purpose-first measures pile up, the more the autonomy of the place is lost.
How to set the theme: start from the motives of the people who gather
Designing a theme-based community is not about “creating a theme to gather someone.” It is about “putting into words first the feelings and motives the people who gather have in common.”
This difference in order matters.
| Approach | Stance | Result |
|---|---|---|
| ”Theme to gather people” | Adapt to participants’ interests | Theme becomes vague, axis wobbles |
| ”Start from a shared motive” | Articulate one’s own motive first | Dialogue with people who share that feeling emerges |
By articulating “your own motive” first, the community gains a basis for the operator’s decisions. Just having an axis of “is this related to the theme?” naturally directs planning, invitations, and dialogue.
Three traits of communities with a strong theme
Communities with a clear theme have qualities that make them grow autonomously.
1. Participants can explain “why I’m here”
In a community with a weak theme, participants stay because “I just kind of joined” or “I was invited.” When the theme is strong, participants join with the feeling “I was thinking the same thing.” This difference directly affects the quality of contributions and retention.
2. Operators don’t burn out as easily
In a theme-based community whose premise is not connection to business KPIs, the pressure of “we must keep it active” is relatively low. Resonance with the theme is the place’s engine, so the operator doesn’t have to manufacture engagement intensity by force.
3. It’s easier to retain pull over time
Communities themed on trends lose vitality together with the trend’s end. But themes rooted in fundamental human motives fade less even as eras change. As participants come and go, the motive is passed along.
Three questions for articulating your theme
“Finding a theme” may sound abstract. The three questions below can be used as a starting point for translating your theme into concrete words.
Question 1: “What do I keep thinking about late at night?”
The thing that keeps you awake; the thing you want to talk to someone about. That’s a candidate for your theme. Don’t think “who would care about something like this” — write it down first.
Question 2: “With whom do I lose track of time?”
The person you got fired up with on a particular topic; the conversation that wouldn’t stop. There’s a shared theme there. By articulating “what was good about that conversation,” you start to see the atmosphere your community wants to create.
Question 3: “What will I still care about ten years from now?”
A theme that’s just riding a trend will hardly survive ten years out. If you are still facing the same question ten years from now, that’s the real theme. Passing your theme through this filter lets you check its sustainability.
The first step for a community with a theme
Once you’ve articulated the theme, the first step is “reaching out to three to five people who seem likely to resonate with your theme.”
Begin with dialogue, before announcements or recruiting. In conversations with the first few people, the theme becomes sharper, and “what this community values” naturally takes shape.
The “place” of a community exists before any tool. Before you create a Discord server, you need three-person dialogue. When the feeling of “I want to keep this going” emerges in those conversations, only then does it make sense to step into “creating a place.”
Summary — Start with “a question first”
Launching a corporate community and launching a theme-based community follow different orders of design.
- Corporate community: Purpose → Audience → Design of the place
- Theme-based community: Discovery of a question → Finding people who resonate → Design of the place
If you start a theme-based community “on a vague impulse,” you fall into the same failure as a corporate community. A place without KPIs, where vaguely gathered people can no longer keep going — to avoid this state, what’s needed is not tactics, but articulation of the question.
Start not with “purpose first,” but with “question first.” That starting point becomes the foundation of a community that lasts.
Related articles
Frequently asked questions
- Q. What is the biggest difference between a corporate community and a theme-based community?
- A. A corporate community has "purpose design" first and is built on the premise of connecting to KPIs. A theme-based community has "discovery of a theme" first — its starting point is a question or interest the operator themselves keeps thinking about late at night. The order of design is reversed, and that creates major differences in operating culture and participant motivation.
- Q. How do I judge whether a theme is "weak"?
- A. Try asking yourself, "Will I still care about this same theme ten years from now?" Themes chosen from trend or buzz are fragile to change, and the community's axis tends to wobble. By contrast, themes rooted in motives and values inside yourself fade less with time and keep attracting people with the same motives and interests.
- Q. Does the theme have to be fully decided from the start?
- A. It does not have to be perfect from the start. Through dialogue with the first 10–20 people, the theme becomes sharper. What matters is keeping the stance "we treasure the motives and feelings the gathered people share." Think of a theme as something you grow with participants, not something you declare.