Back to Details

user-modeling

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

User Modeling

用户建模

Build just enough understanding of your users to make better product decisions.
建立足够的用户认知，以做出更优的产品决策。

Why This Exists

设计初衷

Creates behavior-based user models that reveal what users need and how they'll behave, not marketing personas with stock photos.
创建基于行为的用户模型，揭示用户的需求与行为模式，而非带有库存照片的营销型用户角色。

Input Requirements

输入要求

This skill works best with:
  • problem-framing
    output (problem statement, target user, JTBD)
  • Any existing research (interviews, surveys, support tickets, Reddit threads, reviews)
Can also work from assumptions if no research exists—but flags that these need validation.
本Skill在以下输入下效果最佳：
  • problem-framing
    输出（问题陈述、目标用户、JTBD）
  • 任何现有研究资料（用户访谈、调研问卷、支持工单、Reddit帖子、用户评价）
若没有研究资料，也可基于假设运行，但会提示这些假设需要验证。

Workflow

工作流程

Step 1: Gather Context

步骤1：收集背景信息

Ingest upstream artifacts or ask:
  • Who are you building this for?
  • What do you know about them already?
  • Have you talked to any potential users?
  • Any data sources—reviews, forums, support tickets?
导入上游产出物或询问以下问题：
  • 你正在为谁开发这款产品？
  • 你目前对他们有哪些了解？
  • 你是否与潜在用户沟通过？
  • 有没有相关数据源——比如用户评价、论坛帖子、支持工单？

Step 2: Identify User Segments

步骤2：识别用户细分群体

Look for meaningful differences in:
  • Goals — What are they trying to accomplish?
  • Context — When/where do they encounter the problem?
  • Constraints — What limits their options?
  • Skill level — How sophisticated are they?
  • Frequency — How often do they face this problem?
Not every difference matters. Focus on differences that change what you'd build.
寻找以下维度的显著差异：
  • 目标——他们想要达成什么？
  • 场景——他们何时/何地遇到该问题？
  • 限制条件——哪些因素限制了他们的选择？
  • 技能水平——他们的专业程度如何？
  • 频率——他们多久会遇到一次这个问题？
并非所有差异都有意义，重点关注那些会影响产品设计方向的差异。

Step 3: Build Personas

步骤3：创建用户角色

For each meaningful segment, create a lightweight persona. Limit to 2-3 personas max—more than that dilutes focus.
针对每个有意义的细分群体，创建一个轻量化用户角色。最多限制为2-3个角色——过多会分散关注点。

Step 4: Define Scenarios

步骤4：定义使用场景

For each persona, define 2-3 concrete scenarios where they'd use the product. These become the basis for user stories and flows.
为每个用户角色定义2-3个具体的产品使用场景。这些场景将成为用户故事与流程设计的基础。

Step 5: Identify Insights

步骤5：提炼洞察

Surface patterns that inform product decisions:
  • What do all personas have in common?
  • Where do they diverge?
  • What would you build differently for each?
Automatically save the output to 
design/02-user-modeling.md
using the Write tool while presenting it to the user.
挖掘可指导产品决策的模式：
  • 所有用户角色有哪些共同点？
  • 他们的差异点在哪里？
  • 针对不同角色，产品设计应做出哪些调整？
在向用户展示结果的同时，会自动使用Write工具将输出内容保存至
design/02-user-modeling.md

Output Format

输出格式

markdown
undefined
markdown
undefined

User Modeling: [Project Name]

User Modeling: [Project Name]

Context

Context

[Brief summary of the problem space and what we know]
Research basis:
  • [Source 1: what it told us]
  • [Source 2: what it told us]
  • [Or: "Based on assumptions—needs validation"]
[Brief summary of the problem space and what we know]
Research basis:
  • [Source 1: what it told us]
  • [Source 2: what it told us]
  • [Or: "Based on assumptions—needs validation"]

Personas

Personas

Persona 1: [Name/Label]

Persona 1: [Name/Label]

[One-line description of who they are]
Goals:
  • [Primary goal]
  • [Secondary goal]
Context:
  • [When they encounter the problem]
  • [Where they encounter it]
  • [What else is going on]
Pain points:
  • [Frustration 1]
  • [Frustration 2]
