top of page

ELM

A web-based application that simplifies corporate license and version management

Image by mymind
MacBook Pro 14.png

Summary

In the corporate license management application, I redesigned filtering, file upload, and dashboard flows. By refining button states, tooltip usage, and grid layouts, I improved overall usability. In particular, I simplified the filtering screen, enabling users to access data much faster.

Project Type

Web Tabanlı Elektronik Lisans Yönetimi Uygulaması

Role

UX / UI Designer @Ekinoks Software

Timeline

2024 March

UI Design· Usability Analysis

Where did I start from?

When I joined the ELM project, the application already performed its core functions: users could upload licenses, manage modules, and track versions. However, several critical issues remained:

  • Too much information was displayed at once.

  • User flows were not intuitive.

  • Buttons were always active, which caused confusion.

  • The filtering screen was particularly inefficient.

My goal was to transform this powerful but complex system into something simpler, more consistent, and user-friendly.

As a first step, I carefully reviewed the existing screens

  • Save buttons were always active — users could click “save” even without making any changes.

  • Chips and buttons took up too much space on smaller screens.

  • Dashboard cards were misaligned, breaking visual consistency.

  • The filtering area covered the entire screen, preventing users from reaching quick solutions.

Moving into the solution phase, the first step was to define clear priorities

Since my manager asked me to deliver updates quickly, my priority was to identify changes that developers could implement easily. To do this, I annotated the screens to highlight both the areas that could be adjusted rapidly and the critical sections that required a full redesign.

Notes & Quick Improvements

While reviewing the existing screens, I created visual notes directly on the UI to highlight issues and quick wins for developers. This helped the team see problems in context and apply changes faster. Some examples of my notes:

  • Save buttons should only be active when a change is made, to prevent confusion.

  • Status chips needed reduced padding for better responsiveness on smaller screens.

  • Tooltips were introduced to replace long static texts, making the interface cleaner.

  • Card components were aligned within a proper grid to ensure visual consistency.

By annotating directly on the designs, I bridged communication between design and development, speeding up iteration cycles and making sure improvements were both practical and impactful.

Redesign

In some areas, simply leaving notes wasn’t enough; I had to completely redesign the flows and layouts.

Filtering: I simplified the filtering screen so users could access data faster without being overwhelmed.

Dashboard: I restructured the card layout and alignment to create a cleaner, more consistent visual hierarchy.

Version Management: I redesigned the update process to reduce confusion and make actions more intuitive.

These redesigns balanced quick wins for developers with long-term usability improvements for end users.

Filtering

Filtering was the area I focused on most in the ELM project. With hundreds of users, modules, and versions in the system, searching was a critical function.

In its original state, the filters were scattered and confusing. Users struggled to understand which criteria to select.

My solution was to:

  • Highlight the most frequently used filters

  • Place detailed filters inside an accordion

  • Make the “Clear Filters” and “Apply” buttons visible

Result: Users can now reach the data they need much faster. This small change made a big difference in the daily use of the application.

Version Management

Version management in ELM was a critical process for ensuring system reliability. In the old design, the distinctions between Current / Past / Draft versions and the related action buttons were scattered; users often struggled to understand what stage they were in.
My solution was to make the process more visible and controlled:

  • Displayed version information as clear cards

  • Made the Save button active only when changes were made

  • Added warnings for missing modules

Result: Users are now guided step by step when moving from a draft to a current release. The publishing process has become a safer and more transparent flow.

Outcome

With the improvements I implemented:

  • User flows became clearer and more intuitive.

  • The interface looked more organized and professional.

  • The filtering process became faster, helping users reach data much more easily.

  • Thanks to the clear, visual notes I provided, the development team was able to implement changes quickly.

Learnings

This project showed me how even small details — like inactive states, tooltips, or alignment — can make a big difference in user experience. I also realized once again that simplicity and guidance are the most critical aspects of admin panels. Finally, I learned how providing developers with clear, visually supported feedback can significantly accelerate the implementation process.

bottom of page