I am opposed to putting "best practices", "methodology", and "Framework" on the lips

User Experience is a big topic, starting with a story. I attended the PMP training for two days over the weekend. I noticed a detail of the teacher during the lecture. When I spoke about multiple choice questions, option A and C had a normal pronunciation, while "B" was a boy, "D" reads dog. When I heard it, everyone smiled and thought it was a good joke. However, the questions in the future are all like this. Soon, I figured out that B and D are similar in pronunciation and are easy to confuse. Boy and dog are simple words, and their pronunciation can be clearly distinguished, and there is no confusion like bog and doy. What is this? This is the user experience.

The term "User Experience" seems to have suddenly become popular. It seems that because of the past bitter days, people did not care about dress and dress, and people have been rich recently, and their aesthetics have improved, they suddenly raised their needs. Of course, it is also related to the big environment. For example, many people think that the user experience is the highest. 360 regardless of reputation, products are often used (including pony) as an example of user experience.

The same is true for our company. We must say that we have a user experience, just like the previous two years of "agility. Last month, Zhao, next to me, asked me if I had any friends who could earn an annual salary of 15 million yuan. Although in Beijing, I think this is not a small number, we can see how eager we are for UE.

I have always opposed "best practices", "methodologies", and "frameworks", as well as sticking to my opinions and not accepting others' opinions. No two projects are exactly the same, and no two products are facing the same status quo. Therefore, we should learn successful experiences with a "cleared" and "inclusive" mentality, and analyze them with a "Skeptical" and "critical" attitude; finally, you can think clearly and have a feasible method. In a word, it is against copying and not copying.

Our products are small in size and have few features, which means we may have different solutions than large projects. How to make our products have a good "User Experience", so as to gain user recognition and give a good call? This is a problem I have been thinking about recently. The main conclusions are as follows:

Step 1: identify the responsible person. The user experience is the activity of the product manager.

Do not treat user experience as a live or development activity of UE or requirement. In reality, the UE may not understand the business, and the demand may not be aesthetic. If it happens that your development also plays an important role in user experience, and you will naturally consider it during design or coding, congratulations. This is unrealistic: on the one hand, a team with strong positions and self-organizing skills can work with a sales team. What should I do as a product manager? On the other hand, the aesthetics of each person is different. When coding for each person, the interface display is taken into account, and the style may not be uniform. Retrain, unify the interface style, color match, control shape, and naming rules ...... In this case, we recommend that you use a professional UE. You should consider performance, development efficiency, number of bugs, and scalability for development. The architecture is used as a metaphor. The demand is like a designer who decides what to do. The developer is responsible for civil engineering and building a rough room. The UE is responsible for decoration and making the building suitable for living. Therefore, unless you expand your expertise, these roles cannot independently perform user experience. One of the important responsibilities of a product manager is integration. The product manager needs to handle the problem of user experience globally and comprehensively. The quality of user experience is often affected from the definition of the requirement. Therefore, the product manager needs to run through the project.

Step 2: create an atmosphere

This atmosphere is important for everyone to recognize the user experience, but avoid exaggerating the importance of user experience. Product managers need to take some measures to make team members, regardless of which role recognizes the user experience is very important, and should actively cooperate when it comes to issues related to user experience assigned. By creating an atmosphere, you are also welcome to give your suggestions on the user experience. The product manager needs to make a judgment. These measures may include learning about user experience, internal training, and empathy.

Do not exaggerate the importance. It is true that there is no need to set a user experience frame in your mind when you make the demand; think about how to color when coding; When ue, think about the customer's buzz. At the same time, avoid the plating behavior: in many cases, adding more means a higher chance of error.

Step 3: differentiate the priorities

Grasp the principle that can be used first, and then use it easily. In the initial stage of the project, it is necessary to efficiently complete usable versions, mainly to verify the business ideas and determine the product direction. Xiao Gong, who made GCL and gqi 0.2 billion products, once shared a ppt and impressed me that every iteration of deliverables can work independently. We must avoid making a perfect semi-finished product. Here is a reference to Baidu: Fast iteration, the better the change!

Step 4: separate processing

Our task schedule tends to be too functional to ignore non-functional requirements. For example, in one of our sprints (scrum term, indicating an iteration cycle), function items are often placed on the last day of the iteration. Everyone is busy with functions and bug changes. What kind of loose concerns your user experience? Thank God to catch the last bus every day. Do you really want us to work all night long? Therefore, we recommend that you separate non-functional requirements into a sprint or functional point (often referred to as story in Agile). do not consider these as part of functional requirements.

Step 5: Verify metropolitan entertainment city

What we do is not just customer verification. In show stopper, it is mentioned that katler promotes dog food during the development of Microsoft NT. That is to say, all people must develop on the NT that has not been developed. Therefore, on the one hand, verification is divided into internal and external. Before the product is listed, all members of our team are required to use our products for engineering, which can help users solve problems and are used to challenging our own products. We also need to go out and find different users or customers to try out our products. We also need to be able to try out the third step of the method, fast iteration, the more the better!

On the other hand, do not use a prototype or user interface to verify the user experience. Even the prototype of high imitation is not the software that the user actually works on, it is because you cannot verify whether there will be bugs at critical moments, whether there are performance problems, whether there are silly prompts, and whether there are logical data problems ......

Step 6: Balance

Many people will be happy with Apple's pursuit of user first, how to pursue perfection to paranoia. If there is a ready-made process, Apple will not be so few. A basic skill of a product manager is balancing ability: What should I do if the user experience conflicts with the progress? What if it conflicts with the cost? What if it conflicts with resources? Beware of the spread of user experience. For example, if you buy a camera for 1000 yuan, you will ask it to provide you with two lenses, use Aerospace materials as a shell, use the top-notch Carl Zeiss lens, and have the ability to perform SLR ......

User experience is often associated with progress, cost, and resources. Therefore, it is important to balance the user experience.

Step 7, summary

No matter whether the product is successful or fails, make sure to make a summary of the phase to make it possible to do better. In fact, finding someone with product experience (such as jobs or Zhou Hongyi) may be much more reliable than learning the so-called "best practices". This is a summary.

I am opposed to putting "best practices", "methodology", and "Framework" on the lips