Back to work

A desktop application for Ukrainian railway specialists to analyse track geometry and produce technical reports.

RGMS helps railway specialists find deviations from the standards, review the related measurements and generate technical reports. I was responsible for the UX of the core workspace and the report-generation flow, in a cross-functional team.

Launchedin use by railway analysts

Task
Design the track analysis workspace and end-to-end reporting experience
Client
Ukrzaliznytsia (Ukrainian Railways)
Context

The problem

Analysts do not read a graph alone. They compare the track geometry graph with the table of deviations found on it and with the measurement summaries, and they have to interpret all of it together before they can prepare a report. On a desktop screen that is a lot of dense information.

Stage 1

Solutions

1

The graph and the table are one thing

Need
Analysts read a graph together with the table of its deviations.
Decision
Selecting a deviation in the table highlights the corresponding place on the graph, and selecting a place on the graph highlights it in the table.
Why
The analyst does not have to find the same spot twice.
2

Information about the section stays in view

Requirement
The business analysts originally asked for the information about the file, graph and section to open on a button.
My proposal
A panel above the table that is always visible.
Why
The analyst always sees what they are working with, without taking an extra action.
Outcome
The business analysts fully accepted the proposal, and it was implemented.
The panel with the information about the file, graph and section, above the table
3

Commands on a toolbar, not in a menu

Need
The menu bar was overloaded, and many of its items were rarely used.
Decision
I removed it and placed the commands on the toolbar.
Why
Analysts do not have to search through menus for them.
4

Tabs for open files

Need
Analysts often work with several files at once, and each open file corresponds to one track graph.
Decision
Tabs, one per open file.
Why
They switch between files in one workspace rather than managing separate windows.
Tabs, one per open file
5

One form for report configuration, not a wizard

Options
A multi-step wizard shows fewer options at a time but adds navigation. A single form keeps related parameters together and makes them easier to review or change, but it can feel dense.
Decision
One form with grouped parameters. The main settings stay visible, and less frequently used options are available on demand.
Cost
Density, which the grouping is there to manage.
6

A report flow that accounts for what can go wrong

Flow
From selecting a report type, through configuring parameters and generating the report, to previewing it and opening or downloading the result.
Cases
Unavailable report types and permission restrictions; empty states; progress with the option to cancel; timeouts and server errors; starting another report or returning to the report list. These states are part of the launched product.
Process
I used Claude as a thinking partner to look for states I might have missed. I evaluated its suggestions and made the final decisions.
Stage 2

Testing

I tested an interactive prototype, an earlier version than the screens shown here, with seven participants. They completed three tasks involving track graphs and report export, and all seven completed them with the prototype.

After testing I adjusted the tables on the right. Fields in the report-creation form were added because analysts required them.

Stage 3

Outcomes

Livelaunched and used by railway analysts
7participants in the usability test
3tasks with track graphs and report export, completed by all seven