ERP4SD

Project Overview

Loginet Systems used an outdated internal portal for controlling absences and time tracking, which was inconvenient for both employees and managers. Due to its limitations, they had to run two systems in parallel: employees tracked time in JIRA, and logs were transferred to the internal portal for review.

To address complaints about the dual interfaces, it was suggested to consolidate time logging and editing in one place, preferably outside of JIRA.

My Role

I worked as the sole UX/UI designer on the project, which gave me a major role in UI design. My tasks included establishing the visual identity and contributing to the creation of a design system.

competitor analysis

stakeholder interview

user interview

ux design

ui design

desing system

Research

Desk Research & Interviews

The primary objective of the research phase was to map out the best practices in time logging design, so I spent an extended period testing software solutions that offer such features. This was followed by 12 interviews with PMs and developers to identify pain points and preferences.

It turned out that many people liked some unique elements of the current structure (calendar tiles in the monthly view, use of colors), so we decided to keep them.

Designs

Calendar View

When designing the calendar view, we aimed to create a visually cleaner and more streamlined interface. There was a request to retain the color-coded markings, and additionally, a new important requirement emerged for the separation and administration of different overtime categories.

Before

The existing portal clearly had much room for improvement.

After

I wanted to make the calendar view more streamlined and less noisy. The color codes marking overtimes (purple) or less-than-required hours (red) now appear in the text color instead of being the colors of the tiles.

New functions, such as time tracking and different data representation modes, are already available on the site.

Time Log cards

Designing the time log cards was an exciting task, and their evolution can be seen in the examples below. Here, we needed to differentiate between work surplus/shortage, overtime, and paid overtime, with the latter also having different approval statuses. We conducted A/B tests on each version and continued to develop based on the results. We marked vacations and rest days with cute animal characters that match the season, adding a mood element.

The evolution of time log cards

Creating a time log

Projects page

There was no feature expansion for the controlling pages, but the complexity of this task lay in the fact that, from a data visualization perspective, the redesign was not just a facelift, but also involved rethinking the way data is represented (dashboards, charts, tab and modal systems, etc.) based on the PMs' guidance. This required a lot of research and consultation, as a deep understanding of the system was necessary to ensure that the visualization truly provided assistance.

Projects Page / Overview tab

Dashboard / Projects tab

Mobile screens

Since I have left the company I cannot share more details about how the project has evolved from this point.

Conclusions

Since I was given more freedom and greater responsibility, the project presents a very good development opportunity from a UI design perspective. It was also exciting to delve into data visualization and to become acquainted with such a complex system.

Thank you for your attention!

Want to see more?

Learn how I implement design thinking methodologies in my hobbies to create memorable experiences.

Personal projects

Back to Home