--------------------------------------------- ------- To complex digital product planning, especially those that are directly interacting with others, require professional designers to pre-conduct special efforts, as as complex buildings to deal with people A professional architect is needed to take special efforts in advance. For architects, their planning includes understanding how people living and working in buildings, and designing space to support and facilitate these behaviors. For digital products, planning includes how to live and work on how people who use products, and design the appearance and behavior of products to support and facilitate human behavior. Architecture is an old, well defined area. Design for product and system behavior - interactive design - is a discipline that is quite new, only in recent years. Interaction design is not about aesthetic choice, but based on understanding and cognitive principles for customers. This is a good news because this makes the design of the behavior can become repeatable analysis and integrated processes. But this does not mean that the design of behavior can be automated, even if the appearance and content can be automated, it does not mean that the systematic reaching automatic design is feasible. Of course, there is no need to abandon the aesthetic rules for design appearance, but these rules must be adapted to the user goals. This book introduces a group of methods to meet the needs of newly-oriented design, which is dedicated to the user's goals (Rudolf, 1998), ie: target directive design. In order to understand the target guide design, we need to understand people's goals and how these goals provide an acknowledrance for appropriate design interactions.
-------------------------- understand the user's goal -------------------- ----- So what is the user's goal? How do we identify them? How do we know that they are real? Are all users' goals? Do they change over time? In this rest of this chapter, these issues will be answered. User goals often differ with our guess. For example, we may think that the objectives of the bookmaker are efficient processing invoices. This may not be true. Efficient processing invoices may be the goal of employers. The goal of the staff is more likely to show your ability in work, and make yourself keep your daily and repetitive things. Regardless of our work and completing the task, we always contain some simple, personal goals. Even if we have a high enthusiasm, these goals are still more personal than those: such as, winning promotion, learn more in our field, or make a good example for others. (What is my current goal?) The product that is designed and built only in order to achieve business goals; the user's personal goal needs to be taken. When satisfied by designing the user's personal goals, the business goal will be very effective, and the reasons will be explained in detail in the following sections. If you check most of today's commercial software, websites, and digital products, you will find their user interface to make the number of times the user's goal failure is shocking. They are used to: ■ Let users feel stupid ■ Let users make major mistakes ■ Missing users' speed makes them can't complete enough work ■ Prevent users from happiness or / and let users get boring in boring processes These software, most of them are also the same in the business intent. The invoice is not very good. The user did not get a timely service. The resolution did not get appropriate support (?). This is not accidental. The team developed these products did not distinguish it. That too much attention is limited to implementation of the details, but not paying attention to the needs of users. Even if these development teams become sensitive to their users, they still have no power to change their products because the traditional design process assumes that the user interface should be reached after the coding start - sometimes even at the end. However, as you can't effectively design the buildings that have begun to build, let the program that have begun encoding the program is not an easy task or something is especially true (for the end of the encoding. Finally, even if the development team does pay attention to the user, they also put too much attention to the tasks of the user, but the goals of these tasks do not care enough. Software with gorgeous technology is diligent to implement each business task, and may still fail in comments and business failures. We cannot ignore technical or tasks, but they just meet some of the huge plans to meet the needs of user needs.
Target VS tasks objectives and tasks are different. The goal is the ultimate requirement, and the task is to help the intermediate steps of the target. Target stimulate people to perform tasks. It is very important to mix mission and goals to talk to one, but they are really confused. Fortunately, there is an easy way to illustrate the difference between tasks and goals. The goal is driven by the motivation, even if it passes, it changes very slow. The task is temporary, based on the currently available technology. For example: from St. Louis to San Francisco, people's goals may be fast, comfortable and safe. In 1850, a pioneer may take a horse block car; and he may bring his own trust to the gun. Today, from St. Louis to San Francisco, a businessman rides a jet plane for a journey, and he is asked to leave the firearm in home for safety reasons. The goal has never changed, but the task has changed as the change has changed, and sometimes it is even completely opposite. You can clarify (?) Technology removal of undesired tasks through the target lens. It seems: If you go to work in the morning, your goal is to quickly and safely to your workplace. For today's technology, this means that the task is to take the bus and go, or take the train (rail transit) and walk from the station to the workplace. In the future of StarCraft, you can pull the switch to transfer to the office by radio waves and reform. Focusing on the goal can help designers eliminating those who are unnecessary for people due to technical restrictions. Many developers and usability experts have design the interface by questioning "what is the task?". Although this may also cross, it will never produce the best solution, and it is generally not satisfactory. When the design interface is designed, the task analysis is useful, but it must be after the user's goals have been analyzed. Only task-based design often has such a risk to make the design to fall into the wrong mode, to design the excessive technology, or meet the company's goals, not satisfying its customers. Question "What is the user's goal?" Let us see this confusion and create more appropriate and satisfactory design.
