-------------------- Chapter 1: Target Guide Design -------------------- Our book There is a simple premise if we use the target of the user as the foundation of the design process, the user will be satisfied and happy. If the user is happy, he will be happy to pay us money (and recommend others to do this) so that we will become a career. From the surface, this hypothesis is really easy to see some direct white: let the user happy, your product will succeed. Then why there are so many digital products so difficult to use and hate? Why do we not be happy, or succeed, or is it happy and successful?
-------------------------- Digital products require better design methods --------------- ------------ Many digital products are now produced from the development process like the monsters appear from the bucket overfoam. The developer, instead of their users to plan and imaginary operation in their brains, ultimately form a solution in technology that they can finally have a point of control. Just like a crazy scientist, they failed because they did not inject humanity in creative. Design, according to the definition of Industrial Design Victor Papanek, it is intended or intuitive efforts to improve meaningful sequence. The authors are prepared to be a more careful definition: ● Understand user hopes, need, motivation, and context ● Understand the needs and constraints in business, technology and problems ● On the basis of commercial feasibility and technical feasibility, put the top two points Knowledge Conversion becomes a product plan (or product book), which makes the product form, content, and behavior, available and pleasing these requirements for all design disciplines, although more attention to the appearance of different design disciplines or content is still It will be different. When adopting an appropriate method, design can provide technical products to provide currently missing human communication. However, it is obvious that the method of digital product is now not able to implement or cannot reach the declaration.
----------------------------- Current Digital Product Design ---------------- ------------ Most of the digital products are built in the perspective of the engineer. Indeed, market staff will sometimes provide demand, but they rarely study users' practical needs, and more are based on competitors to provide a list of feature to IT staff, or on the basis of user surveys or customer hopes. Speech. These methods do not help the system's constructor to achieve the user's goal. Below we will discuss why the goal is so important. Developers and users have a completely different, technical and engineering methods - based values. At the same time, market staff is concerned about things, feature lists that can be paid attention to, and people say they will buy. User, if you ask questions and the products they are using, generally pay attention to the low-level mission - the opposite you guess, very few users know and clearly express their goals. The result of this is that unfortunate, software disrupts and reduces productivity, and cannot meet the needs of users. Figure 1-1 shows the evolution of the software development process, including the participation of the decline in the final improvement. The development of most digital products is still in the first, or second, three histograms, which is designed and not playing actual roles or just in a bad interaction. In the case of a customer of the author, it is like "lipstick on the pig's mouth". We will discuss that the design process should confirm that the product is indeed satisfied with the user's request before encoding and testing.
Software development process evolution
1. Initially, programmers do everything: In the original day of the software industry, smart programmers make useful software and write it, and then test it. But with commercial growth, software business and software production become more complicated. 2, the manager brings order: inevitable, professional managers have produced. Excellent product managers understand the market and competitors. They define software products by establishing a demand document. However, it is generally not more than a list of characteristics, and the manager finds that they have to get the progress of the feature. 3, test and design becoming an independent step: with the maturity of the industry, tested independent disciplines and independent steps. In the conversion of the graphical user interface from the command line, the design and availability is also included in the process, although it is often only the end of the process, and often only works on the appearance. Now, usual practice includes simultaneous coding and design and subsequent BUG and user testing and correction. 4, the design must be performed before the start of the programming: the software development of the target driver means that all decisions are all officially defined users and his / her goals. Define the responsibility of the user and user target designer - so the design must be performed before the program is written. Figure 1-1: The evolution of the software development process. Now, design is often a remedy. It should be done before encoding and testing.
Here are some examples to illustrate why just focus on technology, market, and tasks (rather than designing the goals of users and users), we all feel dissatisfied (?) Software.
Software is rude software to treat users. It is not caused by the user, which is not caused by the user's failure, or should not happen because of the user's failure. The message box like Figure 1-2 is like a mourning dress, and the user declared that the user failed again. And this news also needs to recognize his failure and use OK to agree.
Figure 1-2: Thank you for notifying me. But why does the program do not inform the library? What does it want to notify the library? Why don't it tell us? Why should we care about this? And why should we want OK? The procedure failed is not OK!
Software often interrogates the user, the user does not want to answer the question that is not prepared to answer the question: "Where are you hiding?" Or do you still have some other reason for the DELETE key? "Follow the user as the pepper water, put them in the low position of inequality.
Software makes unfounded guess software often assumes that its users are computer experts. For example, when a user edited a document to turn off it, the program will ask if he wants to save the file. The technology about this problem is not simple. How can the computer's primary users can know for the CPU you have to do this, but how can the computer's primary users know?
Software is a hard-to-understand software is often embarrassed, hiding its intentions, purpose, and action on users. The programs often use ordinary users to express themselves, such as "How much is the end bit?" (How Many Stop Bits?) Sometimes even more professional "Please specify IRQ.". Features Hide under the Menu dialog and the window shielding. How can users know that the answer can you find in the help system? If he even helped the system can't find it. Even if the user finds the correct dialog, he will find the net discharged above is unknown abbreviation, obscure command and unpredictable icon. More than you guess, the software requires users to answer difficulties, but do not tell them what is the effect of different answers. For example, how can the user can decide to be completely installed, custom installation or laptop installation, do not tell him the difference between the different options in the function and hard disk space?
The software is not properly if a 10-year-old child is like a software, he will definitely be closed in the room. The program forgot to close the door, throw the shoes in the middle of the house, can't remember what you tell him before 5 minutes ago. For example, if you save a Word document, print it, then close, the program will ask you if you want to save! Obviously, printing this action allows the program to think that the document is changed, even if it does not change. Oh, I am sorry, my mother, I didn't hear what you said? The program often wants us to stop the main task process, and to complete some of the originals should be able to get functions. The dangerous order is often placed in the forefront, and the user who has no care will trigger them. Many overall appearances of programs are over-complex and confusing, making it difficult to understand. So, is this there is a problem? Why does the technical industry have such problems in the design of interactive products?
We don't know anything about the user is that the digital technology industry has nothing to understand how to please users. In fact, most of the technical products are built on the basis of understanding users. Perhaps, the market sector will divide the users. How much do they earn, how much money they spend on weekends, what kind of car they buy. Maybe we will work what kind of work like them and their regular main tasks have a blurred concept. But do everything tells us how to make them happy? Do you tell us how they will actually use the products we build? Whether to tell us why they need our products to do something, why they have chosen our products rather than our competitors, or how can we let them choose our products? Unfortunately, we can't get these answers. We will discuss the behavior of understanding customers and their use of products.
We have a conflict of interest, causing a problem that suppliers and vendors can't please customers are that there is a serious conflict in the development of digital products: programmers, people who build products, are generally those who design products. Programmers often need to choose between convenient coding or convenient use. The programmer's work is generally judged by the efficient encoding and catching the incredible urgency, then it is not difficult to get most of the software products. Just as we will never allow a person to trial his own case, we should also ensure that design products and construction are not the same. Make programmers simultaneously take care of users, business and technology obviously impossible.
