Prysmian Group is a world leader in energy transition enabling technologies. They provide the most comprehensive range of services and know-how in the industry. Every year, the Group produces thousands of miles of underground and submarine cables and power transmission and distribution systems, as well as medium and low voltage cables for the construction and infrastructure sectors.
I was tasked with redesigning the time tracking application used by Prysmian Group employees and managers. The problem definition stated that the target audience does tends to not use the current application and that the application needed to be updated. As a result, I made it a priority to identify the needs and wants of the users. I used both qualitative and quantitative methods to identify the pain points and motivational drivers.
During my investigation, I discovered that the employees lack the motivation to track their hours worked.
This prompted me to further investigate with the use of interviews and empathy mapping.
These were the reasons as to why the employees neglected their duty to track their hours worked:
For starters, they mostly found it a 'hassle' because the current one's design is very outdated, having been created in 2004. It was inefficient, so they put off filling in the hours for the previous days until the end of the week. When you forgot it once, you ran the risk of not tracking anything at all.
Second, there were no repercussions because another party filled in the hours if they were forgotten. When you combine this with the fact that the entire process was difficult to work, it became a routine.
Ultimately, the employees demanded an efficient tool that, quite frankly, provided a better user experience. A tool that could handle everything from checking in to requesting time off.
Because the client has already defined the medium of the solution, a web app, I began my research by analyzing the user flow required for the requested experience. I decided to create a user flow chart and streamline it to eliminate clutter. The goal was to make it as simple to use as possible, with no distractions or 'hassle.'
Following my research, I began the prototyping process. In this project, I decided to use iterative sprints. In total, I'd create three versions and eventually work on the MVP.
In the first low fidelity prototype, I focused on creating the general layout of the web application in terms to user flow. The main focus was on generating a basis to scope out clutter. I made a design for each page and had a validation session with two team leaders. We went through each page and located pain points and brainstormed alternative ways to design certain elements like the schedule page.
First version - Client overview page
First version - Adding a new project page
In the second version of low fidelity prototype, I focused on creating components and for more reference source.
Through Card sorting and adding new components I was able to explore and communicate with the client to create better navigation and information architecture.
The additional goal was to add interaction in the prototype through Adobe XD.
Second Version - Time Tracking schedule
Second Version - Client Overview