[转]一.设计过程 1-在设计过程中引入用户交互_go through the steps and then design a for yoursel-CSDN博客

设计过程
The Design Process

This chapter offers some basic tips on how to make the best design choices for your software. Great software design involves a careful analysis of the needs of your users; after all, they are the ones who will use your product. Identifying their needs and finding ways to meet those needs are important first steps in the design process.

本章将介绍在软件设计时怎样做出合适选择的一些基本技巧。良好的软件设计通常包括对目标用户需求的细致分析；毕竟，是他们使用您的产品。了解并满足用户的需求是软件设计过程中很重要的第一步。

在设计过程中引入用户交互
Involving Users in the Design Process

When you give people an opportunity to use your product (or a prototype of it) you may uncover usability problems that you did not anticipate during your initial design phase. Finding and eliminating these problems early can save you time and money later on. Clearly identifying the needs of your users helps you create products that deliver effective solutions and are typically easier for them to learn and use. These improvements can translate into competitive advantages, increased sales, and enhanced customer satisfaction.

当您让用户有机会使用您的产品（甚至只是原型）时，您可以发现很多在初始设计的时候没有发现的使用性的问题。在早期发现和排除这些问题可以在后期节省您的时间和金钱。清楚地了解您的用户的需求也能让您的产品更为针对性，用户更容易学习和使用。这些改进能够带来竞争优势，市场份额以及用户满意度的上升。

了解您的目标客户
Know Your Audience

Identifying and understanding your target audience are important first steps when designing your product. Equally important is the analysis of similar products in related markets to see what audiences they target and whether those products would be competitors or would interleave nicely with yours. Understanding the approach taken by other product designers might give you insight into the needs of your own target users.

确认和了解您的目标客户是产品设计重要的第一步。同样重要的还有分析市场上类似产品，分析它们的目标客户群，分析它们是竞争对手还是协作伙伴。了解其他产品的设计人员采取的方法有助于您洞悉您的目标客户的需求。

It is useful to create scenarios that describe a typical day of a person who uses the type of software product you are designing. Think about the different environments, tools, and constraints that this person deals with. If possible, visit actual workplaces and study how people perform those tasks you intend your product to help them perform.

想象一个用户使用您设计的软件产品的一天，这种场景的构建是非常有用的。您需要考虑不同的环境，用户使用的工具，以及需要处理的限制。如果可能的话，参观实际的工作场所并了解用户是怎样完成那些您的产品试图帮助他们完成的任务的。

Throughout the design process, find people who fit your target audience to test your prototypes. Listen to their feedback and try to address their concerns. Develop your product with people and their capabilities—not computers and their capabilities—in mind.

寻找合适的目标客户来测试您的原型，这一活动应该贯穿整个设计过程。听取他们的反馈并试着解决他们提出的问题。在开发时更多的从人的角度出发而不是计算机。

Recognize that, as an application developer or interface designer, you have a greater wealth of knowledge and a more intricate understanding of your application than your customers are likely to have. Although you should use that knowledge to choose the best default settings or decide the best presentation of information, remember that you are not designing the program for yourself. It is not your needs or your usage patterns that you are designing for, but those of your (potential) customers.

您必须认识到，作为一个应用程序开发者或者用户接口设计人员，您对您的应用程序的了解远大于您的客户。尽管您可以利用这些理解来决定产品的默认配置或者信息的表达方式，然而，您也要记住，您不是在为您自己设计程序，您不是在为您的需求或者您的使用习惯而设计，而是您的潜在客户。

分析用户的工作流
Analyze User Tasks

When you have defined your audience, you need to define and analyze the tasks that your users might perform. Discover the mental or conceptual model people associate with the task your product will help them perform. A mental model paints a picture of a task and defines expectations about the components of the task, the organization of those components, and the overall workflow.

确定了您的用户群后，您需要定义和分析用户的工作流，并抽象出这些工作流的心智模型。心智模型定义整个工作流，工作流的组件，以及这些组件组织结构的预期。

To help you discover the mental models people associate with your product’s tasks, look at how they perform similar tasks without a computer. What terminology do they use? What concepts, objects, and gestures do your users associate with this task? Design your product to reflect these things, but don’t insist on replicating each step a user might take when performing the task without a computer. Take advantage of the inherent strengths of the computing environment to make the whole process easier or more streamlined. For more information on how the user’s mental models should inform your design, see “Reflect the User’s Mental Model.”

分析用户在没有计算机的情况下的工作流有助于发现和您的产品相关的用户的心智模型。例如，他们使用什么术语？用户在这个工作流都使用了那些相关的概念、对象以及手势？在您的产品设计中都可以对这些因素有所反应，但是不用严格的按照用户的工作流一步步来。您可以利用计算机强大的计算功能使得整个过程更加容易和效率更高。关于用户的心智模型怎样影响您的设计的更多信息，请参考“反映用户的心智模型”。

构造原型系统
Build Prototypes

