您如何处理不读对话框的用户？ [英] How would you handle users who don't read dialog boxes?

问题描述

最近有关 Ars Technica 讨论了北卡罗莱纳州立大学心理学系最近进行的一项研究，表明用户倾向于采取一切措施摆脱对话框，以回到手头的任务。大多数人会单击确定或是，最小化对话框，或关闭对话框，而不管显示的消息如何。显示的一些对话框是真实的，其中一些是假的（像网页显示的弹出窗口构成防病毒警告）。响应时间将表明这些用户并没有真正读取这些对话框。

所以，知道这一点，这将如何影响你的设计，你会尝试做什么（如果有的话）？

解决方案

我试图将应用程序设计为在事故面前坚固 - 无论是滑倒（无意中的操作，如点击错误的地方）还是错误（认知错误，例如在对话框上单击确定或取消）。一些方法是：

1. 无限（或至少多步）撤消/重做


2. 将文档与界面集成，通过动态工具提示和其他上下文相关的沟通手段（一篇特别相关的论文是关于惊喜，解释，奖励（直接链接： SER ） - 使用对意想不到的行为的典型心理反应来通知用户）


3. 将系统的状态纳入所述文档（使用当前用户的数据作为示例，并通过使用他们现在可以看到的数据使文档具体化）


4. Expect 用户错误。如果有人有机会尝试写入：\当没有磁盘到位时，则实施超时，以便系统正常失败，并提示另一个位置。将数据保存在内存中，直到其在磁盘上安全等。

这归结为两个核心内容：（1）防御程序，和（2）尽可能地告知用户。如果系统的界面易于使用，并根据自己的期望行事，那么当出现烦人的对话框时，他们更有可能知道按钮点击。

$ b $我也非常努力地避免任何模态，所以用户可以忽略大多数我必须使用的对话框，至少有一段时间（当他们真的需要注意它们时） ，他们有足够的信息来知道该怎么做）。

这是不可能让系统完全傻瓜，但我发现上述技巧在正确的方向走很长的路。 （并且它们已被纳入用于开发惊喜解释奖励的系统和其他通过广泛的用户研究审查的工具。）

A recent article on Ars Technica discusses a recent study performed by the Psychology Department of North Carolina State University, that showed users have a tendency to do whatever it takes to get rid of a dialog box to get back to their task at hand. Most of them would click OK or yes, minimize the dialog, or close the dialog, regardless of the message being displayed. Some of the dialog boxes displayed were real, and some of them were fake (like those popups displayed by webpages posing as an antivirus warning). The response times would indicate that those users aren't really reading those dialog boxes.

So, knowing this, how would this effect your design, and what would you try to do about it (if anything)?

解决方案

I try to design applications to be robust in the face of accidents -- either slips (inadvertent operations, such as clicking in the wrong place) or mistakes (cognitive errors, such as clicking Ok vs. Cancel on a dialog). Some ways to do this are:

1. infinite (or at least multi-step) undo / redo
2. integrate documentation with the interface, via dynamic tooltips and other context-sensitive means of communication (One paper that is particularly relevant is about 'Surprise, Explain, Reward' (direct link: SER) -- using typical psychological responses to unexpected behavior to inform users)
3. Incorporate the state of the system into said documentation (use the current user's data as examples, and make the documentation concrete by using data that they can see right now)
4. Expect user error. If there's a chance that someone will try to write to a:\ when there isn't a disk in place, then implement a time-out so the system can fail gracefully, and prompt for another location. Save the data in memory until it's secure on disk, etc.

This boils down to two core things: (1) Program defensively, and (2) Keep the user as well informed as you can. If the system's interface is easy to use, and behaves according to their expectations then they are more likely to know which button to click when an annoying dialog appears.

I also try very, very hard to avoid anything modal, so users can ignore most dialogs I have to use, at least for a while (and when they really need to pay attention to them, they have enough information to know what to do with it).

It's impossible to make a system completely fool-proof, but I've found that the above techniques go a long way in the right direction. (and they have been incorporated in the systems used to develop Surprise Explain Reward and other tools that have been vetted by extensive user studies.)

这篇关于您如何处理不读对话框的用户？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！