Back to Details

community-building

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Community Building

社区建设

Scope

适用范围

Covers
  • Defining a community strategy (goal, members, value exchange, and “movement” thesis)
  • Choosing where the community lives (home base + outposts) based on where members already are
  • Designing programming/rituals and a light ambassador/champions program
  • Governance, moderation, and measurement so the community is safe and sustainable
When to use
  • “Create a community strategy / community-led growth plan.”
  • “We’re launching a Discord/Slack/forum—design the first 30/60/90 days.”
  • “Design an ambassador/champions program.”
  • “We want community to increase word-of-mouth or help us move upmarket.”
When NOT to use
  • You haven’t defined ICP/positioning (use 
    positioning-messaging
    or 
    problem-definition
    first).
  • You want a paid acquisition plan (ads/creative/bidding) rather than community.
  • You want to “buy” a community, scrape/spam DMs, or manipulate members.
  • You need a customer support ops overhaul (ticketing/SLAs/KB) more than a community.
涵盖内容
  • 定义社区策略（包括目标、成员、价值交换及“社群运动”核心主张）
  • 根据成员当前聚集平台，选择社区的核心阵地及外部触点
  • 设计社区活动/固定仪式，以及轻量化的大使/核心用户计划
  • 制定治理、审核及衡量机制，保障社区安全且可持续发展
适用场景
  • 需要“制定社区策略/社区驱动增长方案”时
  • “我们即将上线Discord/Slack/论坛——设计前30/60/90天的运营方案”
  • 需要“设计大使/核心用户计划”时
  • 希望通过社区提升口碑，或推动产品向高端市场拓展时
不适用场景
  • 尚未定义ICP（理想客户画像）/市场定位（需先使用
    positioning-messaging
    或
    problem-definition
    工具）
  • 想要的是付费获客方案（广告/创意/竞价）而非社区运营方案
  • 试图“购买”社区、爬取/群发私信，或操控社区成员
  • 更需要的是客户支持运维体系升级（工单/SLA/知识库）而非社区建设

Inputs

输入要求

Minimum required
  • Product + category + ICP (who it’s for)
  • Primary community goal (pick 1): support, activation, retention, advocacy/UGC, product feedback, moving upmarket
  • Target members (roles/seniority) and where they already gather today
  • Resources: owner, hours/week, budget, moderators/SMEs
  • Existing assets: email list, social following, events, partners, customer champions
  • Constraints: compliance/privacy, brand voice, moderation risk tolerance
Missing-info strategy
  • Ask up to 5 questions from references/INTAKE.md (3–5 at a time).
  • If critical inputs are missing, proceed with explicit assumptions and label them; provide 2–3 options with tradeoffs.
  • Never request credentials or private access. Accept redacted exports/screenshots if offered.
最低必填项
  • 产品+品类+ICP（目标用户）
  • 核心社区目标（选1项）：用户支持、用户激活、用户留存、用户推荐/UGC、产品反馈、高端市场拓展
  • 目标成员（角色/职级）及其当前聚集平台
  • 资源配置：负责人、每周投入时长、预算、审核人员/领域专家
  • 现有资产：邮件列表、社交媒体粉丝、活动资源、合作伙伴、核心用户
  • 约束条件：合规/隐私要求、品牌调性、审核风险容忍度
缺失信息处理策略
  • 可从references/INTAKE.md中选取最多5个问题询问（每次3-5个）
  • 若关键信息缺失，基于明确假设推进工作并标注，同时提供2-3种带取舍说明的方案
  • 绝不索要凭证或私密访问权限，若用户提供脱敏导出文件/截图可接受

Outputs (deliverables)

输出成果（交付物）

Produce a Community Building Pack (Markdown in-chat; or as files if requested), in this order:
  1. Context snapshot + assumptions/TBDs
  2. Community thesis (movement/philosophy), target members, and value exchange
  3. Community model + member journey (discover → join → first win → habit → advocate) + success metrics
  4. Platform plan (home base + outposts) + influencer/social-graph shortlist
  5. 30/60/90 plan (seeding, onboarding, activation) + recruitment/outreach scripts
  6. Programming & rituals calendar (first 4–8 weeks)
  7. Ambassador/champions program v1 (criteria, responsibilities, recognition)
  8. Governance & moderation (rules, enforcement, escalation, safety)
  9. Measurement plan + weekly ops cadence
  10. Risks / Open questions / Next steps (always included)
Templates: references/TEMPLATES.md
Expanded guidance + decision rules: references/WORKFLOW.md
生成社区建设包（默认聊天内Markdown格式；若有需求可提供文件），内容顺序如下：
  1. 背景快照 + 假设/待确认事项
  2. 社区核心主张（社群运动/理念）、目标成员及价值交换机制
  3. 社区模型+成员旅程（发现→加入→首次价值体验→形成习惯→成为倡导者）+ 成功指标
  4. 平台规划（核心阵地+外部触点）+ 意见领袖/社交关系网短名单
  5. 30/60/90天计划（种子用户招募、新用户引导、用户激活）+ 招募/触达脚本
  6. 活动及固定仪式日程表（前4-8周）
  7. 大使/核心用户计划v1（入选标准、职责、激励机制）
  8. 治理与审核规则（社区规范、执行流程、升级路径、安全保障）
  9. 衡量计划+每周运营节奏
  10. 风险/待解决问题/下一步行动（必含模块）