Use the information about tasks and their component steps to create an initial design, and then create a prototype of your design. Prototyping is a good way to test aspects of your design and verify how well they will work for your users. You can use a variety of techniques to construct prototypes, not all of which involve writing code. For example, you can create storyboards that visually show the appearance of your product as users go through the steps of a specific task. You can also use prototyping software to simulate some features of your product or demonstrate how it will operate.

您可以利用工作流及其相关步骤的信息来给出一个初步的设计，并构造一个基于该设计的原型。原型是验证设计方案是否按照预期工作的良好方式。有很多技术可以帮您创建原型，并且不是每一种都需要编写代码。例如，您可以在用户使用特定功能时只是显示您的产品的相应界面，而并不实际执行操作。您也可以使用软件原型来模拟或者示范您产品中的某些功能。

Note: Keep in mind that prototyping should be done quickly and only for the purpose of improving your design. If you write code for your prototype, avoidusing that same code in your final product.

注意：原型必须快速完成，并且仅仅是为了改进您的设计。如果您需要为原型编写代码，那么尽量避免使用在您的最终产品中使用同样的代码。

观察用户
Observe Users

Once you have a prototype, let some target users try it out and observe their reactions to it. Watch and listen carefully to these users, and try to videotape their reactions as they work through specific tasks you’ve defined for your prototype. User observations can help you determine how well your design works or where there are problems. If product designers and engineers are available, encourage them to watch the tests, but prevent them from interacting with the users so that they do not influence the test results.

一旦您有了一个原型，您就可以让一些目标用户试用该原型并观察他们的反应。仔细的观察和倾听这些用户，并且当这些用户工作在您的原型中定义的工作流时尝试记录下他们的反应。观察用户能够帮助您了解您的设计是否满足要求，或者问题出在哪里。如果可能的话，让设计人员和工程师也能够观察测试，但是不要让他们和用户交流，以免影响测试的结果。

During user testing, be sure to limit the scope of your tests to key areas of your product. Focus on the tasks you identified during your task analysis. Your instructions to the participants should be clear and complete but should not explain how to do things you’re trying to test.

您必须确保测试的是您的产品的核心功能，并集中于您在工作流分析中标记的步骤。您给参与测试的用户的说明必须清晰，完整，但不应解释测试的具体方法和步骤。

Use the information recorded from your user tests to analyze your design and use that information to revise your prototype. When you have a second prototype, conduct a second set of user observations to test the workability of your design changes. You can repeat this process as often as you like until you feel confident that you’ve addressed the needs of your target audience and created a highly usable product that displays the characteristics of great software (see “Characteristics of Great Software”).

利用测试的记录对您的设计方案进行分析并修正您的原型。当您出了第二个原型时，重新更换用户来测试新设计方案的可行性。您可以一直重复这个过程直到您对您的产品能否满足目标客户的需求以及产品的可用性充满了自信。

观察用户的一些准则
Guidelines for Conducting User Observations

There are many ways to get feedback from users during the design process. These include usability testing, cognitive walkthroughs, group walkthroughs, on-site observations, and heuristic walkthroughs. You can use the following guidelines when conducting user observations, but note that they can apply more generally to other types of testing as well. Remember that testing is not an experiment; you will not get quantitative data that can be statistically analyzed. You can, however, see where people have difficulty using your product, and then use that information to improve your product.

在设计过程中您可以通过多种方式来得到用户的反馈，包括可用性测试，认知走查，群组走查，实地观察以及探索式走查等。您可以根据如下的指导方法来进行用户观察，但要注意到各种类型的测试之间是不能通用的。记住，测试并不是实验，您并不能从中得到可用于静态分析的大量数据。然而，您可以知道用户在使用您的产品时哪儿碰到了困难，并且可以据此改进您的产品。

If time and budget permit, consider working with a professional usability testing facility to conduct this type of testing. If this is not feasible, try to allow a cross-section of colleagues within your company to use a prototype of your product and gather their feedback. This alone will improve the usability of your product because some testing is far better than no testing.

如果时间和预算允许的话，您可以考虑使用一些专业的可用性测试方法来进行这种类型的测试。如果不可行的话，那么尝试让同一公司别的部门的同事来使用您产品的原型并收集他们的反馈。这样也能聊胜于无的提高您产品的可用性。

If you choose to conduct your own user observation-based testing, following these guidelines will help you get the most valuable data:

如果您选择自己来进行基于用户观察的测试，那么遵守下面这些准则将使您的测试数据更有价值：

Introduce yourself and describe the purpose of the observation (in very general terms). Most of the time, you shouldn’t mention what you’ll be observing. Make it clear to the participant that you are testing your product, not the participant.

介绍你自己并简单描述一下这次测试的目的（不要透漏具体细节）。大部分情况下，您不应该指明您需要观察什么。要让测试的参与者明白是您在测试您的产品，而不是这些他们。

Tell the participant about how long the test will take and that it’s OK to quit at any time, for any reason. The user should never feel pressured to complete a test. Besides, quitting may indicate that the underlying task is too difficult or complex and should be simplified.

