Web App Usability Audit

Process

At the beginning of the project, it was unclear exactly where the client needed assistance. The client mentioned their intention to update the now significantly outdated user interface by addressing so-called “low-hanging fruit.” I proposed conducting a UI audit, as its outcome would clearly indicate areas of the interface that needed improvement and reveal those low-hanging fruit.

To perform the audit, I first needed to research how audits are conducted. I checked various methods and came up with a suitable (yet broadly applicable) audit checklist based on my findings. This checklist included 11 categories and 62 criterias.

Together with the client, we identified two critical user journeys within the application. The audit was then conducted on the views related to these user journeys specifically. Each user view was examined individually using the checklist I created. All of the findings were documented in the Figma software.

Outcome

A comprehensive and clear Figma file was delivered to the client, which included:

• The audit criteria checklist
• Two examined use cases and their containing users views
• Detailed notes on findings
• Possible fixes

The views contain clear indicators that show which audit criteria item the identified issue relates to, along with explanatory text that describes why the finding is a usability problem.

Possible fixes provide the client with guidance on how to start addressing the issue. If a solution from other services or interfaces came to mind during the audit, I provided it as a potential solution in the documentation.

The results were delivered to the client in a meeting, where they were also given the opportunity to ask any questions related to the audit or the findings. The client was satisfied with the overall outcome and believed that they could “utilize the results in their future UX/UI updates.”