How

The Process

“User Experience Design (UXD or UED) is the process of enhancing user satisfaction with a product by improving the usability, accessibility, and pleasure provided in the interaction with the product.” — Wikipedia

Developing a user experience to the level of customer satisfaction is not a single person or team’s responsibility, instead it is a company’s vision.



I. Understand your user

Finding out as much as possible about the users, their environment and the business. Use Analytical and Quantitative data (conduct actual interviews with users, if possible).

  • Define the issues that need solving as well as the good parts ( in case of redesigns. )
  • Ask if there is an existing UX guideline
  • Establish requirements
  • Create personas / use cases / user flows
Outcome
  • Clear requirements
  • User personas
  • User stories
  • Use cases / user flows

II. Research

  • Analyze other business / competitors. It’s important to explore how the outside is working on similar features / application.
  • Discuss with actual users if possible
  • Evaluate technologies
  • Evaluate ways of implementation ( research latest UX trends. e.g.: )
  • Consult UX Guideline if there is one
Outcome

Ideas and material based on which a design can be build. ( can be anything from meeting notes to screenshoots ).

III. Wireframing + Prototyping

  • Sketch the ideas based on I.Understanding your user and II. Research
  • Quick wireframes and low fidelity prototyping ( e.g. InvisionApp / Zeplin for prototyping ). Always keep an overview of the entire application / product
  • Evaluate and make changes if necessary
  • Consult with product managers and technical experts. It’s important to get an early advice to establish costs and development time frames.
  • For web applications start mobile first.
  • Start preparing content ( it will be needed for the IV. Design stage )
Outcome
  • Wireframes
  • Invision prototype or Sketch Prototype.
  • User flows

IV. Design

It’s important when starting at this stage to have the actual content. For web applications start mobile first.

  • Design the UI
  • Create more prototypes ( high fidelity ) – always test the ideas and use best practices ( consult UX trends )
  • Consult with technical experts ( e.g. front-end developer ). Evaluate and make changes if necessary
  • Prepare and share design specifications by creating a Design System and using Zeplin in order to communicate with the Development team.
Outcome
  • Design images – Zeplin mockups
  • Design System specs like typography, colors, guidelines
  • Assets ( e.g. icons and images )
  • User testing based on a prototype ( such as InvisionApp )
  • There are cases when developing new and innovative features requires testing them using a prototype before actual implementation. This can be done with user interviews. Evaluate and make changes if necessary. Go back to Wireframing if there are new issues to address.

V. Implementation

Implementation can start once the Wireframing & Prototyping stage is ready

  • Build back-end functionality and then the front interface
  • Consider scalable solutions;
  • Involve a UX designer for feedback. Make changes if necessary
  • TEST. Make changes if necessary. TEST.
Outcome

Complete functionality and experience based on designed style.

VI. Evaluate

If new features are implemented, end product needs to be evaluated in order to establish areas of improvements:

  • A/B testing / user interviews
  • Optimize for segments of users
  • Personalize for segments of users
Outcome
  • User feedback
  • Requirements for areas of improvement.

VII. Maintenance

  • Use the Design System for editing or adding new content
  • Involve a UX designer for feedback