Current behavior:
  • [How they solve this today]
  • [Tools they use]
  • [Workarounds they've developed]
Constraints:
  • [Time/budget/skill/access limitations]
What success looks like:
  • [How they'd know the problem is solved]
Quote: "[Something they might say that captures their mindset]"
[One-line description of who they are]
Goals:
  • [Primary goal]
  • [Secondary goal]
Context:
  • [When they encounter the problem]
  • [Where they encounter it]
  • [What else is going on]
Pain points:
  • [Frustration 1]
  • [Frustration 2]
Current behavior:
  • [How they solve this today]
  • [Tools they use]
  • [Workarounds they've developed]
Constraints:
  • [Time/budget/skill/access limitations]
What success looks like:
  • [How they'd know the problem is solved]
Quote: "[Something they might say that captures their mindset]"

Persona 2: [Name/Label]

Persona 2: [Name/Label]

[One-line description]
[Same structure]
[One-line description]
[Same structure]

Persona 3: [Name/Label]

Persona 3: [Name/Label]

[One-line description]
[Same structure]
[One-line description]
[Same structure]

Scenarios

Scenarios

Persona 1 Scenarios

Persona 1 Scenarios

Scenario 1.1: [Name]
  • Situation: [Context—what's happening]
  • Trigger: [What prompts them to act]
  • Goal: [What they're trying to accomplish]
  • Current approach: [How they handle it today]
  • Frustration: [What's broken about current approach]
Scenario 1.2: [Name] [Same structure]
Scenario 1.1: [Name]
  • Situation: [Context—what's happening]
  • Trigger: [What prompts them to act]
  • Goal: [What they're trying to accomplish]
  • Current approach: [How they handle it today]
  • Frustration: [What's broken about current approach]
Scenario 1.2: [Name] [Same structure]

Persona 2 Scenarios

Persona 2 Scenarios

Scenario 2.1: [Name] [Same structure]
Scenario 2.1: [Name] [Same structure]

Key Insights

Key Insights

Commonalities

Commonalities

[What all personas share—these are table-stakes features]
  • [Insight 1]
  • [Insight 2]
[What all personas share—these are table-stakes features]
  • [Insight 1]
  • [Insight 2]

Divergences

Divergences

[Where personas differ—these inform prioritization]
  • [Persona 1] needs [X], while [Persona 2] needs [Y]
  • [Persona 1] is [context], while [Persona 2] is [different context]
[Where personas differ—these inform prioritization]
  • [Persona 1] needs [X], while [Persona 2] needs [Y]
  • [Persona 1] is [context], while [Persona 2] is [different context]

Design Implications

Design Implications

[How this should influence what you build]
  • [Implication 1]
  • [Implication 2]
  • [Implication 3]
[How this should influence what you build]
  • [Implication 1]
  • [Implication 2]
  • [Implication 3]

Validation Needed

Validation Needed

[What assumptions need testing]
  • [Assumption to validate]
  • [Assumption to validate]
undefined
[What assumptions need testing]
  • [Assumption to validate]
  • [Assumption to validate]
undefined

Adaptation Guidelines

适配指南

Minimal (single obvious user type):
  • One persona, 2-3 scenarios
  • Skip Divergences section
  • 1 page total
Standard (2-3 user types):
  • Full structure as shown
  • 2-3 pages total
Research-heavy (actual user data):
  • Include research summary
  • Add quotes from real users
  • Link to source data in appendix
极简模式（单一明确用户类型）：
  • 1个用户角色，2-3个场景
  • 跳过差异部分
  • 总篇幅1页
标准模式（2-3个用户类型）：
  • 使用上述完整结构
  • 总篇幅2-3页
重研究模式（真实用户数据）：
  • 包含研究摘要
  • 添加真实用户的引用
  • 在附录中链接至数据源

What Makes a Good Persona

优质用户角色的标准

Good persona:
  • Defined by goals and behaviors, not demographics
  • Reveals something that changes what you'd build
  • Based on patterns, not individuals
  • Specific enough to make decisions against
Bad persona:
  • Stock photo + age + job title + hobbies
  • So generic it could be anyone
  • Based on one interview or pure assumption
  • Doesn't inform any product decisions
优质用户角色：
  • 基于目标与行为定义，而非人口统计学特征
  • 揭示会影响产品设计的关键信息
  • 基于模式提炼，而非单个用户
  • 足够具体，可用于指导决策
劣质用户角色：
  • 仅包含库存照片+年龄+职位+爱好
  • 过于通用，适用于任何人
  • 基于单次访谈或纯粹的假设
  • 无法为产品决策提供任何指导

Anti-Patterns to Avoid

需避免的反模式

  • The Kitchen Sink — Don't add demographics unless they matter
  • The Clone Army — If personas don't differ meaningfully, merge them
  • The Wishful Thinker — Model who users are, not who you wish they were
  • The Edge Case Collector — Focus on primary users, not every possible user
  • 面面俱到——除非人口统计学特征有影响，否则不要添加
  • 克隆军团——如果用户角色没有显著差异，应将其合并
  • 一厢情愿——建模真实的用户，而非你期望的用户
  • 边缘案例收集器——聚焦核心用户，而非所有可能的用户

Handoff

后续衔接

After presenting the personas, ask:
"Want to move to 
/solution-scoping
to prioritize features, or straight to 
/prd-generation
?"
Note: File is automatically saved to 
design/02-user-modeling.md
for context preservation.
在展示用户角色后，询问：
"是否要进入
/solution-scoping
进行功能优先级排序，还是直接进入
/prd-generation
？"
注意： 文件会自动保存至
design/02-user-modeling.md
以留存上下文。