Serenity, study case
Case study to evaluate possible improvements in a Serenity dashboard; Adevinta's internal product, in this case a fictitious proposal for a Dashboard for the coordination of UX and product research, a UX repository, was generated as a deliverable.
Duration: 1 week
Tools: Figma
Role in team: Product Designer
Benchmark
A review of the different direct and indirect competitors of the UX repository was carried out in order to define the main points to be considered, the following points were highlighted from this analysis:
The importance of a visually simple platform with clear levels of information.
The presence of a constant navigation menu, and allows the visualization of the sections clearly.
The use of filters in a quick and visible way, with a variety of options, allows the information to be found quickly.
Flows definition
When defining the navigation flow, the following had to be considered:
The definition of the sections present: Home, Projects, Favourites, Contacts, Users, Tags, Highlights, Settings, FAQ, Help, User.
Establish the home pages and their landing pages after logging in.
Define what actions can be performed when you are in the main Dashboard.
Wireframes
The definition of the screens was carried out by means of low-fidelity sketching, in order to be able to quickly evaluate the diagramming of the information and also to be able to check the flow already defined.
Definition
The design and prototyping were carried out for the evaluation of the proposal, which can be seen below.
Dashboard homepage
Modal for the new creation of a template
Editing of a page
Project page
Highlights
1 __
The integration of quick access buttons was defined to facilitate team communication, in this case: Slack.
2 __
It was proposed to integrate the use of tags in the content so that users of the platform could find it quickly.
3 __
A proposal was made for the use of templates for the creation of the different case studies, examples of the templates would be: interviews, survey, notes, user persona, card sorting, journey map.
Conclusions
As it is simply a case study for evaluation, it can be highlighted that the next step, possibly necessary, would be to study it with the users, in order to evaluate with them the need and feasibility of the project. In the same way, this case study allows at an initial stage to have more information for business decision-making.