告诉参与者测试会持续多久，并且他们可以随时以任何理由退出测试。这样用户就不会有必须完成测试的压力。另外，退出可能意味着现在设计的工作流太困难，太复杂，需要简化。

A common testing methodology is to use the think-aloud protocol. If you are using this protocol, explain how to do it. Ask participants to think aloud during the observation, saying what comes to mind as they work. By listening to participants think and plan, you’ll be able to examine their expectations for your product as well as their intentions and their problem-solving strategies.

一个通常使用的方法是自言自语条约。当您在使用该条约时，您需要向您的用户解释怎样去做。让您的用户在被观察时自言自语，说出他们使用您的产品时心里所想的。通过倾听这些参与者的想法，您可以知道他们对您的产品的期望，他们的意图，以及他们解决问题的策略。

You may find that listening to users as they work will provide you with an enormous amount of useful information. In particular, you’ll discover some of the details of the mental model the user has of the task. You can help users practice thinking aloud by having them describe a simple task, like how they prepare a cup of coffee.

您会发现这种方法会得到很多有用的信息。特别的是，您将发现用户的心智模型的一些细节。您可以让用户简单描述一下他们的工作流，就像他们怎样冲杯咖啡一样，这样可以帮助他们练习自言自语。

Describe in general terms what the participant will be doing. Explain what all the materials are and the sequence in which the participant will use them. If you are using a lab, explain the purpose of each piece of equipment in the room (hardware, software, recording devices, and so forth) and how it will be used in the test. If you need to demonstrate your product before the user observation begins, be sure you don’t demonstrate something you’re trying to test.

概括的描述一下参与者将要做些什么。解释所有会用到的材料以及使用它们的顺序。如果您是在一个实验室里面，解释一下实验室里面设备的用途（硬件，软件，记录设备等等）以及他们在测试用的使用顺序。如果您需要在用户观察开始之前示范一下您产品的使用，切记不要示范那些您需要测试的部分。

It is very important that you allow participants to work with your product without any interference or extra help from the facilitator, the analyzer, or anyone else. This is the best way to see how people really interact with the product. For example, if you see a participant begin to have difficulty and you immediately provide an answer, you will lose the most valuable information you can gain from user observation: determining where users have trouble and how they figure out what to do.

确保参与者是独立的使用您的产品，而不是通过服务商，分析员或者其他人员的帮助，这一点很重要。这是知道用户使用您产品的真实情况的最好方式。例如，如果您看到某个参与者有了困难而立即提供答案，您就失去了您从观察用户测试中能够得到的最有价值的信息：用户在哪儿遇到了麻烦而且他们是怎么解决的。

Note: There may be situations in which you will have to step in and provide assistance, but you should decide what those situations will be before you begin testing. For example, you may decide that you will allow someone to struggle for at least 3 minutes before you provide assistance or that there is a distinct set of problems on which you will provide help. However, if a participant becomes very frustrated, it’s better to intervene than have the participant give up completely.

注意：可能有些情况您必须介入提供帮助，但您必须在测试开始前就决定什么样的情况需要介入。例如，您可以决定如果用户超过三分钟还不能解决问题你就可以提供帮助，或者您事先决定一组您可以提供帮助的的问题集合。因为，如果用户在测试过程中变得非常沮丧，那么介入并提供帮助总比完全放弃要好一些。

Conclude by explaining what you were trying to find out and answer any questions the participant may have.

在结束时说明您在测试什么并回答参与者的任何问题。

Use the results. As you observe, you will see users doing things you may never have expected them to do. When you see participants making mistakes, your first instinct may be to blame their inexperience or lack of intelligence. This is the wrong response to have. Remember that the purpose of observing users is to learn what parts of your product might be difficult to use or ineffective because of faulty product design.

分析测试结果。如您所看到的，用户可能采用您决不希望他们采用的方式来使用您的产品。当您看见用户犯下这些错误时，可能您的第一反应就是认为他们缺少经验或者不是足够的聪明。然而，这种想法是错误的。切记观察用户的目的是了解您的产品中哪一部分由于失败的设计而难于使用。

Watch for patterns. Just because one user has a problem with something, that doesn’t mean every user will. Carefully consider why the single user had the problem and consider discarding that finding if it can be easily explained, otherwise, recognize that the software may be faulty.

当心泛化。因为一个用户出了问题不代表每个用户都会有问题。仔细思考为什么这个用户会碰到问题，如果很好解释的话，就忽略这个问题，否则，重新考虑软件产品的缺陷。

Review all results with a cross-functional team comprising representatives of product management, marketing, engineering, human interface design, documentation, and quality assurance. Each of these participants will view the results through the lens of their own expertise, enabling them to provide valuable insights into various usability issues with which the users might have struggled.

和其他功能小组一块复查结果，如产品管理小组，市场管理小组，工程师，人机接口设计小组，文档小组以及质量保证小组。这些小组将会从他们自身的角度来查看测试的结果，从而在可能困扰用户的使用性问题上提供更有价值的见解。

取自“http://www.uxguide.net/wiki/macos:Involving-users-in-the-design-process”