How UX improves the development process

A company must operate in a way that does not rely on the congestion of a human brain to take the lead, and there are many things that need to work together. Ui/ux is a very popular topic recently, and has come to the point where everyone speaks well of users. Speaking of which, in what phase of software development do you want to import UX? This article, from my perspective, demonstrates how UX can improve the development process.

As far as I can see and understand, a software development process is usually as long as this: Customer wrangling > Bargaining > Writing specification > Signing > mockup Modify > Mockup Modify > Mockup modify > Set and cut to rd > Gavin function > Add new function > Patch diagram > RD quick Turn table > write more than half of the first test to see the > plus new features > time to fix the Bug first launched to say > ... > Closed > (Behind the flip-flop brick)

1. About 95% of customers don't understand UI flow, and no one is finding fault at each output.

2. About 90% customers modify Wireframe to add new features, not which side is weird.

3. About 85% customers in the early development will be Gao, and so mockup to start feeding the son to eat C.

4. About 80% of customers pretend to know what they think, and 100,000 can also frame a Facebook.

5. About 75% customers will be in the Code are almost finished to send a test to say that the page has problems to change.

6. About 99% customers do not understand Chinese and English after signing, feel that the specification book is to take to eat not to see.

　　How long does this project take to revise?

PM must have experience, obviously caught a lot of reserved time why to the end or not enough to rush to death, hastily closed. Although customers are accustomed to be very arrogant, think add new features and drink boiled water as free simple, but there are more times is to change back and forth to eat most of the time. I believe many people in the industry know: "If the design time before the development of insufficient time, development costs will increase more than three times times!" Yes, know to know, the Wireframe to PM or BD planning ... That's a good thing, right? Wireframe designed by non-professionals Why do you think it won't be a problem?

I will strictly follow the functional Map > UI flow > Wireframe > Mockup process, in order to minimize the number of changes to and fro.

The results of these three phases of output are given to SA, RD acknowledgement, especially UI flow and Wireframe, which are related to the logic of their threaded pages. If you are involved in membership systems, shopping carts and so pay more attention to the integrity and simplicity of flow, a careless may become very disgusting sticky slippery slug, muddy also attached to catch the worm. The cost of changing back and forth in these three phases is much less than when RD starts to write Code and finds problems. As with cavities, the initial treatment at most to wash a small repair, reluctantly dragged long root canal treatment or knock back to practice the false teeth ... Will this save time and energy savings?

The importance of professional UX

UX's biggest job is to communicate with users, do tests, design UI flow, draw Wireframe, and write files. But the boss, who is usually called UX, does not want to be able to communicate tests and draw boxes as instructed. UI flow and Wireframe are important enough to extend the development process by 10 times times or with less effort. Unfortunately, the number of people who recognize this is very small, compared to washing the teeth, as if most people are more like root canal treatment. Let the layman (PM, BD) part-time Wireframe result is to produce a bunch of specious, dead RD, the feasibility of very low planning.

A good UX can use simple logic to design an Easy-to-use interface. This means that not only users are easy to use, even RD will feel the interface is good, do not worry about various pages and many of the connections between the state is too complex. The more confusing the more difficult the logic is, the easier it will be to create bugs, and when the worms are full, what are the time to make a steady flow of apps?

　As an example

For example, the simplest and least visual element of a word-table App is almost 1 functional. Preview all kinds of fonts, 2. The appearance of various characters.

Point in the upper right corner of the font list, scrolling screen various word level preview.

App:rainfont

Sliding left and right to switch a variety of fonts, up and down scrolling zoom in to reduce the word level. Click on the bottom left corner icon appears font list.

From the top two examples it is clear that the pros and cons of almost the same function, there is no UX intervention is very large. The same can meet the needs of customers, but the operating experience, interface design, future expansion, and so completely different.

The demand interview before signing up will add UX!

The attendees who usually engage in customer interviews may have PM, SA, at this stage, please pull the UX in, since UX is responsible for the entire interface design, he must have a lot of information to be asked from the customer, such as: This App is "Hyun"-oriented, or "functional" oriented? Who are the target groups? Need and what kind of advertising or marketing way to match ... Wait a minute

Good UX is familiar with all kinds of guideline, and the benefit of adhering to the guideline is that there are almost built-in elements available that allow RD to save a lot of effort. Experienced senior UX can even at this stage will be able to the customer's fantasy to block or change both sides can accept a more time-saving and labor-saving way to execute, so that RD will spend a lot of effort in the development of unnecessary features.

"Should not just users feel good, even RD should think the Code is good to write can be called the design!"

Simple interface is not only easy to use, the logic is also simple, simple logic means that RD will also be easy, less error-prone, QA also do not have to test again. The time course pressure is small, PM also will not be hunted down every day by the customer. At the beginning of the development of the UX will definitely significantly reduce the pressure on various departments, and make the project more practical implementation, and the sudden situation and the number of insects will be reduced.

Liberation PM/BD

PM and BD Professional will not be the user experience, do not force them to do beyond their professional field of things, Shaolin Kung Fu and singing and dancing there is no play? Since the demand for highly paid legislators is only to not fight, why do grassroots officers have 18 classes of martial arts and everything? It doesn't make sense to go back to the pros when it's time to do something for UX.

Add UX when you need to interview.

Adhere to the functional Map > UI flow > Wireframe development process.

The output of UX at each stage is to be confirmed by the relevant personnel.

Don't let pm/bd design flow, Wireframe, that's UX work.

Do not let SA/RD/PG design flow, Wireframe, function will run to the first floor, into the public Office Web page.