UX team Key Performance Indicators
< Takaisin blogi sivulle

UX team Key Performance Indicators

In this post I would like to talk about our UX-team and the Key Performance Indicators used by our design team to evaluate the success of our customer's project processes.

Our team conducts design research with potential users and customers, identifies behaviour patterns and needs based on this research, and determines the form and nature of the solution that will best address the needs of our customers. There are 4 roles in our UX team that cover the needs of every design project: UX team lead, Visual designer, UX designer and Front-end developer. We work in close contact with each other to reach the common goal that we have planned and designed with the customer.

UX team Key Performance Indicators

Our main objectives (KPIs) are to reach the best results aesthetically-wise, user friendly-wise, and in customer satisfaction. We share a common language and overall method from the initial research through implementation. Each role is sufficient for most projects, and responsible for leading a certain aspects of the work with open-minded attitude for input from others.

As a Visual designer, I am responsible for conveying the customer's brand ideals and creating a positive first impression. In addition, it is important that I articulate any visual design requirements, propose a visual strategy and develop and refine details such as typography, colour, icons, images, layout, and so on. A key task is to ensure that the visual representation of the design effectively communicates the information at the expected behaviour and fulfills customer's needs because looks and design do matter in ideal digital world.

User friendly design is also important. Good design is not the only thing that separates the good from the bad. After all, we all have visited those gorgeous websites that blow our mind, but are also (damn) near unusable. That is why the product needs an appropriate skeleton underneath its skin, which means the wireframes. Information architecture is a difficult term to understand, but it pretty much describes the subject best. Data or information needs to be where it belongs and be easily approached and obtained. The Front-end developer has to think and work to make the website or application easy and comfortable to use and make sure that even a person who is not familiar with the subject can find what he/she wants. There has to be a logical structure behind all the glitter, so to speak. Especially if the subject is really broad and takes in a bunch of information, it is important to avoid and reduce the unnecessary bits from it that the website becomes fluent and comfortable to use by anyone.


Seuraava: 10 reasons for Learning eXperience Solutions
Edellinen: Arcusys Beer - Internet & ATK