Create a user Experience

Maybe you just came to a company and they want to do some "usability" work. You may be a UI designer, business analyst, or front-end developer, a product manager, or a manager or VP in charge of the user Experience Department. You know, if you have a better understanding of people who use products/software/websites, you may develop better products/software/websites. No matter what, no matter who you are, no matter where you are, the user experience this matter, it is now for you.

Well, you might want to build a user experience (UX) process, of course, such a process may be value-for-money, can also bring disaster, but there are many opportunities to improve the process of product development, of course, including the product itself.

Where do you start with a process like this? What methods can be used? What problems need to be avoided? How can you keep your motivation, keep your enthusiasm, and stay professional and not discouraged?

Why build a user experience process?

• The user experience process helps to develop products that people expect and meet their needs
• The user experience process can save time and money

Remember, these two points are strongly linked to what many people in the company value: Money . Whether it is through sales revenue or reduced spending through savings, it is practical to begin to explain the value of user experience activities from the financial impact.

Start Small

Starting small can prevent you from accidentally can chew, and can also help you get down to the ground and start a process. Gradual progress is more effective than starting with radical changes in all aspects of the process.

Remember to record UX activities and outputs and track their progress, and they will be useful in explaining your UX process in the future.

Find business drivers and track them

In simple terms, let the numbers speak. Identify the company's goals and keep the user experience process goals in line with it. For example, if the company's main goal is to save money by reducing the number of technical support calls, one of your main UX goals is to improve usability, improve the product's self service rate, and record the number of technical support calls before and after the process.

Plan UX activities in advance

Another benefit of starting with a smaller project is that you are more likely to exert some impact on the project plan. Participating in the project plan at an early stage gives you the opportunity to prepare your project team for UX integration.

Go deep, don't roll it out

Avoid distributing yourself to too many projects. If you're the only person in the company who has UI design and usability research, the project managers may want you to help them support each project. You need to avoid doing so at all costs. Because the more projects you serve, the more likely you are to have a discount on the quality of your service. And you will soon be exhausted and unable to make substantial changes. What happens when resources are limited and demand is high? One compromise is to develop your UX team and try not to shop too hard at the beginning.

Be realistic and be flexible

Make a realistic assessment of the company's support for UX and adjust your expectations accordingly. If most people in the company don't yet know the concept of UCD and usability testing, you probably shouldn't be doing ethnographic research for months or spending a lot of money on field usability tests.

Be flexible, while presenting your ideas and suggestions, let people see that you take care of all aspects and compromise when needed.

Remember: There are lots of fruit to pick, don't worry too much about how to pick them, just make sure to take them off.

Pay attention to scrappy, but don't avoid them.

No one wants to hear that using their methods will get bad products, or that the company will lose money, no one will want to hear you say, you are right, they are wrong.

The key is to show them, not to say, to convince, not to state, use screen/video capture tools, such as Morae, to convince developers that by conceptual design and prototyping you will make their work easier and take less time. Let product managers see that you can help them define business requirements better.

Have the patience to set clear expectations

While building a new user experience process, it is most difficult to be patient. A good UX process will not happen overnight.

Be creative

Because your resources are almost always limited, you have to be creative and let your team see that UX activities don't need to be expensive or require a lot of time:

• Representative users within the company can be used as user resources
• Remote interviews and availability activities in the context of insufficient budget
• Not enough staff? Teach your developers some best practices for UI design
• No budget to buy expensive softening and research tools? Pens and paper can be used for your unexpected use
• E-Mail The UX lecture excerpt to spread the UX message in a wide range
• Make a poster showing common UX errors and classic Solutions

Record your results and do not hesitate to release them

It's probably the most important thing to promote UX in your company. You've done so much, now it's time to put everything together. As long as the results, no matter how small, should not hesitate to release them in the company, and, do not forget to thank the entire team, of course, ready, and more work will fall on your shoulders.

full text See :pioneering a User experience (UX) Process