MOL Group: enterprise UX design for internal tools

MOL Group's operational teams do their daily work in internal applications for gas trading, maintenance and pipeline logistics. Before the redesign, much of this ran on SAP screens and on legacy forms in older Windows applications.

The goal, in our words, was one consistent user experience across the group's internal tools.

Our role: design for the apps, code by the development partner

We worked with the software company that builds MOL Group's internal applications. They wrote the code. We owned the design: the UX and UI of the B2B and back-office apps across almost all of their MOL Group projects, over three years.

We also built a shared design system and used it across the apps. Each app kept its own character, while the patterns, components and behaviour carry over from one to the next.

The applications we designed

• Gas Trader Platform: contract and point of delivery (POD) data for the energy trading division, with tabbed views and inline editing for high-volume entry.

• E-Worklog: time and task logging for maintenance and operations teams, with work orders, role-based views and task confirmation, in Hungarian and English.

• LOGIR: pipeline logistics, where deliveries are recorded with product specs, flow meter values, density and temperature, then confirmed at handover and takeover.

• SAP dashboard: role-based views for traders, admins and analysts, with editable forms and approval workflows inside the SAP environment.

Three decisions that shaped the work

One design system, with room for each app

A single design system runs through the apps, but we did not force them to look identical. A gas trading form and a maintenance work order solve different problems, so each app departs from the system where its work needs it. The trade-off is a system that takes more care to maintain than one rigid template.

Inline editing for high-volume data

Traders in the Gas Trader Platform enter and correct a lot of delivery point data. They edit fields in place, with validation as they go, instead of opening a separate form for every change.

Confirmation on both sides of a delivery

In LOGIR a pipeline delivery is confirmed twice: once by the side handing it over and once by the side taking it over. Both parties sign off on the same record, so it is clear who confirmed what.

Tens of thousands of people work with the platforms we designed.