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

问题描述

最近一篇关于 Ars Technica 讨论了北卡罗来纳州立大学心理学系最近进行的一项研究，该研究表明用户倾向于不惜一切代价摆脱对话框以返回手头的任务.他们中的大多数会单击确定"或是"，最小化对话框或关闭对话框，而不管显示的消息如何.显示的对话框有些是真实的，有些是假的(例如那些冒充防病毒警告的网页显示的弹出窗口).响应时间表明这些用户并没有真正阅读这些对话框.

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. 无限(或至少多步)撤消/重做
2. 通过动态工具提示和其他上下文相关的通信方式将文档与界面集成(一篇特别相关的论文是关于 '惊喜，解释，奖励'(直接链接:SER) -- 使用对意外行为的典型心理反应来告知用户)
3. 将系统状态整合到所述文档中(以当前用户的数据为例，并使用他们现在可以看到的数据使文档具体化)
4. 预计用户错误.如果有人在没有磁盘的情况下尝试写入 a:，则执行超时，以便系统可以正常失败，并提示另一个位置.将数据保存在内存中，直到它在磁盘等上安全为止.

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.

这归结为两个核心内容:(1) 防御性编程，以及 (2) 尽可能让用户了解情况.如果系统的界面易于使用，并且行为符合他们的期望，那么他们更有可能知道在出现烦人的对话框时应该点击哪个按钮.

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).

要让系统完全万无一失是不可能的，但我发现上述技术在正确的方向上大有帮助.(并且它们已被纳入用于开发 Surprise Explain Reward 和其他已通过广泛用户研究审查的工具的系统中.)

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屋！