At the end of our process, we want to be able to present tangible results with concrete recommendations for action that really help our clients and their product teams. That is why, in the first step, we define UX principles together with our clients, which we use to review the product.
First we look at the overall information architecture and the general impression: Is the application clearly structured? What is the general performance and stability like? Then we work our way to the details: What do the single processes look like? Is the user guidance clear and distinctive? Finally, we look at the building blocks of the application: Are the right UI elements used? Are buttons correctly named and icons semantically correct? The previously defined UX principles always serve as a benchmark. This creates a comprehensive picture of the status quo.
We are experts in user experience. The technical expertise, however, lies with our clients and their users. That is why it is important for us to involve the actual users. In this way, we can respond to "learned" and domain-specific aspects. With qualitative user tests, we test our hypotheses and base our recommendations on statements from real users.
We do not leave our customers alone with the findings from the review. Our specific recommendations on weak spots can be easily integrated into the development process. Such a recommendation could be, for example: Write "Delete" instead of "Confirm" on the button in the delete dialogue. When the recommendations are implemented, you can achieve an enormous positive effect on the user experience even through small adjustments.
The UX Expert Review concept can be applied to a product several times. By conducting regular reviews, progress over time becomes measurable. This makes it possible to check whether the measures taken have actually contributed to improving the user experience. Combined with UX KPI, it becomes a method for measuring user experience and anchoring it in the development process.
A UX Expert Review does not replace the user-centred development process. It is a neutral view from the outside and a first cost-effective and non-binding step towards this. It offers a solid foundation for possible new developments and helps to sensitise internal decision-makers to the relevance of UX.
Are you facing similar challenges?