user-research

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

User Research

用户研究

Frameworks for building deep user understanding through structured research methods. Covers personas, journey mapping, interviews, usability testing, and Jobs-to-be-Done.

通过结构化研究方法建立深度用户认知的框架。涵盖Persona（用户角色）、旅程地图、用户访谈、可用性测试以及Jobs-to-Be-Done（待完成工作）方法。

Research Method Selection

研究方法选择

Choose the right method for your question:

Method	When to Use	Sample Size	Time	Output
User Interviews	Early discovery, deep understanding	5-8	2-3 weeks	Qualitative insights
Usability Testing	Validate designs, find issues	5-10	1-2 weeks	Actionable fixes
Surveys	Quantify attitudes, preferences	100+	1-2 weeks	Statistical data
Card Sorting	Information architecture	15-30	1 week	IA recommendations
A/B Testing	Compare alternatives	1000+	2-4 weeks	Statistical winner

Rule of thumb: Start with interviews (5-8 participants) to discover unknowns. Switch to surveys once you have hypotheses to validate.

根据你的问题选择合适的方法：

方法	适用场景	样本量	耗时	产出
用户访谈	早期探索、深度认知	5-8	2-3周	定性洞察
可用性测试	验证设计、发现问题	5-10	1-2周	可落地的修复方案
问卷调查	量化用户态度、偏好	100+	1-2周	统计数据
卡片分类法	信息架构设计	15-30	1周	信息架构建议
A/B测试	对比方案优劣	1000+	2-4周	统计得出的最优方案

经验法则： 先通过访谈（5-8名参与者）探索未知信息。当你有假设需要验证时，再转向问卷调查。

Persona Quick Reference

Persona快速参考

Personas are fictional composites built from research synthesis. Keep to 3-5 max.

markdown

undefined

Persona是基于研究综合得出的虚构用户画像，最多保留3-5个。

markdown

undefined

Persona: [Name]

Persona: [姓名]

Demographics

人口统计信息

Age: [Range]
Role: [Job title]
Company: [Type/size]
Tech savviness: [Low/Medium/High]

年龄: [区间]
职位: [岗位名称]
公司: [类型/规模]
技术熟练度: [低/中/高]

Quote

代表性语录

"[Characteristic statement that captures their mindset]"

"[能体现其心态的典型表述]"

Goals

目标

[Primary goal - what success looks like]
[Secondary goal]

[核心目标 - 成功的定义]
[次要目标]

Pain Points

痛点

[Frustration with current state]
[Obstacle they face]

[对当前状态的不满]
[面临的障碍]

Key Insight

关键洞察

[The most important thing to remember about this persona]


**Incorrect — vague persona without goals:**
```markdown
Persona: Sarah, Age 35, Marketing Manager. Likes social media and coffee.

Correct — actionable persona with goals and pain points:

markdown

Persona: DevOps Dana
Quote: "I don't have time for tools that create more work than they save."
Goals: Reduce deployment failures, give devs self-service capabilities
Pain Points: Alert fatigue from false positives, context-switching between 10+ tools
Key Insight: Evaluates tools by "time saved vs. time invested" — needs immediate value.

[关于该Persona最需要记住的要点]


**错误示例——模糊且无目标的Persona：**
```markdown
Persona: Sarah, 35岁，营销经理。喜欢社交媒体和咖啡。

正确示例——具备可落地价值、包含目标与痛点的Persona：

markdown

Persona: DevOps Dana
语录: "我没时间用那些带来的麻烦比解决的问题还多的工具。"
目标: 减少部署故障，为开发人员提供自助服务能力
痛点: 误报导致的告警疲劳，在10+个工具间来回切换
关键洞察: 以“节省时间vs投入时间”评估工具——需要即时价值。

Journey Map Structure

旅程地图结构

Maps the end-to-end experience for a specific persona and scenario.

markdown

undefined

针对特定Persona和场景绘制端到端体验地图。

markdown

undefined

Journey Map: [Journey Name]

旅程地图: [旅程名称]

Persona + Scenario

Persona + 场景