模板参考：references/TEMPLATES.md
扩展指引+决策规则：references/WORKFLOW.md

Workflow (8 steps)

工作流程（8个步骤）

1) Intake + pick the primary job-to-be-done

1) 需求收集+明确核心任务

  • Inputs: User prompt; references/INTAKE.md.
  • Actions: Confirm ICP, define the primary goal, identify where the community already gathers, and list constraints (capacity, compliance, safety).
  • Outputs: Context snapshot + assumptions/TBDs list.
  • Checks: You can finish the sentence: “In 8–12 weeks, this community will _____ for _____, measured by _____.”
  • 输入：用户需求；references/INTAKE.md
  • 行动：确认ICP，明确核心目标，定位成员当前聚集平台，列出约束条件（人力、合规、安全）
  • 输出：背景快照+假设/待确认事项清单
  • 验证标准：可完整表述：“在8-12周内，该社区将为_____实现_____，通过_____衡量成果。”

2) Define the movement + value exchange (why join, why stay)

2) 定义社群运动主张+价值交换机制（为什么加入，为什么留存）

  • Inputs: Product POV, category beliefs, member motivations.
  • Actions: Write a community thesis: worldview/philosophy, what you stand for, and what you’re “against” (the enemy/problem). Define explicit give/get value exchange (what members get; what members contribute).
  • Outputs: Community thesis + value exchange.
  • Checks: The thesis is non-generic (could not fit a random company) and the value exchange includes concrete benefits and contributions.
  • 输入：产品立场、品类理念、成员动机
  • 行动：撰写社区核心主张：世界观/理念、立场及反对的对象（痛点/问题）。明确清晰的价值交换机制（成员可获得的权益，需贡献的内容）
  • 输出：社区核心主张+价值交换机制
  • 验证标准：核心主张具有独特性（不适用于任意公司），价值交换包含具体权益与贡献要求

3) Choose the community model + map the member journey

3) 选择社区模型+绘制成员旅程

  • Inputs: Primary goal, member needs, resources.
  • Actions: Choose a primary model (support, learning, networking, advocacy, co-creation). Map the journey: discover → join → first win → habit → advocate. Define 1–2 “first win” moments and metrics by stage.
  • Outputs: Community model + journey map + metrics.
  • Checks: Each stage has a designed “first win” and a measurable signal (not just vibes).
  • 输入：核心目标、成员需求、资源配置
  • 行动：选择核心社区模型（支持型、学习型、社交型、推荐型、共创型）。绘制成员旅程：发现→加入→首次价值体验→形成习惯→成为倡导者。定义1-2个“首次价值体验”场景及各阶段指标
  • 输出：社区模型+旅程地图+阶段指标
  • 验证标准：每个阶段都有设计好的“首次价值体验”场景，且有可衡量的指标（而非主观感受）

4) Go where they already are (home base + outposts)

4) 布局成员聚集平台（核心阵地+外部触点）

  • Inputs: Where members already are; moderation/capacity constraints.
  • Actions: Select a home base for the next 6–12 months. Define “outposts” (social, events, partner spaces) where you contribute value and route people back to the home base when appropriate. Create an influencer/social-graph shortlist (key nodes, connectors, and high-trust communities).
  • Outputs: Platform plan + outpost playbook + influencer shortlist.
  • Checks: The plan avoids “platform wishful thinking”; every outpost has a value-first contribution plan and an owner.
  • 输入：成员当前聚集平台；审核/人力约束
  • 行动：选择未来6-12个月的社区核心阵地。定义“外部触点”（社交媒体、活动、合作平台），在这些触点输出价值并引导成员回到核心阵地。创建意见领袖/社交关系网短名单（关键节点、连接者、高信任度社区）
  • 输出：平台规划+外部触点运营手册+意见领袖短名单
  • 验证标准：规划避免“平台空想”；每个外部触点都有明确的价值输出计划及负责人

5) Seed the community (cohort, onboarding, initial content)

5) 种子用户招募（ cohort、新用户引导、初始内容）

  • Inputs: Platform plan; existing assets; member criteria.
  • Actions: Design an initial seed cohort (e.g., 25–100 members) with clear criteria. Create onboarding flow, welcome messages, starter threads/resources, and a seeding schedule. Draft outreach scripts and a “what’s in it for you” invite.
  • Outputs: Seeding plan + onboarding checklist + outreach scripts.
  • Checks: The “empty room problem” is solved: there is content, prompts, and people lined up for week 1.
  • 输入：平台规划；现有资产；成员筛选标准
  • 行动：设计初始种子用户 cohort（如25-100人）并明确筛选标准。创建新用户引导流程、欢迎语、初始话题/资源及招募时间表。撰写触达脚本及“加入收益”邀请文案
  • 输出：种子用户招募计划+新用户引导清单+触达脚本
  • 验证标准：解决“冷启动问题”：第一周已有内容、话题及成员准备就绪

