There were some limitations to the project in regards to users who could talk to the Design team. Because they were always occupied at the operation, we ended up doing group interviews to make better use of everyone's schedules.
We interviewed 21 UNILOG users, in groups, over the course of two weeks. We used semi-structured interviews and users also shared their screen to walk us through their process in the system. Here are some of what we learned from the sessions:
  1. The user experience of the train formation in the system is very complex: each page has a code and the user must learn the codes to be able to form the train.
  1. The processes are too manual: they need to do so much manual work, it is extremely time-consuming.
  1. There's no system feedback or alerts in case of errors.
  1. Important information, which could assist the user in their job, is missing from the system: they need to consult other sources.
  1. System integrations don't work: the different systems don't integrate well and there's a lot of extra work because of that.
  1. Users consider that manual processes can lead to errors and losses in the operation.
 

User feedback from the focus groups

"When you need to remember the codes for each step, you get a mental block and when a problem arises, you just don't know what to do".
"When the system goes down, the railway practically stops, because we depend on the system 24/7".
"If the field operation passed along wrong data, the train will transit with wrong information. But the system should be able to alert or correct errors.”
"If any information is filled out wrong, it can cause accidents or loss."
 

Insights and opportunities from the focus groups

  • Optimizing processes through automation
  • Integrating with the other VLI systems and other railroads
  • Centralization of content in the system
  • Reviewed flows and information to be filled in the system
  • System rules must be on the platform itself
  • System feedback
  • Unified use flow
 
badge