[Which persona | What they're trying to accomplish]

[对应的Persona | 他们试图完成的任务]

Stages: Aware → Consider → Purchase → Onboard → Use → Retain

阶段: 认知 → 考虑 → 购买 → 入门 → 使用 → 留存

For each stage:

Touchpoints: [Channel/interaction point]
Actions: [What user does]
Emotions: [Satisfied / Neutral / Frustrated]
Pain Points: [Friction]
Opportunities: [How we improve]


Common B2B SaaS stages: `Awareness → Evaluation → Purchase → Onboarding → Adoption → Expansion → Advocacy/Churn`

每个阶段包含：

触点: [渠道/交互点]
行为: [用户的操作]
情绪: [满意 / 中立 / 沮丧]
痛点: [摩擦点]
优化机会: [我们如何改进]


常见B2B SaaS阶段：`认知 → 评估 → 购买 → 入门 → 采用 → 拓展 → 推荐/流失`

JTBD Framework

JTBD框架

People don't buy products — they hire them to do specific jobs.

JTBD Statement Format:

When [situation], I want to [motivation], so I can [expected outcome].

Example:

When I'm preparing for a board review, I want to quickly see revenue trends,
so I can answer questions confidently without scrambling for data.

Job Dimensions:

Dimension	Description
Functional	Practical task to accomplish
Emotional	How the user wants to feel
Social	How the user wants to be perceived

Opportunity Score:

Importance + (Importance - Satisfaction)

— scores > 10 indicate high-opportunity areas.

人们购买产品不是为了拥有它——而是“雇佣”它来完成特定工作。

JTBD表述格式：

当[场景]时，我想要[动机]，这样我就能[预期结果]。

示例：

当我准备董事会汇报时，我想要快速查看收入趋势，
这样我就能从容回答问题，不用慌乱找数据。

工作维度：

维度	描述
功能性	要完成的实际任务
情感性	用户期望的感受
社会性	用户期望被他人如何看待

机会评分：

重要性 + (重要性 - 满意度)

——评分>10表示高机会领域。

Empathy Map

共情地图

Quick tool for building shared understanding in workshops:

+-------------------------+-------------------------------+
|         SAYS            |            THINKS             |
| Direct quotes           | Worries and concerns          |
| Questions asked         | Aspirations                   |
+-------------------------+-------------------------------+
|         DOES            |            FEELS              |
| Observable actions      | Emotional state               |
| Workarounds             | Frustrations and delights     |
+-------------------------+-------------------------------+
|         PAINS           |            GAINS              |
| Fears and obstacles     | Wants and needs               |
+-------------------------+-------------------------------+

用于在工作坊中建立共识的快速工具：

+-------------------------+-------------------------------+
|         所言            |            所思               |
| 直接引用的话语           | 担忧与顾虑                     |
| 提出的问题               | 期望与目标                     |
+-------------------------+-------------------------------+
|         所行            |            所感               |
| 可观察到的行为           | 情绪状态                       |
| 变通方案                 | 不满与愉悦点                   |
+-------------------------+-------------------------------+
|         痛点            |            增益               |
| 恐惧与障碍               | 需求与诉求                     |
+-------------------------+-------------------------------+

Interview Best Practices

访谈最佳实践

Do	Don't
Ask open-ended questions	Ask leading questions
Ask "why" and "how"	Accept surface answers
Follow interesting threads	Stick rigidly to script
Take verbatim notes	Paraphrase or interpret

Standard interview arc: Warm-up (5 min) → Context setting (10 min) → Deep dive (25 min) → Wrap-up (5 min)

建议	禁忌
提出开放式问题	提出诱导性问题
追问“为什么”和“如何”	满足于表面答案
跟进有趣的线索	严格固守脚本
逐字记录	转述或解读

标准访谈流程： 暖场（5分钟）→ 背景介绍（10分钟）→ 深度探讨（25分钟）→ 收尾（5分钟）

Rules (Load On-Demand)

规则（按需加载）

Read these files for detailed guidance:

research-personas.md — Persona template, empathy map, maintenance schedule
research-journey-mapping.md — Journey map template, service blueprints, experience curves
research-user-interviews.md — Interview structure, usability testing, NPS/SUS, card sorting

阅读以下文件获取详细指导：

research-personas.md —— Persona模板、共情地图、维护计划
research-journey-mapping.md —— 旅程地图模板、服务蓝图、体验曲线
research-user-interviews.md —— 访谈结构、可用性测试、NPS/SUS、卡片分类法

user-research

Original

Translation

User Research

用户研究

Research Method Selection

研究方法选择

Persona Quick Reference

Persona快速参考

Persona: [Name]

Persona: [姓名]

Demographics

人口统计信息

Quote

代表性语录

Goals

目标

Pain Points

痛点

Key Insight

关键洞察

Journey Map Structure

旅程地图结构

Journey Map: [Journey Name]

旅程地图: [旅程名称]

Persona + Scenario

Persona + 场景

Stages: Aware → Consider → Purchase → Onboard → Use → Retain

阶段: 认知 → 考虑 → 购买 → 入门 → 使用 → 留存

JTBD Framework

JTBD框架

Empathy Map

共情地图

Interview Best Practices

访谈最佳实践

Rules (Load On-Demand)

规则（按需加载）

References

参考资料

Related Skills

相关技能