Stop pursuing the so-called "complete UCD design PROCESS"

It used to be asked a similar question: "Is there any SOP for UX design?" We want to import a complete design process like ideo. Every time I hear such a big question, I am not too embarrassed to splash the other side of cold water, after all, will raise such a problem, must be for the use of experience has a certain pursuit and vision. However, the real situation is that most companies do not need a "complete" design process; instead, what you really need is an "effective and resilient" design process.

In other words, the world is not without a complete set of detailed planning UCD (USER-CENTERED DESIGN) process, in fact, many are, and write a complete. The typical UCD process in the figure UPA below is a good example reference. I remember the first time I saw this design flowchart, I was amazed to send a sound, and then thought: how could it be possible to run all over once AH? Yes, every case can run like this. When companies ' UX team are pursuing more time, more resources and convincing the company bosses to import the complete design process, basically my practical experience is that it is difficult to run through the so-called complete design process, and even if run out, the design project will often fail.

Failed？ Are you sure? UCD design process seems to be very reasonable and rigorous ah, how can not be successful?

The earth is round, and it keeps turning fast.

UCD process is not wrong, every design project, basically must start from understanding users, through user profile and scenario analysis, to find potential problems and opportunities, and then gradually develop concepts, validation, and to the detailed design. This basic principle and people need to eat water as natural, do not need to do more explanation.

Just, in the industry there is no such a lot of time, can be such a complicated and accurate research report, the world is not so clever competitors and consumers, will not move to wait where, let you slowly study the market thoroughly, and then spend another 6-12 months to the product design validation in place.

For example, I have experienced several innovative product development, the research team spent 2-3 months to do meticulous user interviews, contextual analysis, and finally produced a number of resounding user research reports, not only a few specific user needs, but also provides several possible design context. In that moment, the research report is of high value. But over time, a few weeks later, the launch of a competitor's new product has met several of the design needs; two months later, the emergence of new technology has eliminated several problems; six months later, consumers ' enthusiasm for the issue was beginning to cool. At this point, although these innovative products have invested a lot of resources to design research and development, towards mass production, but the value has been greatly reduced.

So the UX team will be caught in an infinite loop, repeatedly hard to find demand, watching competitors keep up, and then leave the "we know as early as six months ago," the regret.

Take out pencils and white paper, simplify communication, speed up

Be too slow, spend too much time, almost every organized, has the process, the quality of the design team, will be surrounded by other departments to complain about common problems. It's not to be denied that every team I've ever had, under different corporate cultures, was all over it, haha. Think back, UCD design speed can be a little faster? My own test results, very simple, as long as the computer turned off, the pencil and white paper out, you will see the effect.

First of all, UCD to understand the user, clarify problems and needs. Since the user is not in the computer, the computer turned off, go directly to the target group of the field, began to do stealth for a long time to observe, if necessary, do a sample interview immediately. and Daily Review, revise the direction and structure of the interview, until the skeleton can be found. This flexible approach, there is no way to achieve impeccable credibility, but in a relatively short period of time, to find a few large design context, that is enough.

Again, the pencil and white Paper will help the designer focus on solving the "consumer problem" rather than solving the "operational problems" of the drawing tools. Do not underestimate pencil and paper, good conceptual design, with a pencil can outline the main structure and outline, to do a rapid divergence with the inspection. If an interface design with a pencil painting, with the mouth to communicate, in 1 minutes there is no way to make people feel the value, then the most probably can be put aside, quickly think of new. As for the graphics software, in the conceptual phase can not be used. It takes a lot of time and brainpower to draw a line and fill a color with this complex and demanding tool. The resources of the mind are very precious, with simple and labor-saving tools. Again, we're dealing with the "subject of the user," not the "operational issues" of the drawing tools.

Then there is the simplification of communication. The cost of communication is very high, especially in the company has MIS department, will regularly update the Exchange Server version of the large companies, communication costs is unimaginable high (shame). For example, I used to take an average of 120-150 letters a day, open 4-5 hours of meetings, and then make 5-10 calls. Do these communications promote our relationship with various departments and speed up the design and quality of the team? No, honestly not at all.

To simplify communication and speed up, the quickest way is to take Rd, PM together to observe the user, and then in a very short period of time, repeatedly "find the problem, solve the problem" process, until the product in place. This saves calls, letters, and fine PowerPoint, as well as a bunch of files that no one looks at. Skipping forms, simplifying communication, and spending every effort to produce effectively, is the spirit of agile development, echoing the recent rise of lean UX.

However, can only be designed to speed up? Of course not. If your home PM, take this article to buckle your hat, ask them to look back to see how much of their work, the proportion is purely convey the message, the exchange of views, and reminders progress and other types of administrative work. Please save them a little bit of effort on the meaningless things, spend more time with the research and development team to plan products and solve the user's problems. UCD is EVERYONE's AFFAIR, only everybody cares, all agree, only then may see the result.

Is it all right to do what it says?

Product development There is so simple, uh.

The ideal UCD design process will be like the one mentioned by Bill Buxton in sketching User interfaces. From left to right is a gradual convergence of the process, over time, from concept sketches, gradually shaped into design prototypes. There will be constant according, but the design direction will be gradually clear, the design department will devote less resources.

But the actual situation is more like the figure below. Information Architecture (information architecture) with interface design In addition to investing a lot of effort in the first half, there are usually at least two highly hectic periods of time before the program develops the initial version and the product goes public. The resource inputs for this period are theoretically unnecessary, as the design architecture has been identified and the product development variables have been minimized. However, there are accidents, people have unforeseen. Product development must encounter a variety of conditions, such as the development of platform Update SDK, the boss asked to add new features, 0 component suppliers fell, anything is possible, unexpected situation is always more than you expected.

So be sure to make your design process more "effective and resilient" and always keep an optimistic and humorous heart. Now turn off the computer, take out a pencil and white paper, and do the design in a different way. Maybe you'll be happier and more fulfilling.

Extended books:

Sketching User Interfaces

http://www.books.com.tw/exep/assp.php/handyui/exep/prod/booksfile.php?item=F011092596

Behind the napkin: a pen + a piece of paper can solve the problem + convince the boss and customers

http://www.books.com.tw/exep/assp.php/handyui/exep/prod/booksfile.php?item=0010418902

Source: http://www.handyui.com/2011/10/06/no-more-comprehensive-ucd-process/