GOAL
EDP Drive already existed but the UX and UI were rudimentary. Therefore, EDP employees tended to bypass the platform. We were challenged to make sure both UX and UI become a priority, as well as to think strategically about which functional and journey features should be implemented. After analysing the inputs from several users and stakeholders, we sketched, prototyped, tested and iterated towards the most effective solutions.
EDP Drive already existed but the UX and UI were rudimentary. Therefore, EDP employees tended to bypass the platform. We were challenged to make sure both UX and UI become a priority, as well as to think strategically about which functional and journey features should be implemented. After analysing the inputs from several users and stakeholders, we sketched, prototyped, tested and iterated towards the most effective solutions.
Improved dashboard
The new version of the homepage helps users to keep track of incoming requests and next tasks. It’s organised in tabs, which are shown to users according to their different profiles.
The new version of the homepage helps users to keep track of incoming requests and next tasks. It’s organised in tabs, which are shown to users according to their different profiles.
Full project pages
This page format helps users to have full visibility over the status of each project. Staff can upload the deliveries and change the status of their tasks. On the other hand, leaders can create tasks, close the project and evaluate the client.
This page format helps users to have full visibility over the status of each project. Staff can upload the deliveries and change the status of their tasks. On the other hand, leaders can create tasks, close the project and evaluate the client.
Carefully selected mobile features
Although being an internal tool, used mainly on desktop, certain features were widely used on mobile as well. Based on the JTBD framework, we’ve identified those features and assembled the mobile version of the platform based on the collected insights.
Although being an internal tool, used mainly on desktop, certain features were widely used on mobile as well. Based on the JTBD framework, we’ve identified those features and assembled the mobile version of the platform based on the collected insights.
A custom Design System
To ensure consistency, agility and independence from our team when the client looks to scale and add functionalities to the platform, we’ve created a Design System. This one is currently used not only by developers and designers but also by other stakeholders.
To ensure consistency, agility and independence from our team when the client looks to scale and add functionalities to the platform, we’ve created a Design System. This one is currently used not only by developers and designers but also by other stakeholders.
