[Original] UX process (User Experience Team workflow)

I recently worked with UX team on a project, and the cooperation in the initial phase was very painful and depressing (before process )........ here I will sort out and introduce the final UX workflow, hoping to help others.

 

Additionally, the UX team is the user experience team. Some projects may encounter conflicts between the developer and the user experience team, and the focus of the conflict is: who should lead the project? Driven by the UX team? Or development team-driven? In fact, there is no only answer to this question. My personal point is to select a suitable mode based on the project characteristics and personnel conditions.

 

The UX driver can help users get desired products, improve user experience, and increase user satisfaction. Development-driven projects usually focus more on the implementation of business and functions. The product manager will always serve as a bridge between users and teams in development-driven projects, the user experience communication here is more dependent on the personal experience, abilities, and energy of the product manager (many product managers are responsible for multiple projects at the same time ). For a Ux-driven project, the UX team can analyze user experience from a more professional perspective, and propose operations and process suggestions based on the data generated by surveys such as existing user operation habits, design a UI that better meets user expectations. This helps the project team develop a customer satisfaction prototype faster in the early stage of the project. For example, if the project is an upgrade to an existing project, the UX staff will observe how users use existingProgramWhen they complete an interface operation, the UX staff will record the order of user information entry, and the mouse sliding track, and on which operation the user will switch the mouse and keyboard? Which of the following operations (buttons or information items) are prone to errors? During user operations, UX personnel also ask and record user satisfaction with existing interfaces and improvement expectations. Then, sort out the operations of the new system and the basic page principles, such as: more shortcut keys should be supported for daily users, while common modules for managers such as charts and reports, to the maximum extent, only the mouse is supported. For example, you need to manually enter the date period before generating a report in the old system. Managers are usually interested in data from the last week, the last month, and the last quarter. The time period drop-down list is available on the report generation page, allows managers to quickly select weeks, months, and years, thus reducing the chance of incorrect input time periods ).

 

A Ux-driven project usually has a good user experience, but it brings challenges to developers. For example, in order to pursue a better user experience, the Ux-driven B/s program prefers to adopt the Silverlight and flex fat client models, greatly improving the user experience. However, few programmers are familiar with Silverlight and flex. Many development teams need a learning cycle to start Silverlight and flex development. In addition, because the focus is too much on user experience and interface effects, the project team can easily find problems such as security and performance in the future.

 

Many domestic UX Staff hope to try to use the UX driver in real projects because of their foreign praise for the UX driver method. Therefore, the product manager must be clear-headed and should not be influenced by the new concept. Select an appropriate development mode based on the actual conditions of the project team. When the UX team already has experience with the UX driver, or has senior UX staff, or you are working with a familiar UX team, we may try to adopt part of the Ux-driven model in the project to facilitate user satisfaction. The following is the UX team workflow for a project that wants to partially introduce the ux driver:

 

1, (meeting: developer, UX team, Product Manager)

1. The product manager introduced the basic functions of the module to UX: business logic, basic information of target users, and module objectives.

2. Product Manager, UX, and development team discuss basic page migration pageflow and page logic.

3. The product manager, UX, and development team jointly design the wireframe of the page.

 

2, (UX Team)

1. UX implementation line diagram and Interactive Design

2. UX interaction design description (draft, no detail)

 

3, (meeting: developer, UX team, Product Manager)

1. UX introduces the line diagram and interactive improvement, and solution details

2. Adjust the details of the solution based on the business logic, target users, and module objectives.

3. Get product manager approval.

 

4, (UX Team)

1. The UX improvement line diagram and interaction instructions are sent to relevant personnel by email.

2. Product Manager approval.

 

5, (UX Team)

1. UX implementation uses black and white graphs to implement pages (the purpose is not to let everyone focus on the review color discussion)

2. UX provides page interaction and operation functions (document)

 

6, (meeting: developer, UX team, product manager, high level manager, customer)

1. UX introduces page functions, purposes, interactions, and operations.

2. Record Customer Suggestions

Objectives and conditions for entering the next step: the customer accepts the design of the existing interface.

 

7, (UX Team)

1. Update page and document.

2. product manager sends page and document to customer.

 

8, (UX Team)

1. coloring

 

9, (meeting: developer, UX team, product manager, high level manager, customer)

1. Review the rendered Interface

Objectives and conditions for entering the next step: the customer accepts the design interface and confirms the Basic Color of the system.

 

9, (developer)

1. Some module prototypes are implemented based on the process and operation description.

 

10, (UX Team)

1. UX review prototype

2. UX And product manager confirm that the prototype meets the requirements

 

11, (meeting: developer, UX team, product manager, high level manager, customer)

1. Review the prototype with the user and confirm that the design meets the user's expectations.

At this point, the work of ............. UX has basically ended.

 

* Note: After designing two or three interfaces of UX, define the UI style guide based on customer feedback.

 

The above is my cooperation process with UX team. If you have other better experiences, please share with us. :-)