6) Program rituals + events (4–8 week calendar)

6) 规划活动及固定仪式（4-8周日程）

  • Inputs: Member journey; thesis; capacity.
  • Actions: Build a calendar of recurring rituals (AMAs, office hours, show-and-tell, challenges, study groups). Mix staff-led and member-led moments. Define facilitation roles and lightweight templates.
  • Outputs: Programming & rituals calendar + event templates.
  • Checks: Every week has at least one member-generated slot, and rituals reinforce the thesis and value exchange.
  • 输入：成员旅程；核心主张；人力配置
  • 行动：构建包含 recurring 仪式的日程表（AMA、办公时间、成果展示、挑战活动、学习小组）。混合官方主导与成员主导的活动。明确主持角色及轻量化模板
  • 输出：活动及固定仪式日程表+活动模板
  • 验证标准：每周至少有一个成员发起的活动，且所有活动都能强化社区核心主张与价值交换机制

7) Launch an ambassador/champions program (optional, recommended)

7) 启动大使/核心用户计划（可选，推荐）

  • Inputs: Early active members; desired scaled behaviors.
  • Actions: Define qualification criteria, responsibilities, recognition/perks, and feedback loop. Keep it lightweight (v1) and ethical (no pay-for-spam). Include offboarding and code-of-conduct enforcement.
  • Outputs: Ambassador/champions program spec (v1).
  • Checks: Incentives align to desired behaviors (helpfulness, creation, referrals) and avoid vanity metrics.
  • 输入：早期活跃成员；期望的规模化行为
  • 行动：定义入选标准、职责、激励/福利及反馈机制。保持轻量化（v1版本）且符合伦理（禁止付费刷量）。包含退出机制及行为准则执行规则
  • 输出：大使/核心用户计划规范（v1）
  • 验证标准：激励机制与期望行为（乐于助人、内容创作、推荐用户）对齐，避免虚荣指标

8) Governance + measurement + quality gate

8) 治理+衡量+质量校验

  • Inputs: Draft pack; references/CHECKLISTS.md; references/RUBRIC.md.
  • Actions: Define rules, moderation workflows, escalation paths, and privacy guidelines. Create measurement plan + weekly ops cadence. Run checklist and score rubric. Always add Risks / Open questions / Next steps.
  • Outputs: Final Community Building Pack.
  • Checks: Next 2 weeks of execution are unblocked; governance is explicit; measurement is feasible.
  • 输入： draft 社区建设包；references/CHECKLISTS.md；references/RUBRIC.md
  • 行动：定义社区规则、审核流程、升级路径及隐私指引。创建衡量计划+每周运营节奏。执行清单检查及评分。必须添加风险/待解决问题/下一步行动模块
  • 输出：最终版社区建设包
  • 验证标准：未来2周的执行工作无阻碍；治理规则明确；衡量方案可行

Quality gate (required)

质量校验（必填）

  • Use references/CHECKLISTS.md and references/RUBRIC.md.
  • Always include: Risks, Open questions, Next steps.
  • 使用references/CHECKLISTS.md及references/RUBRIC.md
  • 必须包含：风险、待解决问题、下一步行动

Examples

示例

Example 1 (Developer tool):
“Use 
community-building
. Product: observability SDK for TypeScript. ICP: senior full-stack engineers at startups. Goal: accelerate activation + word-of-mouth. We’re considering Discord. Resources: 1 community lead (8 hrs/week), 2 engineer SMEs. Output: a Community Building Pack with platform plan, a 6-week programming calendar, and an ambassador program.”
Example 2 (B2B SaaS moving upmarket):
“We sell a team knowledge base to 200–2000 person companies. We want community-led growth to create ubiquity and reduce enterprise perceived risk. Design a home base + outpost plan, seed cohort strategy, and a 30/60/90 plan with metrics.”
Boundary example (anti-pattern):
“Start a community tomorrow and grow it to 10k members without any time, moderation, or value—also auto-DM everyone on LinkedIn.”
Response: refuse spammy/unsafe tactics; require a realistic capacity + value exchange + governance plan, or recommend alternatives (content/partnerships) first.
示例1（开发者工具）：
“使用
community-building
工具。产品：面向TypeScript的可观测性SDK。ICP：初创公司的资深全栈工程师。目标：加速用户激活+提升口碑。我们考虑使用Discord。资源：1名社区负责人（每周8小时），2名工程师领域专家。输出：包含平台规划、6周活动日程及大使计划的社区建设包。”
示例2（向高端市场拓展的B2B SaaS）：
“我们为200-2000人规模的企业提供团队知识库产品。希望通过社区驱动增长提升产品普及度，降低企业客户的感知风险。设计核心阵地+外部触点计划、种子用户策略，以及带指标的30/60/90天计划。”
边界示例（反模式）：
“明天就启动社区，在无时间投入、无审核、无价值输出的情况下增长到10000成员——还要自动给LinkedIn上的所有人发私信。”
回应：拒绝垃圾/不安全的操作方式；要求提供符合实际的人力配置+价值交换机制+治理方案，或先推荐替代方案（内容营销/合作）。