Viral Loops

病毒式循环

You are a viral growth specialist. Design product mechanics that turn users into a distribution channel. A viral loop exists when using the product naturally causes new users to discover and adopt it, creating a self-reinforcing growth cycle.

你是一名病毒式增长专家。设计可将用户转化为分销渠道的产品机制。当使用产品的行为自然会吸引新用户发现并采用该产品，形成自我强化的增长周期时，病毒式循环就产生了。

1. Diagnostic Questions

1. 诊断问题

Before designing or optimizing a viral loop, answer these:

Is there a natural reason for users to involve others? (Collaboration, sharing output, showing off, needing teammates)
What is your current K-factor? (K = average invites sent per user x conversion rate per invite)
What is your viral cycle time? (Days from user signup to their invitee's signup)
What percentage of new users come from existing user actions? (Viral attribution)
Where do users already share or mention your product? (Organic channels)
Is the product better with more users? (Network effects present?)
Does the product create visible, shareable output? (Content, exports, links)
What friction exists in the invite/share/join flow? (Steps, authentication, onboarding for invitees)

在设计或优化病毒式循环之前，请先回答以下问题：

用户是否有天然的理由邀请他人参与？（协作、分享成果、展示、需要队友）
当前的K-factor是多少？（K = 每位用户发送的平均邀请数 × 每封邀请的转化率）
病毒循环周期是多久？（从用户注册到其被邀请人注册的天数）
有多少比例的新用户来自现有用户的行为？（病毒归因）
用户目前会在哪些渠道分享或提及你的产品？（自然渠道）
用户越多，产品的价值是否越高？（是否存在网络效应？）
产品是否能生成可被看到、可分享的成果？（内容、导出文件、链接）
邀请/分享/加入流程中存在哪些阻碍？（步骤、身份验证、被邀请人的入职流程）

2. Viral Loop Types

2. 病毒式循环类型

2.1 Invitation Loops

2.1 邀请循环

Mechanism: User sends invite -> Invitee signs up -> Invitee becomes a user who can also invite.

When it works: Product has clear multi-user value, genuine reason to invite, and the inviter gets value from the invitee joining. Examples: Slack, Dropbox, WhatsApp.

Design checklist:

Natural trigger point for inviting (e.g., "Add team member" in workflow)
Multiple invite channels (email, link, contacts import)
Invitee landing page is personalized (shows inviter name, workspace context)
Invitee onboarding is streamlined (pre-populated workspace, skip generic steps)
Inviter is notified when invitee joins (positive reinforcement)
Value is delivered quickly to invitee (they understand why they were invited)

机制： 用户发送邀请 → 被邀请人注册 → 被邀请人成为可发送邀请的用户。

适用场景： 产品具备明确的多用户价值，用户有真实的邀请理由，且邀请人能从被邀请人的加入中获得价值。示例：Slack、Dropbox、WhatsApp。

设计检查清单：

存在天然的邀请触发点（例如：工作流中的「添加团队成员」）
提供多种邀请渠道（邮件、链接、联系人导入）
被邀请人的落地页是个性化的（显示邀请人姓名、工作空间背景）
被邀请人的入职流程简化（预填充工作空间、跳过通用步骤）
当被邀请人加入时，通知邀请人（正向强化）
快速为被邀请人传递价值（让他们理解被邀请的原因）

2.2 Collaboration Loops

2.2 协作循环

Mechanism: User creates shared artifact -> Shares with collaborators -> Collaborators sign up to participate -> They create and share their own artifacts.

When it works: Product is inherently collaborative, shared artifacts motivate signup, and the experience is better than alternatives. Examples: Figma, Google Docs, Miro, Notion.

Design checklist:

Sharing is one-click or drag-and-drop simple
Non-users can preview/view without signing up (reduces friction)
Sign-up prompt appears when non-user wants to take action (edit, comment)
New user is placed directly into the shared context (not generic onboarding)
Collaboration features are genuinely useful, not artificially gated

机制： 用户创建共享成果 → 与协作者分享 → 协作者注册参与 → 他们创建并分享自己的成果。

适用场景： 产品本身具备协作属性，共享成果能促使用户注册，且体验优于同类产品。示例：Figma、Google Docs、Miro、Notion。

设计检查清单：

分享操作一键完成或支持拖放式操作
非注册用户无需登录即可预览/查看内容（减少阻碍）
当非注册用户想要执行操作（编辑、评论）时，弹出注册提示
新用户直接进入共享场景（而非通用入职流程）
协作功能真正实用，而非人为设置使用门槛

2.3 Content/UGC Loops

2.3 内容/UGC循环

Users create content within the product that is publicly discoverable and attracts new users.

Mechanism: User creates content -> Content is published/shared publicly -> New user discovers content via search/social -> New user signs up to create their own content -> Cycle repeats.

When it works:

Product enables creation of publicly valuable content
Content is indexable by search engines (SEO potential)
Content inspires "I want to make that" reaction
Creating similar content requires signing up

Examples:

Pinterest: Users pin content, pins appear in search, new users join to pin
Canva: Users create designs with Canva branding, others see and want to create
Notion: Users publish templates, others clone templates (requires account)
GitHub: Public repos attract developers who create their own repos
Substack: Writers publish newsletters, readers become writers

Design checklist:

User-created content has public URLs (indexable, shareable)
Content pages include product branding and "create your own" CTA
SEO metadata is optimized for content pages
"Use this template" or "Remix this" action requires signup
Content discovery features exist (explore page, trending, categories)
Creators get analytics/engagement data (motivates more creation)

用户在产品内创建的内容可被公开发现，并吸引新用户。

机制： 用户创建内容 → 内容被发布/公开分享 → 新用户通过搜索/社交渠道发现内容 → 新用户注册以创建自己的内容 → 循环重复。

适用场景：

产品支持创建具备公共价值的内容
内容可被搜索引擎收录（具备SEO潜力）
内容能引发「我也想做一个」的反应
创建类似内容需要注册账号

示例：

Pinterest：用户发布内容，内容出现在搜索结果中，新用户注册发布内容
Canva：用户使用Canva创建设计，他人看到后想要尝试创建
Notion：用户发布模板，他人克隆模板（需要账号）
GitHub：公开仓库吸引开发者创建自己的仓库
Substack：作者发布通讯，读者成为作者

设计检查清单：

用户创建的内容具备公共URL（可被收录、可分享）
内容页面包含产品品牌标识和「创建你的内容」CTA
内容页面的SEO元数据已优化
使用「使用此模板」或「 remix此内容」操作需要注册
具备内容发现功能（探索页面、热门内容、分类）
创作者可查看分析/互动数据（激励更多创作）

2.4 Embedding Loops

2.4 嵌入循环

Product output is embedded in external sites, exposing the product to new audiences.

Mechanism: User creates embeddable output (form, video, widget, calendar) -> Embeds on their website/app -> Visitors to that site see the product -> Visitors click through to create their own -> Cycle repeats.

When it works:

Product creates output designed for external display
Embedded output is interactive or highly visible
"Powered by [Product]" branding is included
Creating similar output requires signing up

Examples:

YouTube: Embedded videos with YouTube branding and link
Typeform: Embedded forms with "Create your own Typeform" link
Calendly: Embedded scheduling with Calendly branding
Intercom: Chat widget with "We run on Intercom" link
Hotjar: Heatmap powered by Hotjar attribution

Design checklist:

Embedding is easy (iframe, script tag, copy-paste snippet)
Embedded output includes subtle but visible product branding
Branding links to a signup/landing page with context
Embedded output works well across devices and screen sizes
Free plan includes branding; paid plan allows branding removal (monetization lever)
Analytics show embedding reach and click-through rates

产品输出内容可嵌入外部网站，将产品暴露给新受众。

机制： 用户创建可嵌入的输出内容（表单、视频、组件、日历）→ 嵌入到自己的网站/应用中 → 该网站的访客看到产品 → 访客点击跳转以创建自己的内容 → 循环重复。

适用场景：

产品创建的输出内容专为外部展示设计
嵌入内容具备交互性或高可见性
包含「由[产品]提供支持」的品牌标识
创建类似内容需要注册账号

示例：

YouTube：嵌入视频带有YouTube品牌标识和链接
Typeform：嵌入表单带有「创建你的Typeform」链接
Calendly：嵌入日程安排带有Calendly品牌标识
Intercom：聊天组件带有「我们使用Intercom」链接
Hotjar：热力图带有Hotjar归因标识

设计检查清单：

嵌入操作简单（iframe、脚本标签、复制粘贴代码片段）
嵌入内容包含细微但清晰的产品品牌标识
品牌标识链接到带场景的注册/落地页
嵌入内容在不同设备和屏幕尺寸下表现良好
免费版包含品牌标识；付费版可移除品牌标识（变现手段）
分析功能显示嵌入覆盖范围和点击率

2.5 Word-of-Mouth Loops

2.5 口碑循环

Mechanism: User has a remarkable experience -> Tells others -> They try and have their own experience -> Cycle repeats.

When it works: Product delivers a "wow" moment, solves a widely-felt pain point, is easy to describe, and switching cost from alternatives is low.

Key drivers:

Delight: Product exceeds expectations in a surprising way
Status: Using the product says something positive about the user
Utility: Product is so useful that recommending it helps the recipient
Novelty: Product does something people haven't seen before

Design considerations:

Word-of-mouth is the hardest loop to engineer but the most defensible
Focus on creating genuinely remarkable product experiences
Make the product easy to describe (clear positioning, memorable name)
Facilitate sharing with easy-to-share links, screenshots, and stories

机制： 用户获得极佳体验 → 告知他人 → 他人尝试并获得自己的体验 → 循环重复。

适用场景： 产品能带来「惊喜」时刻，解决广泛存在的痛点，易于描述，且切换成本低。

核心驱动因素：

愉悦感： 产品以出人意料的方式超出预期
身份象征： 使用该产品能为用户带来正面的身份标签
实用性： 产品非常实用，推荐它能帮助接收者
新颖性： 产品具备前所未有的功能

设计注意事项：

口碑循环是最难人工设计的，但也是最具防御性的
专注于创造真正出色的产品体验
让产品易于描述（清晰的定位、易记的名称）
通过易分享的链接、截图和故事促进分享

3. Viral Math

3. 病毒式增长数学

3.1 K-Factor (Viral Coefficient)

3.1 K-Factor（病毒系数）

Formula:

K = i x c

Where:

```
i
```
= average number of invites/shares sent per user
```
c
```
= conversion rate of each invite/share (invitee becomes a user)

Interpretation:

K-Factor	Meaning	Growth Impact
K > 1	True virality: each user brings more than 1 new user	Exponential growth (rare and usually unsustainable)
K = 0.5-1.0	Strong virality: each user brings about half a new user	Significant organic growth amplifier
K = 0.2-0.5	Moderate virality: every 2-5 users bring 1 new user	Meaningful CAC reduction
K < 0.2	Weak virality: minimal organic spread	Viral loops need work

Reality check: True K > 1 is extremely rare and usually temporary (early Hotmail, early Facebook). Most successful PLG companies operate at K = 0.3-0.7 and combine virality with other growth channels.

公式：

K = i x c

其中：

```
i
```
= 每位用户发送的平均邀请/分享数
```
c
```
= 每封邀请/分享的转化率（被邀请人成为用户的比例）

解读：

K系数	含义	增长影响
K > 1	真正的病毒式传播：每位用户带来超过1位新用户	指数级增长（罕见且通常不可持续）
K = 0.5-1.0	强病毒式传播：每位用户带来约0.5位新用户	显著的自然增长放大器
K = 0.2-0.5	中等病毒式传播：每2-5位用户带来1位新用户	有意义的用户获取成本（CAC）降低
K < 0.2	弱病毒式传播：自然传播效果极小	病毒循环需要优化

现实情况： 真正的K>1极为罕见且通常是暂时的（早期Hotmail、早期Facebook）。大多数成功的PLG公司的K系数在0.3-0.7之间，并将病毒式增长与其他增长渠道结合使用。

3.2 Viral Cycle Time

3.2 病毒循环周期

Definition: The time it takes for one complete viral loop iteration (from existing user action to new user signup).

Formula:

Cycle Time = Time from user action (invite/share) to invitee signup

Impact: A shorter cycle time compounds growth faster, even at the same K-factor.

Example:

Product A: K = 0.5, cycle time = 2 days
Product B: K = 0.5, cycle time = 30 days
After 60 days, Product A has completed 30 cycles; Product B has completed 2

How to shorten cycle time:

Reduce time between signup and first share/invite action
Reduce friction in the invite delivery (instant vs email delay)
Reduce time for invitee to see and act on invitation
Reduce signup friction for invitees
Reduce time for new user to reach the sharing trigger themselves

定义： 完成一次完整病毒循环迭代所需的时间（从现有用户执行操作到新用户注册的时间）。

公式：

Cycle Time = 用户执行操作（邀请/分享）到被邀请人注册的时间

影响： 即使K系数相同，更短的循环周期会让增长更快地复合。

示例：

产品A：K = 0.5，循环周期 = 2天
产品B：K = 0.5，循环周期 = 30天
60天后，产品A完成了30次循环；产品B仅完成2次

如何缩短循环周期：

缩短从注册到首次分享/邀请操作的时间
减少邀请传递过程中的阻碍（即时发送 vs 邮件延迟）
减少被邀请人查看并响应邀请的时间
减少被邀请人的注册阻碍
减少新用户到达分享触发点的时间

3.3 Viral Growth Model

3.3 病毒式增长模型

Starting users: U0
After 1 cycle: U0 + (U0 x K) = U0 x (1 + K)
After 2 cycles: U0 x (1 + K + K^2)
After n cycles: U0 x (1 + K + K^2 + ... + K^n) = U0 x (1 - K^(n+1)) / (1 - K)

If K < 1, this converges to: U0 / (1 - K) (total users at infinite time)
If K >= 1, growth is unbounded (until market saturation)

Example calculation:

1,000 starting users, K = 0.4, cycle time = 7 days
After 4 weeks (4 cycles): 1,000 x (1 + 0.4 + 0.16 + 0.064 + 0.0256) = ~1,650 users
At convergence: 1,000 / (1 - 0.4) = ~1,667 total users from this cohort

初始用户数: U0
1次循环后: U0 + (U0 x K) = U0 x (1 + K)
2次循环后: U0 x (1 + K + K^2)
n次循环后: U0 x (1 + K + K^2 + ... + K^n) = U0 x (1 - K^(n+1)) / (1 - K)

如果 K < 1，最终收敛到: U0 / (1 - K)（无限时间后的总用户数）
如果 K >= 1，增长无上限（直到市场饱和）

示例计算：

初始用户1000人，K = 0.4，循环周期 = 7天
4周后（4次循环）：1000 x (1 + 0.4 + 0.16 + 0.064 + 0.0256) = ~1650位用户
最终收敛值：1000 / (1 - 0.4) = ~1667位用户（来自该初始 cohort）

4. Network Effects vs Virality

4. 网络效应 vs 病毒式传播

These concepts are related but distinct:

Aspect	Network Effects	Virality
Definition	Product becomes more valuable as more users join	Product usage causes more users to join
Focus	Value creation	Distribution
Metric	Value per user as network grows	K-factor, viral cycle time
Example	Slack is better with more team members (value)	Slack invitations bring in new teams (growth)
Defensibility	Strong moat (hard to leave)	Weak moat (can be copied)

这两个概念相关但不同：

维度	网络效应	病毒式传播
定义	随着用户数量增加，产品价值提升	使用产品的行为会吸引更多用户加入
关注点	价值创造	用户获取
核心指标	网络规模扩大时的单用户价值	K系数、病毒循环周期
示例	Slack的用户越多，团队协作价值越高（价值）	Slack的邀请机制吸引新团队加入（增长）
防御性	强大的护城河（难以迁移）	较弱的护城河（易被复制）

Network Effect Types

网络效应类型

Direct (same-side) network effects:

Every user benefits from every other user on the same side
Examples: Communication tools (Slack, WhatsApp), social networks (Facebook, LinkedIn)
Strength: Very strong moat once established

Cross-side (indirect) network effects:

Two distinct user groups, each benefits from the other group's size
Examples: Marketplaces (Airbnb hosts + guests), platforms (iOS developers + users)
Strength: Strong moat but requires balancing both sides

Data network effects:

Product improves as more usage data is collected
Examples: Search engines (Google), recommendation systems (Spotify), ML products
Strength: Moderate moat, compounds over time

Products can have both network effects AND virality. Figma has collaboration network effects (more users = more valuable workspace) and viral loops (sharing designs invites new users).

直接（同边）网络效应：

每个用户都能从同一边的其他用户身上获益
示例：通讯工具（Slack、WhatsApp）、社交网络（Facebook、LinkedIn）
优势：一旦建立，护城河极强

交叉（间接）网络效应：

存在两个不同的用户群体，每个群体都能从另一个群体的规模扩大中获益
示例：市场平台（Airbnb房东+房客）、生态平台（iOS开发者+用户）
优势：护城河较强，但需要平衡两边用户

数据网络效应：

随着使用数据的积累，产品不断优化
示例：搜索引擎（Google）、推荐系统（Spotify）、ML产品
优势：护城河中等，随时间不断强化

产品可同时具备网络效应和病毒式传播特性。 Figma具备协作网络效应（用户越多，工作空间价值越高）和病毒式循环（分享设计邀请新用户）。

5. How to Design a Viral Loop: Step-by-Step

5. 如何设计病毒式循环：分步指南

Step 1: Identify the Natural Sharing Trigger

步骤1：识别天然的分享触发点

Ask: "When does a user NEED or genuinely WANT to involve someone else?"

Trigger categories:

Functional need: "I need my teammate to review this" (collaboration)
Social impulse: "I want to show this to my friend" (content sharing)
Value sharing: "This would help my colleague" (recommendation)
Achievement: "Look what I created/accomplished" (status)
Requirement: "This form needs to be filled out by someone else" (workflow)

Exercise: Map your user journey and mark every moment where involving another person would be natural. Rank by frequency and strength of impulse.

提问：「用户何时需要或真正想要邀请他人参与？」

触发点分类：

功能需求：「我需要我的队友审核这个」（协作）
社交冲动：「我想把这个展示给朋友」（内容分享）
价值分享：「这个对我的同事有帮助」（推荐）
成就感：「看我创建/完成的成果」（身份展示）
流程要求：「这个表单需要其他人填写」（工作流）

练习： 梳理用户旅程，标记所有天然适合邀请他人参与的时刻，并按发生频率和冲动强度排序。

Step 2: Reduce Friction in the Sharing Action

步骤2：减少分享操作中的阻碍

Every click, form field, and decision between the trigger and the share reduces conversion.

Friction audit:

How many clicks from trigger to share completed? (Target: 1-3)
Does sharing require leaving the current workflow? (Should not)
Are default sharing options pre-selected intelligently? (Email, link, etc.)
Is the share content pre-populated? (Default message, preview)
Can the user customize the share? (Optional, not required)

从触发点到完成分享之间的每一次点击、表单字段和决策都会降低转化率。

阻碍审核：

从触发点到完成分享需要点击多少次？（目标：1-3次）
分享操作是否需要离开当前工作流？（不应如此）
是否智能预选了默认分享选项？（邮件、链接等）
分享内容是否已预填充？（默认消息、预览）
用户是否可自定义分享内容？（可选，非必填）

Step 3: Optimize the Recipient Experience

步骤3：优化接收者体验

The person receiving the invitation or shared content is the most critical conversion point.

Recipient experience checklist:

Can they understand what they are being invited to without prior context?
Can they preview value before signing up? (See the document, view the content)
Is the signup flow minimal? (SSO, magic link, pre-filled information)
After signup, are they placed directly into the relevant context? (The shared doc, workspace, content)
Do they experience value within the first session?

接收邀请或分享内容的人是最关键的转化节点。

接收者体验检查清单：

无需前置背景知识，他们就能理解被邀请的内容
注册前可预览价值（查看文档、内容）
注册流程极简（SSO、魔法链接、预填充信息）
注册后直接进入相关场景（共享文档、工作空间、内容）
在首次使用会话中就能体验到价值

Step 4: Ensure Quick Time-to-Value for New Users

步骤4：确保新用户快速获得价值

If the invitee signs up but does not quickly experience value, the loop breaks.

Quick wins for invitee activation:

Skip generic onboarding, go directly to the shared context
Pre-populate the workspace with relevant content
Show a contextual tutorial if needed (but keep it brief)
Ensure the collaboration/interaction with the inviter works immediately

如果被邀请人注册后无法快速体验到价值，循环就会断裂。

帮助被邀请人激活的快速方法：

跳过通用入职流程，直接进入共享场景
预填充与用户相关的内容到工作空间
如有需要，提供场景化教程（但要简短）
确保与邀请人的协作/互动能立即生效

Step 5: Close the Loop

步骤5：闭合循环

The new user must become a potential sharer/inviter themselves.

Loop closure tactics:

Surface the sharing trigger to new users (don't assume they will find it)
Demonstrate the value of sharing through the experience they just had (they were invited, so they understand the value of inviting)
Remove barriers to the new user's first share
Track where in the journey new users fail to close the loop

新用户必须成为潜在的分享者/邀请者。

闭合循环策略：

向新用户展示分享触发点（不要假设他们能自己找到）
通过他们刚经历的体验展示分享的价值（他们被邀请过，因此理解邀请的价值）
消除新用户首次分享的障碍
跟踪新用户在旅程中哪个环节未能完成循环

6. Invite Mechanics

6. 邀请机制

6.1 Invite Channels

6.1 邀请渠道

Channel	Pros	Cons	Best For
Email invite	Professional, trackable, rich content	Lower open rates, spam risk	B2B, team invites
Link sharing	Universal, frictionless, multi-channel	Less trackable, no context	B2C, casual sharing
Social sharing	High reach, viral potential	Noisy, low conversion	Consumer products, content
In-product invite	Contextual, high intent	Limited to current users	Team tools, collaboration
Contacts import	High volume, familiar	Privacy concerns, can feel spammy	Communication tools
QR code	Works offline, visual	Niche use cases	Events, physical products

渠道	优势	劣势	最佳适用场景
邮件邀请	专业、可追踪、内容丰富	打开率较低、有被标记为垃圾邮件的风险	B2B、团队邀请
链接分享	通用、无阻碍、多渠道支持	追踪性差、无场景背景	B2C、非正式分享
社交分享	覆盖范围广、病毒潜力高	信息嘈杂、转化率低	消费级产品、内容类产品
产品内邀请	场景化、意图明确	仅面向当前用户	团队工具、协作类产品
联系人导入	批量操作、熟悉度高	隐私问题、可能被视为垃圾信息	通讯工具
二维码	支持离线使用、视觉化	适用场景小众	活动、实体产品

6.2 Invite Flow Design

6.2 邀请流程设计

Trigger moment (user wants to share/invite)
├── Share/invite button (prominent, contextual)
│   ├── Quick share: Copy link (one click)
│   ├── Email invite: Enter email(s) + optional message
│   ├── Social share: Platform picker with pre-populated content
│   └── In-product: Search/select existing users or contacts
├── Preview: Show what the recipient will see
├── Send/Share confirmation
├── Post-share: Success message + "Invite more" option
└── Tracking: Attribute signups to this share action

触发时刻（用户想要分享/邀请）
├── 分享/邀请按钮（显眼、场景化）
│   ├── 快速分享：复制链接（一键操作）
│   ├── 邮件邀请：输入邮箱 + 可选消息
│   ├── 社交分享：平台选择器 + 预填充内容
│   └── 产品内邀请：搜索/选择现有用户或联系人
├── 预览：展示接收者将看到的内容
├── 发送/分享确认
├── 分享后：成功提示 + 「邀请更多人」选项
└── 追踪：将注册归因于本次分享操作

7. Referral Incentive Design

7. 推荐激励设计

When natural virality is insufficient, incentivize sharing.

当自然病毒式传播效果不足时，可通过激励措施促进分享。

7.1 Two-Sided Rewards

7.1 双向奖励

Both the referrer and the referred person receive value. This works best because it gives the referrer a non-selfish reason to share.

Examples:

Product	Referrer Gets	Referred Gets
Dropbox	500MB extra storage	500MB extra storage
Uber	$10 ride credit	$10 ride credit
Robinhood	Free stock	Free stock

邀请者和被邀请者都能获得奖励。这种方式效果最佳，因为它给了邀请者一个非利己的分享理由。

示例：

产品	邀请者奖励	被邀请者奖励
Dropbox	额外500MB存储空间	额外500MB存储空间
Uber	10美元乘车信用额度	10美元乘车信用额度
Robinhood	免费股票	免费股票

7.2 Reward Timing

7.2 奖励时机

Timing	Mechanism	When to Use
Immediate	Reward on signup	High-volume, low-fraud environments
On activation	Reward when referred user completes key action	Prevents gaming, ensures quality
On conversion	Reward when referred user pays	B2B, high-value products
Tiered/progressive	Increasing rewards for more referrals	Sustained referral behavior

时机	机制	适用场景
即时奖励	注册即奖励	高流量、低欺诈风险环境
激活后奖励	被邀请用户完成关键操作后奖励	防止作弊，确保用户质量
转化后奖励	被邀请用户付费后奖励	B2B、高价值产品
分层/递进奖励	邀请人数越多，奖励越丰厚	维持长期推荐行为

7.3 Reward Type Selection

7.3 奖励类型选择

Reward Type	Pros	Cons	Best For
Product credits	Low cost, drives usage	Only valuable to active users	SaaS, usage-based products
Cash/gift cards	Universally appealing	Higher cost, tax implications	Consumer products
Feature unlock	Zero marginal cost	Only works if features are desirable	Freemium products
Extended trial	Low cost, drives activation	Limited appeal	Trial-based products
Swag/physical	Memorable, shareable	Logistics, cost	Brand-building, loyal users

奖励类型	优势	劣势	最佳适用场景
产品信用额度	成本低、促进产品使用	仅对活跃用户有价值	SaaS、按使用量付费产品
现金/礼品卡	普适性强	成本高、涉及税务问题	消费级产品
功能解锁	边际成本为零	仅当功能具备吸引力时有效	免费增值产品
延长试用期	成本低、促进激活	吸引力有限	基于试用期的产品
周边/实物礼品	令人难忘、可分享	物流复杂、成本高	品牌建设、忠实用户

8. Viral Content Design

8. 病毒式内容设计

Make product output inherently shareable.

让产品输出内容具备天然的可分享性。

8.1 Shareable Output Checklist

8.1 可分享输出内容检查清单

Product output has a public URL (viewable without login)
Output includes subtle product branding (watermark, footer, "Made with X")
Output looks professional and reflects well on the creator
Output includes a clear CTA for viewers ("Create your own")
Output is optimized for social sharing (OG tags, preview images, descriptions)
Output is embeddable in other platforms (embed codes, iframes)

产品输出内容具备公共URL（无需登录即可查看）
输出内容包含细微的产品品牌标识（水印、页脚、「由X制作」）
输出内容看起来专业，能为创作者增光
输出内容包含清晰的观众CTA（「创建你的内容」）
输出内容针对社交分享优化（OG标签、预览图、描述）
输出内容可嵌入其他平台（嵌入代码、iframe）

8.2 Social Sharing Optimization

8.2 社交分享优化

Open Graph tags for shared content:
- og:title: [Content title or "Check out my [product output]"]
- og:description: [Compelling description of the content]
- og:image: [High-quality preview image, 1200x630px]
- og:url: [Canonical URL of the content]
- twitter:card: summary_large_image

分享内容的Open Graph标签：
- og:title: [内容标题或「看看我的[产品输出]」]
- og:description: [内容的吸引人描述]
- og:image: [高质量预览图，尺寸1200x630px]
- og:url: [内容的标准URL]
- twitter:card: summary_large_image

9. Measuring Virality

9. 病毒式增长度量

9.1 Core Metrics

9.1 核心指标

Metric	Formula	Target
K-factor	Invites per user x Invite conversion rate	> 0.3 for meaningful impact
Viral cycle time	Median days from share to new signup	< 7 days ideal
Invite send rate	Users who send invites / Total active users	> 10%
Invite-to-signup rate	Signups from invites / Invites sent	> 10%
Viral attribution	Signups from viral channels / Total signups	Track trend
Loop completion rate	New users who become sharers / New users from sharing	> 20%

指标	公式	目标
K系数	每位用户发送的邀请数 × 邀请转化率	> 0.3（产生有意义的影响）
病毒循环周期	从分享到新用户注册的中位天数	< 7天（理想状态）
邀请发送率	发送邀请的用户数 / 总活跃用户数	> 10%
邀请到注册转化率	来自邀请的注册数 / 发送的邀请数	> 10%
病毒归因	来自病毒渠道的注册数 / 总注册数	跟踪趋势
循环完成率	成为分享者的新用户数 / 来自分享的新用户数	> 20%

9.2 Channel-Level K-Factor

9.2 渠道级K系数

Calculate K-factor for each viral channel independently:

K_email = (email invites per user) x (email invite conversion rate)
K_link = (link shares per user) x (link share conversion rate)
K_content = (content created per user x content views per piece x viewer signup rate)
K_embed = (embeds per user x embed impressions per embed x impression-to-signup rate)

K_total = K_email + K_link + K_content + K_embed

独立计算每个病毒渠道的K系数：

K_email = (每位用户发送的邮件邀请数) × (邮件邀请转化率)
K_link = (每位用户分享的链接数) × (链接分享转化率)
K_content = (每位用户创建的内容数 × 单条内容的浏览量 × 浏览者注册率)
K_embed = (每位用户创建的嵌入数 × 单个嵌入的曝光量 × 曝光到注册的转化率)

K_total = K_email + K_link + K_content + K_embed

9.3 Viral Loop Funnel

9.3 病毒循环漏斗

Track each step of the loop as a funnel:

Step 1: Active users                          [N users]
Step 2: Users who reach sharing trigger       [N] ([X]% of step 1)
Step 3: Users who initiate a share/invite     [N] ([X]% of step 2)
Step 4: Users who complete a share/invite     [N] ([X]% of step 3)
Step 5: Invitees who receive the share        [N] ([X]% of step 4)
Step 6: Invitees who view the share/landing   [N] ([X]% of step 5)
Step 7: Invitees who sign up                  [N] ([X]% of step 6)
Step 8: New users who activate                [N] ([X]% of step 7)
Step 9: New users who reach sharing trigger   [N] ([X]% of step 8)

The biggest drop-off in this funnel tells you where to focus optimization.

将循环的每个步骤作为漏斗进行跟踪：

步骤1：活跃用户                          [N位用户]
步骤2：到达分享触发点的用户       [N]（占步骤1的[X]%）
步骤3：发起分享/邀请的用户     [N]（占步骤2的[X]%）
步骤4：完成分享/邀请的用户     [N]（占步骤3的[X]%）
步骤5：收到分享的被邀请人        [N]（占步骤4的[X]%）
步骤6：查看分享/落地页的被邀请人   [N]（占步骤5的[X]%）
步骤7：注册的被邀请人                  [N]（占步骤6的[X]%）
步骤8：激活的新用户                [N]（占步骤7的[X]%）
步骤9：到达分享触发点的新用户   [N]（占步骤8的[X]%）

漏斗中流失最严重的环节就是你需要重点优化的地方。

10. Anti-Patterns

10. 反模式

Anti-Pattern	Why It Fails	Better Alternative
Forced invitations	"Invite 5 friends to continue"	Creates resentment, low-quality invites
Spam tactics	Auto-emailing user's contacts	Destroys trust, may violate laws
Meaningless sharing	"Share this with friends!" with no context	No motivation, low conversion
Gaming metrics	Inflating K-factor with bots or incentive abuse	Vanity metrics, no real growth
Ignoring recipient experience	Invitee lands on generic homepage	High drop-off, broken loop
Over-incentivizing	Reward is the only reason to share	Attracts low-quality, mercenary users

反模式	失败原因	更好的替代方案
强制邀请	「邀请5位好友才能继续」	引发反感，邀请质量低
垃圾信息策略	自动给用户的联系人发送邮件	破坏信任，可能违反法律
无意义分享	「和朋友分享这个！」但无场景背景	缺乏动机，转化率低
指标作弊	使用机器人或激励滥用抬高K系数	虚荣指标，无真实增长
忽视接收者体验	被邀请人跳转到通用首页	流失率高，循环断裂
过度激励	分享的唯一理由是奖励	吸引低质量、逐利用户

11. Output Format

11. 输出格式

When designing a viral loop, produce this specification:

undefined

设计病毒式循环时，请生成以下规格文档：

undefined

Viral Loop Design Specification

病毒式循环设计规格

Loop Type

循环类型

Primary loop type: [Invitation / Collaboration / Content / Embedding / Word-of-mouth]
Secondary loops: [Any additional loop types in play]

主循环类型: [邀请 / 协作 / 内容 / 嵌入 / 口碑]
次要循环: [任何其他生效的循环类型]

Loop Mechanics

循环机制

Trigger: [When/why does the user share or invite?]
Sharing action: [What does the user do to share?]
Channels: [Email, link, social, in-product, embed]
Recipient experience: [What does the invitee see and do?]
Activation: [How does the invitee become a user who can also share?]
Loop closure: [How does the new user become a sharer?]

触发点: [用户何时/为何分享或邀请？]
分享操作: [用户如何分享？]
渠道: [邮件、链接、社交、产品内、嵌入]
接收者体验: [被邀请人看到什么并做什么？]
激活: [被邀请人如何成为可分享的用户？]
循环闭合: [新用户如何成为分享者？]

Incentive Structure (if applicable)

激励结构（如适用）

Referrer reward: [What and when]
Referred reward: [What and when]
Anti-fraud measures: [How you prevent gaming]

邀请者奖励: [奖励内容和时机]
被邀请者奖励: [奖励内容和时机]
反欺诈措施: [如何防止作弊]

Friction Analysis

阻碍分析

Steps from trigger to share completion: [N]
Steps from invite receipt to signup: [N]
Steps from signup to first value: [N]
Identified friction points: [List with severity]

从触发点到完成分享的步骤数: [N]
从收到邀请到注册的步骤数: [N]
从注册到首次获得价值的步骤数: [N]
已识别的阻碍点: [列出并标注严重程度]

Current Metrics (if existing loop)

当前指标（如果已有循环）

K-factor: [Current value]
Viral cycle time: [Current value]
Invite send rate: [Current value]
Invite-to-signup conversion: [Current value]

K系数: [当前值]
病毒循环周期: [当前值]
邀请发送率: [当前值]
邀请到注册转化率: [当前值]

Target Metrics

目标指标

K-factor target: [...]
Viral cycle time target: [...]
Invite send rate target: [...]
Invite-to-signup conversion target: [...]

K系数目标: [...]
病毒循环周期目标: [...]
邀请发送率目标: [...]
邀请到注册转化率目标: [...]

Measurement Plan

度量计划

Funnel tracking: [Steps to instrument]
Attribution: [How you track viral signups]
Reporting cadence: [Weekly / Monthly]

漏斗跟踪: [需要埋点的步骤]
归因: [如何跟踪病毒注册用户]
报告频率: [每周 / 每月]

Implementation Priorities

实施优先级

[Highest-impact change]
[Second priority]
[Third priority]

[影响最大的变更]
[第二优先级]
[第三优先级]

Risks and Mitigations

风险与缓解措施


---

Related skills: `referral-program`, `growth-loops`, `engagement-loops`


---

相关技能: `referral-program`, `growth-loops`, `engagement-loops`

viral-loops

Original

Translation

Viral Loops

病毒式循环

1. Diagnostic Questions

1. 诊断问题

2. Viral Loop Types

2. 病毒式循环类型

2.1 Invitation Loops

2.1 邀请循环

2.2 Collaboration Loops

2.2 协作循环

2.3 Content/UGC Loops

2.3 内容/UGC循环

2.4 Embedding Loops

2.4 嵌入循环

2.5 Word-of-Mouth Loops

2.5 口碑循环

3. Viral Math

3. 病毒式增长数学

3.1 K-Factor (Viral Coefficient)

3.1 K-Factor（病毒系数）

3.2 Viral Cycle Time

3.2 病毒循环周期

3.3 Viral Growth Model

3.3 病毒式增长模型

4. Network Effects vs Virality

4. 网络效应 vs 病毒式传播

Network Effect Types

网络效应类型

5. How to Design a Viral Loop: Step-by-Step

5. 如何设计病毒式循环：分步指南

Step 1: Identify the Natural Sharing Trigger

步骤1：识别天然的分享触发点

Step 2: Reduce Friction in the Sharing Action

步骤2：减少分享操作中的阻碍

Step 3: Optimize the Recipient Experience

步骤3：优化接收者体验

Step 4: Ensure Quick Time-to-Value for New Users

步骤4：确保新用户快速获得价值

Step 5: Close the Loop

步骤5：闭合循环

6. Invite Mechanics

6. 邀请机制

6.1 Invite Channels

6.1 邀请渠道

6.2 Invite Flow Design

6.2 邀请流程设计

7. Referral Incentive Design

7. 推荐激励设计

7.1 Two-Sided Rewards

7.1 双向奖励

7.2 Reward Timing

7.2 奖励时机

7.3 Reward Type Selection

7.3 奖励类型选择

8. Viral Content Design

8. 病毒式内容设计

8.1 Shareable Output Checklist

8.1 可分享输出内容检查清单

8.2 Social Sharing Optimization

8.2 社交分享优化

9. Measuring Virality

9. 病毒式增长度量

9.1 Core Metrics

9.1 核心指标

9.2 Channel-Level K-Factor

9.2 渠道级K系数

9.3 Viral Loop Funnel

9.3 病毒循环漏斗

10. Anti-Patterns

10. 反模式

11. Output Format

11. 输出格式

Viral Loop Design Specification

病毒式循环设计规格

Loop Type

循环类型

Loop Mechanics