usability-testing

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Usability Testing

可用性测试

Help the user conduct effective usability testing using frameworks and insights from 11 product leaders.

借助11位产品负责人的框架和见解，帮助用户开展有效的可用性测试。

How to Help

如何提供帮助

When the user asks for help with usability testing:

Clarify the goal - Determine if they're validating a concept, finding friction points, or optimizing conversion
Choose the right fidelity - Help them select between Wizard of Oz tests, fake doors, prototypes, or production testing
Design the test - Guide them on recruiting users, creating scenarios, and what to observe
Plan for iteration - Discuss how findings will flow back into the product development process

当用户请求可用性测试相关帮助时：

明确目标 - 确定他们是要验证概念、找出体验摩擦点，还是优化转化效果
选择合适的保真度 - 帮助他们在Wizard of Oz测试、假门测试（fake doors）、原型测试或生产环境测试中做出选择
设计测试方案 - 指导他们完成用户招募、场景创建以及观察要点的确定
规划迭代流程 - 讨论如何将测试结果反馈到产品开发流程中

Core Principles

核心原则

Fake it before you build it

先模拟再构建

Itamar Gilad: "Initially you fake it - fake door test, smoke test, Wizard of Oz tests. We showed the tabbed inbox working to people, but it wasn't really Gmail, it was just a facade." Validate core value propositions before writing production code using faked versions where humans perform the automated task behind the scenes.

Itamar Gilad：“最初我们会进行模拟——假门测试、冒烟测试、Wizard of Oz测试。我们向人们展示了标签式收件箱的功能，但那其实不是真正的Gmail，只是一个外壳。”在编写生产代码前，先通过人工后台执行自动化任务的模拟版本验证核心价值主张。

Small samples reveal big friction

小样本也能发现关键问题

Melanie Perkins: "It's amazing how you can find 10 random people on the internet and they can give such astute feedback that's so representative for such a large number of people." Run tests with as few as 10 random people to identify core product issues.

Melanie Perkins：“仅在网上找10个随机用户，就能得到极具洞察力且能代表大量用户的反馈，这太令人惊讶了。”只需测试10个左右的随机用户，就能发现产品的核心问题。

Watch users, don't just ask them

观察用户，而非仅询问

Uri Levine: "Simply watch users and see what they're doing. If they're not doing what you expect, then ask them why." Direct observation reveals behaviors and needs that surveys miss. Ask 'why' when users deviate from the expected path.

Uri Levine：“只需观察用户的操作即可。如果他们的行为与预期不符，再询问原因。”直接观察能揭示调查无法发现的行为和需求。当用户偏离预期路径时，询问其原因。

Test multiple options, not one

测试多个选项，而非单一选项

Kristen Berman: "We never do a UX study where we're just showing people one thing. We always present multiple options and relatively look for which one drives the intended behavior." Single-design testing is ineffective for predicting behavior.

Kristen Berman：“我们开展的UX研究绝不会只展示一个方案。我们总会呈现多个选项，对比哪个更能引导预期行为。”单一设计测试无法有效预测用户行为。

Overcome creator bias

克服创作者偏见

Guillermo Rauch: "You tend to overrate how well your products work. It's very important to give your product to another person and watch them interact with it." Directly observing users helps overcome the tendency to think your product is more intuitive than it is.

Guillermo Rauch：“你往往会高估自己产品的易用性。将产品交给他人并观察其交互过程，这一点非常重要。”直接观察用户能帮助你打破“自己的产品更直观”的认知偏差。

Micro-level testing drives millions

微级测试带来巨大收益

Judd Antin: "We changed seven characters and made Airbnb millions of dollars because we found out the button felt scary." Don't dismiss usability testing as junior work; finding scary or confusing CTAs can massively impact conversion.

Judd Antin：“我们修改了7个字符，为Airbnb带来了数百万美元的收益，因为我们发现那个按钮让用户感到不安。”不要将可用性测试视为初级工作；找出令人不安或困惑的CTA（号召性用语）能极大地影响转化效果。

Progress through testing stages

分阶段推进测试

Itamar Gilad: "Mid-level tests are about building a rough version - early adopter programs, alphas, longitudinal user studies, and fish food (testing on your own team)." Use a progression from fish fooding to dogfooding to alphas to increase confidence iteratively.

Itamar Gilad：“中期测试是构建粗略版本——早期采用者计划、alpha测试、纵向用户研究以及内部团队测试（fish food）。”遵循从内部团队测试（fish fooding）到全员测试（dogfooding）再到alpha测试的流程，逐步提升信心。

Make testing a team sport

让测试成为团队协作项目

Noah Weiss: "We had PMs, engineers, designers, and the user researcher all in one Slack thread live, responding and reacting to the usability session." Increase engagement by having cross-functional teams live-react to sessions in shared chat threads.

Noah Weiss：“我们让产品经理、工程师、设计师和用户研究员都加入同一个Slack线程，实时对可用性测试会话做出响应和反馈。”通过让跨职能团队在共享聊天线程中实时参与会话，提升团队参与度。

Questions to Help Users

用于引导用户的问题

"What specific behavior are you trying to observe or validate?"
"Do you need to validate the concept (use fake doors) or optimize the execution (use the real product)?"
"How will you recruit users who have 'zero skin in the game' for honest feedback?"
"Are you testing one option or multiple options to compare?"
"What will you do with the findings - how will they flow back into development?"
"Who else on the team should observe these sessions?"

“你想要观察或验证的具体行为是什么？”
“你需要验证概念（使用假门测试）还是优化执行效果（使用真实产品）？”
你将如何招募“与产品无利益关联”的用户以获取诚实反馈？”
“你是在测试单一选项还是多个可对比的选项？”
“你将如何处理测试结果——如何将其反馈到开发流程中？”
“团队中还有哪些人应该参与观察这些测试会话？”

Common Mistakes to Flag

需要指出的常见错误

Testing only one design - Present multiple options to measure relative performance
Building before validating - Use Wizard of Oz or fake door tests before writing production code
Relying on internal intuition - Employees are too familiar with the product to spot real user friction
Ignoring micro-level issues - Small copy changes and button labels can have massive business impact
Testing in isolation - Bring engineers and designers into sessions to build shared understanding

仅测试单一设计 - 应呈现多个选项以衡量相对表现
先构建后验证 - 在编写生产代码前，先使用Wizard of Oz或假门测试
依赖内部直觉 - 员工对产品过于熟悉，无法发现真实的用户体验摩擦
忽视微级问题 - 文案微调、按钮标签等小细节可能对业务产生巨大影响
孤立开展测试 - 让工程师和设计师参与测试会话，建立统一的认知

Deep Dive

深入研究

For all 14 insights from 11 guests, see

references/guest-insights.md

如需查看来自11位嘉宾的全部14条见解，请参阅

references/guest-insights.md