Discovery/usability findings
June 6, 2017 - Amsterdam
Note: All of the conclusions and opinions in this presentation are my own. They are assumptions & propositions based on exploring the current website, through discoveries online or from personal experience. These have not yet been validated nor properly tested.
- Aäron Sikkink
Disclaimer
June 6, 2017 - Amsterdam
Before coming to any concrete conclusions and/or suggestions, we should be able to answer these essential questions first:
June 6, 2017 - Amsterdam
After a closer look at the site, the following strategy/goals seem important:
June 6, 2017 - Amsterdam
Not all questions can be answered, but it's clear the website focusses on the following target groups below. With that in mind, we can serve the content better, and convey the right tone of voice.
June 6, 2017 - Amsterdam
Without having access to website insights or user data & task flows (completed or uncompleted), it is obviously hard to make suggestions that can improve the strategy (measurable goals), and the relevance of the presented content. However, there are some improvements that can help the following:
June 6, 2017 - Amsterdam
The main unique selling point (USP) for Elsevier is its content. Therefor it is of the utmost importance to make it easy for the users to find / read the content they need. In the Invision Prototype example below you can see some of my ideas.
June 6, 2017 - Amsterdam
While scanning the site on desktop, mobile (ipad/iphone) I stumbled on some errors or design inconsistencies that really should be looked into.
June 6, 2017 - Amsterdam
Besides optimizing for mobile, mobile design needs some adjustments to make it better readible. The touch areas (top level icons) are too small for navigation.
June 6, 2017 - Amsterdam
June 6, 2017 - Amsterdam
For viewing my presentation.