Reducing user workload
With a solution where risk behaviors in traffic is reported in real time to the user, we faced a challenge: how to reduce the users' workload, directing them only to what is emergency at a given moment.
In this job, my role was the UX/UI designer within a multidisciplinary development squad. In addition to carrying out all the UX and UI work, I also actively participated in business rule definition conversations and technical definitions with technology members.
1
Identifying the Problem
Since the pain point had come up during a conversation with an internal stakeholder, my first step was to look for evidence of what was being said in previous researches.
In addition, I also did an analysis with the technology team to identify the amount of information generated by our system.
2
External Research
With the previous research, it was possible to prove the pain point, however, I still felt a lack of understanding about how the customer dealt with risk situations in real life.
For this, remote interviews were carried out with users and also with internal specialist consultants.
At the end of each conversation, the process detailed by the interviewee was outlined.
- Remote user interviews;
- Interviews with internal expert consultants;
- Detailed schematic of the process;
- Customer pain point discovery
3
Ideation
As this was a significant systemic change, I chose to do a brainstorm with several internal stakeholders.
Activities related to the subject were created, using the "how might we" technique as inspiration.
- Unique solutions based on usability techniques
4
Prototyping
With the results of the previous steps, it was possible to design a new page in the system that included the solution.
In the initial version, however, it was necessary to leave some information aside due to technical restrictions. To get around this, we worked with re-directions and links.
5
Tests & Design Critique
With the design created in Figma, we started usability tests. In addition, we carried out a design critique round with the squad responsible for development.
Both interactions brought several improvements and points that needed to be defined before going into development.
Conclusion
The result was a feature with two main characteristics:
- User with freedom to configure and let us know what they consider important;
- Work with an information grouping system, allowing user to deal in information in batches.
