The scenario sounds a bit worrying to me. You have a UX team, yet they aren't that hot on UX. And you've got one hour to deliver stuff like an intro to human factors?
Find out where each of their weaknesses are send them on training courses. One hour is going to achieve very little.
Given your audience already has some background in UX, I’d use the time to present one to three case studies and lessons learned from your personal work experience. Describe a design or user performance problem, how you dealt with it, and what the outcome was. Select cases without easy answers, such as one where compliance with standards conflicts with usability test results, or where a general human factors design principle conflicts with theoretical or formal analysis (e.g., GOMS).
For each case, try to engage the audience to discuss the problem and how it can be resolved. Get them to identify the pros and cons of each solution, and see if they can come up with one that addresses all issues, for example how the design can comply with standards yet still achieve high performance in testing. It’s okay to present a case where you’re not confident in the actual implemented solution. The point is the get your audience thinking about usability and design.
By working with concrete examples, you provide the audience a chance to exercise the high level stuff it already knows. This approach will cover the basics but keep you from boring individuals that already know them at a theoretical level. If the case studies serve as good illustrations of areas you think the team can improve, so much the better. If it allows you to present a new principle or process beyond the basics, that’s good too.
In other words, treat your audience more as peers, like an academic presenting a paper at a conference, rather than like a professor lecturing to undergraduates.
I'd be sure to include examples of what you're talking about as it applies to your primary product(s). High-level for part of it is fine, but examples make it real.
Also show how human factors can aid in readhing the UE teams goals faster (X% customer satisfaction, faster time to market, etc.) Whet their appetite by giving them solutions to their challenges.
If this is for you UX team, I would think they have at least the 10000 foot overview already. If this is going to be a series of lunch-and-learn talks, then do the basics first and dive into specifics in subsequent talks.
If this is stand alone, I would hit the highlights fast (5 - 10 minutes) and then choose a specific topic.
发布评论
评论（6）
这个场景听起来有点令人担忧。你有一个用户体验团队，但他们对用户体验并不那么热衷。您有一个小时的时间来提供诸如人为因素介绍之类的内容吗？
找出他们的弱点，然后送他们去参加培训课程。一小时的收获微乎其微。
The scenario sounds a bit worrying to me. You have a UX team, yet they aren't that hot on UX. And you've got one hour to deliver stuff like an intro to human factors?
Find out where each of their weaknesses are send them on training courses. One hour is going to achieve very little.
鉴于您的听众已经具有一些用户体验背景，我将利用这段时间介绍一到三个案例研究以及从您的个人工作经验中吸取的教训。描述设计或用户性能问题、您如何处理它以及结果是什么。选择没有简单答案的案例，例如符合标准与可用性测试结果相冲突的案例，或者一般人为因素设计原则与理论或形式分析（例如，GOMS）相冲突的案例。
对于每个案例，尝试让观众参与讨论问题以及如何解决问题。让他们确定每种解决方案的优缺点，看看他们是否能提出一种解决所有问题的解决方案，例如设计如何符合标准，同时在测试中仍能实现高性能。如果您对实际实施的解决方案没有信心，可以提出一个案例。重点是让观众思考可用性和设计。
通过使用具体的例子，你可以为观众提供一个练习他们已经知道的高水平内容的机会。这种方法将涵盖基础知识，但不会让那些已经在理论层面上了解这些知识的人感到厌烦。如果案例研究能够很好地说明您认为团队可以改进的领域，那就更好了。如果它允许您提出超越基础的新原则或流程，那也很好。
换句话说，更多地对待你的听众，就像在会议上发表论文的学者一样，而不是像教授给本科生讲课一样。
Given your audience already has some background in UX, I’d use the time to present one to three case studies and lessons learned from your personal work experience. Describe a design or user performance problem, how you dealt with it, and what the outcome was. Select cases without easy answers, such as one where compliance with standards conflicts with usability test results, or where a general human factors design principle conflicts with theoretical or formal analysis (e.g., GOMS).
For each case, try to engage the audience to discuss the problem and how it can be resolved. Get them to identify the pros and cons of each solution, and see if they can come up with one that addresses all issues, for example how the design can comply with standards yet still achieve high performance in testing. It’s okay to present a case where you’re not confident in the actual implemented solution. The point is the get your audience thinking about usability and design.
By working with concrete examples, you provide the audience a chance to exercise the high level stuff it already knows. This approach will cover the basics but keep you from boring individuals that already know them at a theoretical level. If the case studies serve as good illustrations of areas you think the team can improve, so much the better. If it allows you to present a new principle or process beyond the basics, that’s good too.
In other words, treat your audience more as peers, like an academic presenting a paper at a conference, rather than like a professor lecturing to undergraduates.
我一定会提供您所讨论的示例，因为它适用于您的主要产品。部分内容的高级程度很好，但例子使它更真实。
还展示人为因素如何帮助更快地理解 UE 团队的目标（X% 的客户满意度、更快的上市时间等），通过为他们提供应对挑战的解决方案来激发他们的兴趣。
I'd be sure to include examples of what you're talking about as it applies to your primary product(s). High-level for part of it is fine, but examples make it real.
Also show how human factors can aid in readhing the UE teams goals faster (X% customer satisfaction, faster time to market, etc.) Whet their appetite by giving them solutions to their challenges.
我建议在
I'd suggest having a progressive customer viewpoint of the user experience in terms of
如果这是为您的 UX 团队准备的，我认为他们至少已经有了 10000 英尺的概览。如果这将是一系列午餐学习演讲，那么首先做基础知识，然后在随后的演讲中深入探讨细节。
如果这是独立的，我会快速（5 - 10 分钟）抓住重点，然后选择一个特定的主题。
If this is for you UX team, I would think they have at least the 10000 foot overview already. If this is going to be a series of lunch-and-learn talks, then do the basics first and dive into specifics in subsequent talks.
If this is stand alone, I would hit the highlights fast (5 - 10 minutes) and then choose a specific topic.
我认为很多该做和不该做的内容既有用又有趣。
I think a lots of DOs and Dont's is both usefull and fun to see.