Where does the perfect user experience design come from?

Personally recommended this article, a more comprehensive description of user experience design and at different stages should pay special attention to matters. Attachment is the canonical flow of UE.

Last week translation on the home banner good surprise, thank you ~ ~

Most people think that the perfect product user experience can be achieved as long as the product's interface visual design is exquisite enough.

Is that right? To be honest, this view is not correct.

In fact:

The first thing I'll tell you is that the user experience (users experience, UX) has nothing to do with the so-called "out of the beautiful graph."

The user experience is a process that ideally starts at the strategic level and affects the entire lifecycle of the project. User experience design first needs to understand the business model, then the landing user research, and understand how the service is integrated into the user's expectations.

User experience is a very important part of business strategy development, and interface design (user Interface) does not represent the end-loop of user experience. We still need to test the user, provide support in the product iterations, and even after the release of the product, we need to adjust accordingly.

So, how do you work out the best product user experience strategy?

Generally speaking, the user experience process has 6 different stages. 3 of them are explained in this article.

1. User Experience Research and analysis

Here you need to know the context of your product, identify the target market for the new product, and the stakeholders involved.

It is important to understand the company strategy – the company strategy is able to describe their brand, vision and guiding principles. The "strategy" behind a user experience project will affect the project objectives:

How much success does the company want to achieve in this project?

How to measure the above "success"?

What is the priority of each task in the task list?

The most difficult thing in a product user experience is not the work itself, but the ability to maintain a good relationship with many project stakeholders. You can often hear this from the stakeholders ' mouths:

"We don't need a user experience now ..."

"Yes, I know you're a user experience expert ... But can you make the menu bigger, the content of the site more like this ... "

The user experience is more than just an idea.

Ideas are just the basis of design. The idea is not to stand the test, you need to have a thorough scrutiny of the deficiencies in the idea. The hardest task is to convert an idea into a design. When you have a good idea, do not immediately start to develop the transformation, but should further refine the idea, first let the idea into a concept.

The best way to build a concept is to collect feedback from different sources, including those who are interested in the success/failure of the product.

Be careful......

People rarely make pure rational decisions based on careful cost analysis, more often in the sense of emotion rather than logic/conscious thinking to make decisions. This is not a benefit to us: our irrationality is predictable. A good user experience designer needs to collaborate effectively with product owners, engineers, leaders, and other stakeholders, as well as understanding how people make decisions.

At this stage, the following things are often done by the user experience:

Mind Storm;

Competitive product research, best case study;

Internal Focus group interview (within the company department);

External Focus group Interviews (project stakeholder analysis);

To find project members with interdisciplinary backgrounds to ensure complete expertise;

The research phase may be the most variable part of the project. A large project user research institute is very complex, and a relatively small start-up company website project can be directly skipped user studies, only need to do some informal interviews and questionnaires on it. For many user experience designers, this phase is the key to creating a good user experience, but it is also the most overlooked phase-because it does not conform to the "streamlined" approach.

You are ready to start exploring the user experience vision for your product at this stage. In order to ensure the next stage of orderly development, a good way to organize information is to try to build user files, situation files, conceptual models. Collecting and sorting from "What" can help you to understand "why."

2. User Experience design and development

This is my favorite stage. You've collected enough information from the first phase, and you can integrate all the ideas in your mind and continue to build the product architecture.

Note that this is a very important milestone. Your construction of the product must be based on the time span of the next few years.

In fact, this phase is more iterative. You can start creating prototypes, putting ideas in front of users, getting feedback from users, improving them, and then repeating those steps. You can sketch sketches with a pen and paper, then design them in detail, and then place the sketches on the interactive wireframe and prototype.

After you have completed the high-fidelity design and confirmed the design version with the stakeholders and end users, it is time to enter the development phase. At this point, the user Experience designer's role is transformed from creating, validating ideas to collaborating with engineers to develop frameworks and beta versions.

The common user experience tasks at this stage include the following:

Wireframes and Prototypes

Set Availability Metrics

Flowchart and User Experience map

To build a complete framework

Α/β version

As mentioned above, this phase is iterative. This may explain why there are many synergies between user experience design strategies, agile development principles, and lean entrepreneurial thinking. It turns out that regular user feedback is at the heart of all product development methodologies. After each iteration releases the test version, evaluate the product feedback results, based on the priority order of the tasks after this adjustment.

3. Publish and evaluate the beta version

At this stage, you need to understand how your product works in real-world situations.

There is no doubt that you will not want to see the product become a failure when it is officially released. So you need to be in the usability testing phase to find out if there is a problem with your product design. Formative testing is a way to get up early in product development to quickly discover the usability of a product and to improve it, as well as part of the iterative design process.

Time is of paramount importance. Observe and listen carefully to the problems that the tester is faced with and be wary of the possible triggers behind the problems. Remember to keep track of the use of the product and continually improve the product.

Remember three things:

The first time can not be perfect;

Finding problems does not mean failure;

Users will always give you a surprise.

Giving your insights to drive product launches or new product designs, which is why usability testing is widely popular.

The common user experience tasks at this stage include the following:

A/b Test

Custom Tests

Use log

Analysis and telephone support