usability-tester

可用性测试员

通过系统观察，验证用户能否成功完成核心任务。

核心原则

观察用户遇到困难。 发现 UX 问题的最佳方法是观察真实用户尝试完成真实任务。他们遇到的困难揭示了调查问卷和分析数据无法呈现的真相。

测试规划

1. 定义测试目标

Good Objectives:
  - "Can users complete onboarding in <5 minutes?"
  - "Can users find and use the export feature?"
  - "Do users understand the pricing page?"

Bad Objectives:
  - "Test the UI" (too vague)
  - "See if users like it" (subjective, not behavioral)

2. 研究问题

Examples:
  - Where do users get stuck during sign-up?
  - Can users find the settings page?
  - Do users understand what each tier includes?
  - What errors do users encounter?

3. 确定核心任务

选择 3-5 个能够代表关键用户旅程的任务：

Example Tasks (Project Management Tool): 1. Sign up and create account
  2. Create your first project
  3. Invite a team member
  4. Assign a task to someone
  5. Export project data

4. 招募参与者

Sample Size:
  - 5-8 users per persona
  - After 5 users, diminishing returns (Nielsen's research)
  - Test in waves: 5 users → fix issues → test 5 more

Recruitment Criteria:
  - Match target persona
  - Haven't used product before (for onboarding tests)
  - Or: Active users (for feature tests)

Incentives:
  - $50-100 per hour (B2C)
  - $100-200 per hour (B2B professionals)
  - Gift cards work well

任务场景

最佳实践

✅ 好的任务场景：

"Your team is launching a new project next week. Create a project
called 'Q2 Launch' and invite [email protected] to collaborate."

有效原因：

• 情境真实
• 目标明确
• 使用自然语言
• 不提供逐步说明

❌ 差的任务场景：

"Click the 'New Project' button, then enter 'Q2 Launch', then
click Settings, then click Invite, then enter email."

无效原因：

• 提供逐步说明
• 没有情境
• 无法测试易发现性
• 用户只是在照做

任务场景模板

Scenario: [Context/Motivation]
Goal: [What they need to accomplish]
Success Criteria: [How to know they completed it]

Example:
  Scenario: You're preparing for a client meeting tomorrow and need to review past conversations.
  Goal: Find all conversations with "Acme Corp" from the last 30 days
  Success Criteria: User successfully uses search/filter to find conversations

开展测试

出声思考协议

给参与者的关键指示：

"Please think aloud as you work. Tell me what you're looking for,
what you're thinking, what you're trying to do. There are no
wrong answers - we're testing the product, not you."

需要留意的内容：

• “我在找……”（他们的预期）
• “我以为这里会……”（心智模型）
• “这让人困惑，因为……”（阻碍点）
• “我不确定是否……”（不确定之处）

主持规则

✅ 要做：

• 安静观察
• 做笔记
• 让他们自己尝试（这样才能发现问题）
• 在任务结束后再提出后续问题
• 保持中立

❌ 不要做：

• 提供帮助或解释
• 引导他们（“也许可以试着点击……”）
• 为设计选择辩解
• 在任务进行中打断
• 表现出不耐烦

每项任务结束后要问的问题

Completion Questions:
  - 'On a scale of 1-5, how easy was that task?'
  - 'What were you expecting to see?'
  - 'What was confusing about that?'
  - 'If you could change one thing, what would it be?'

Discovery Questions:
  - 'Where did you expect to find that?'
  - 'What do you think this [feature] does?'
  - 'Why did you click there?'

要跟踪的指标

任务成功率

Measurement:
  - Completed: User achieved goal without help
  - Partial: User achieved goal with hints
  - Failed: User could not complete task

Calculation: Task Success Rate = (Completed Tasks / Total Attempts) × 100

Target: ≥80% for core tasks

任务用时

Measurement:
  - Start timer when task begins
  - Stop when user completes or gives up

Analysis:
  - Compare to baseline/previous tests
  - Identify outliers (very fast or very slow)

Target: Varies by task complexity
  - Simple task (e.g., log in): <30 seconds
  - Medium task (e.g., create project): 1-2 minutes
  - Complex task (e.g., configure integration): 3-5 minutes

错误率

Errors:
  - Wrong path taken
  - Incorrect button clicked
  - Had to backtrack
  - Gave up and tried different approach

Calculation: Errors per Task = Total Errors / Number of Users

Target: <2 errors per task

满意度评分

Post-Task Question:
  "How satisfied are you with completing this task?" (1-5 scale)

  1 = Very Dissatisfied
  2 = Dissatisfied
  3 = Neutral
  4 = Satisfied
  5 = Very Satisfied

Target: ≥4.0 average

问题严重程度评级

严重程度公式

Severity = Impact × Frequency

影响程度量表（1-3）

1 - Low Impact:
  - Minor inconvenience
  - User can easily recover
  - Cosmetic issue

2 - Medium Impact:
  - Causes delay or confusion
  - User eventually figures it out
  - Moderate frustration

3 - High Impact:
  - Blocks task completion
  - User cannot proceed without help
  - Critical to core functionality

发生频率量表（1-3）

1 - Rare:
  - Only 1-2 users encountered
  - Edge case
  - Specific conditions

2 - Occasional:
  - 3-5 users encountered
  - Somewhat common
  - Specific user types

3 - Frequent:
  - Most/all users encountered
  - Consistent issue
  - All user types

综合严重程度

Critical (8-9):
  - Impact: 3, Frequency: 3
  - Blocks most users
  → Fix immediately before release

High (6-7):
  - Impact: 3, Frequency: 2 OR Impact: 2, Frequency: 3
  - Significant delay or frequent minor issue
  → Fix before release

Medium (4-5):
  - Impact: 2, Frequency: 2 OR Impact: 3, Frequency: 1
  - Minor frustration or rare blocker
  → Fix in next release

Low (1-3):
  - Impact: 1, Frequency: 1-3
  - Cosmetic or rare minor issue
  → Backlog

系统可用性量表（SUS）

10 道题的调查问卷（测试后填写，采用 1-5 李克特量表）：

Questions (Odd = Positive, Even = Negative): 1. I think I would like to use this product frequently
  2. I found the product unnecessarily complex
  3. I thought the product was easy to use
  4. I think I would need support to use this product
  5. I found the various functions well integrated
  6. I thought there was too much inconsistency
  7. I imagine most people would learn this quickly
  8. I found the product cumbersome to use
  9. I felt very confident using the product
  10. I needed to learn a lot before getting going

Scoring:
  - Odd questions: Score - 1
  - Even questions: 5 - Score
  - Sum all scores
  - Multiply by 2.5
  - Result: 0-100 score

Interpretation:
  ≥80: Excellent
  68-79: Good (industry average)
  51-67: OK
  <51: Needs significant improvement

测试报告模板

usability_test_summary:
  date: '2024-01-20'
  participants: 8
  participant_profile: 'New users, age 25-45, tech-savvy'

  tasks:
    - task: 'Create a new project'
      success_rate: '87.5% (7/8)'
      avg_time: '1m 24s'
      errors: 1.2 per user
      satisfaction: 4.3/5

    - task: 'Invite team member'
      success_rate: '62.5% (5/8)'
      avg_time: '2m 45s'
      errors: 2.8 per user
      satisfaction: 3.1/5

  issues:
    - issue: "Users can't find 'Invite' button"
      severity: high
      impact: 3
      frequency: 3
      affected_users: 7/8
      recommendation: "Move 'Invite' button to top of project page, make it more prominent"

    - issue: 'Confusion about project vs workspace'
      severity: medium
      impact: 2
      frequency: 3
      affected_users: 6/8
      recommendation: 'Add tooltip explaining difference, update onboarding'

    - issue: 'Export button text unclear'
      severity: low
      impact: 1
      frequency: 2
      affected_users: 2/8
      recommendation: "Change 'Export' to 'Export to CSV'"

  sus_score: 72 (Good)

  key_insights:
    - 'Onboarding is smooth (87.5% success)'
    - 'Team collaboration features hard to discover'
    - 'Overall product easy to use once features are found'

  recommended_actions:
    1. "High priority: Redesign invite flow"
    2. "Medium priority: Add contextual help for workspace vs project"
    3. "Low priority: Update button labels"

远程测试与现场测试

远程测试（主持式）

工具：Zoom、Google Meet、UserTesting.com

Pros:
  - Can test with users anywhere
  - Lower cost (no travel)
  - Easier to recruit
  - Record sessions easily

Cons:
  - Can't see body language as well
  - Technical issues possible
  - Harder to build rapport
  - Screen sharing can lag

Best Practices:
  - Test your setup beforehand
  - Have backup communication method
  - Ask user to share screen + turn on camera
  - Record session (with permission)

现场测试

Pros:
  - See full body language
  - Better rapport
  - No technical issues
  - Can see facial expressions

Cons:
  - Limited geographic reach
  - Higher cost
  - Harder to schedule
  - Need physical space

Best Practices:
  - Set up quiet room
  - Have snacks/water
  - Use screen recording software
  - Position yourself behind/beside user

测试频率

When to Test:
  - Pre-launch: Test prototypes/designs
  - Post-launch: Test new features
  - Ongoing: Test every major release
  - Quarterly: Full usability audit

Continuous Testing:
  - Week 1: Test with 5 users
  - Week 2: Fix issues
  - Week 3: Test with 5 new users
  - Repeat until success rate ≥80%

工具和软件

Remote Testing:
  - UserTesting.com (recruit + test)
  - UserZoom (enterprise solution)
  - Lookback (live testing)
  - Maze (unmoderated testing)

Recording:
  - Zoom (screen + audio)
  - Loom (quick recordings)
  - OBS (advanced recording)

Analysis:
  - Dovetail (organize insights)
  - Notion (collaborative notes)
  - Miro (affinity mapping)
  - Excel/Sheets (metrics tracking)

快速入门清单

规划阶段

• 定义测试目标
• 编写 3-5 个任务场景
• 招募 5-8 位参与者
• 准备测试脚本
• 设置录制

测试阶段

• 欢迎参与者
• 说明出声思考协议
• 开展任务（不要提供帮助！）
• 提出后续问题
• 请参与者填写 SUS 调查问卷
• 感谢参与者

分析阶段

• 计算成功率
• 找出常见问题
• 评定问题严重程度
• 编写报告
• 与团队分享
• 排定修复优先级

常见陷阱

❌ 让员工参与测试：他们太熟悉产品了
❌ 在任务过程中帮助用户：让他们自己尝试，才能发现真正的问题
❌ 只测试顺利完成的路径：也要测试错误情况和边缘情况
❌ 参与者人数不足：每种用户画像至少 5 人
❌ 忽视低严重程度的问题：这些问题累积起来会导致糟糕的体验
❌ 测试了却不修复：如果不采取行动，可用性测试就毫无价值

总结

出色的可用性测试：

• ✅ 每种用户画像测试 5-8 位用户
• ✅ 使用真实的任务场景（而非逐步说明）
• ✅ 采用出声思考协议（了解心智模型）
• ✅ 任务过程中不要帮助用户
• ✅ 跟踪成功率、用时、错误和满意度
• ✅ 根据严重程度（影响程度 × 发生频率）评定问题
• ✅ 发布前修复高优先级问题
• ✅ 持续测试，而非只测一次