Getting user feedback with UI prototypes is essential to creating a user interface that your user community will understand and be productive with. The best way to do this IMO is with paper prototyping. Your use cases can drive the initial creation of these prototypes, and the user interaction sessions with your clients can refine the UI design.
If you prefer electronic prototypes, you can use something like PowerPoint to rapidly prototype them.
First gather information about the users' workflow and goals. This is best done by physically going to see how the users are doing their work today (for example using contextual inquiry). Document those goals as goal-based use cases (see the link below), which contain only the goal - they should not contain any details of how the system will be used, because those details are what we are just starting to design based on the use cases.
Based on the use cases, create a quick paper prototype of the UI, and try step-by-step that how the users would reach their goals using the prototyped system. If the use cases can not be executed well enough with the UI prototype, keep on improving it until all use cases are supported. Show the prototype to the users and use usability testing and other techniques to find out problems with the UI.
When the UI design is good enough (~85% ready - some fine details are best tweaked after implementation), you can document it for example by taking picture sequences of the prototype, which show how the use cases can be executed with the system. But communicating the UI design to the programmers is best done face-to-face, by showing manually how the prototype works and answering their questions. Don't just "throw the documentation over a wall", but follow through to see how it is implemented and test whether the implementation matches what was designed.
发布评论
评论（2）
通过 UI 原型获取用户反馈对于创建用户社区能够理解并高效使用的用户界面至关重要。在我看来，实现此目的的最佳方法是使用纸质原型。您的用例可以推动这些原型的初始创建，并且与客户的用户交互会话可以完善 UI 设计。
如果您更喜欢电子原型，可以使用 PowerPoint 快速原型化它们。
另请参阅 http://www.codinghorror.com/ blog/2008/04/ui-first-software-development.html 和 http://www.codinghorror.com/blog/2007/01/low-fi-usability-testing.html
Getting user feedback with UI prototypes is essential to creating a user interface that your user community will understand and be productive with. The best way to do this IMO is with paper prototyping. Your use cases can drive the initial creation of these prototypes, and the user interaction sessions with your clients can refine the UI design.
If you prefer electronic prototypes, you can use something like PowerPoint to rapidly prototype them.
See also http://www.codinghorror.com/blog/2008/04/ui-first-software-development.html and http://www.codinghorror.com/blog/2007/01/low-fi-usability-testing.html
首先收集有关用户工作流程和目标的信息。最好通过亲自查看用户今天的工作情况来完成（例如使用上下文查询< /a>）。将这些目标记录为基于目标的用例（请参阅下面的链接），其中仅包含目标 - 它们不应包含有关如何使用系统的任何细节，因为这些细节是我们刚刚开始基于用例。
根据用例，创建 UI 的快速纸质原型，并逐步尝试用户如何使用原型系统实现其目标。如果 UI 原型无法很好地执行用例，请继续改进它，直到支持所有用例。向用户展示原型并使用可用性测试和其他技术来找出 UI 的问题。
当 UI 设计足够好时（约 85% 准备就绪 - 一些细节最好在实现后进行调整），您可以通过拍摄原型的图片序列来记录它，这些图片显示了如何使用系统执行用例。但是，与程序员交流 UI 设计最好是面对面进行，通过手动展示原型如何工作并回答他们的问题。不要只是“把文档扔到墙上”，而是要跟进看看它是如何实现的，并测试实现是否与设计相匹配。
请参阅 http://www.cs.helsinki 上的较长流程说明。 fi/u/salaakso/papers/GUIDe.pdf
First gather information about the users' workflow and goals. This is best done by physically going to see how the users are doing their work today (for example using contextual inquiry). Document those goals as goal-based use cases (see the link below), which contain only the goal - they should not contain any details of how the system will be used, because those details are what we are just starting to design based on the use cases.
Based on the use cases, create a quick paper prototype of the UI, and try step-by-step that how the users would reach their goals using the prototyped system. If the use cases can not be executed well enough with the UI prototype, keep on improving it until all use cases are supported. Show the prototype to the users and use usability testing and other techniques to find out problems with the UI.
When the UI design is good enough (~85% ready - some fine details are best tweaked after implementation), you can document it for example by taking picture sequences of the prototype, which show how the use cases can be executed with the system. But communicating the UI design to the programmers is best done face-to-face, by showing manually how the prototype works and answering their questions. Don't just "throw the documentation over a wall", but follow through to see how it is implemented and test whether the implementation matches what was designed.
See the longer process description at http://www.cs.helsinki.fi/u/salaakso/papers/GUIDe.pdf