This user type is involved in high-level locomotive issues and in diagnosing the same by working with individual shops.
He is involved with making decisions for locomotive maintenance, creating reports, and providing support to mechanical crews (MOC) as needed.​
Certain pieces of information are redacted for confidentiality purposes
Information
It's definitely important to have it. However, it makes the most sense when you have the ability to draw insights by creating helpful assets.
UX Research
The process
Feedback
Working with users to get feedback on existing applications and V.1 release of the new applications to provide insights to business stakeholders for improvements.
​
Personas
Interviewing users, understanding their pain points, and creating detailed personas. The personas have critical information that will provide context about the user profile, roles and responsibilities, and the type of applications being used.
​
Journey map
Laying out the entire process and workflow of features. Create callouts and understand how to highlight the data points with key opportunities.
​
Interviews
Interviewing users and understanding their workflow. Narrowing down their pain points and taking in their feedback.
​
Persona
1. Systems Operations Center (SOC) user
2. Reliability user
Persona
This user type is with the reliability team
which is involved with supporting the Mechanical Operations Center (MOC)
His duties involve assessing locomotives that consistently break down and diagnosing second offenders, i.e., troubled locomotives.
3. User type: Live view
Persona
4. Feedback and training
As a part of the project, I also had to assist with training users to use and deploy our new suite of applications. It gave me the chance to collect valuable feedback and user insights.
The user type is a high-level shop supervisor​
He's in charge of addressing locomotive maintenance issues in his shop and also plans the workflow for his shop.
He uses a feature known as live view, which gives him access to a high-level view of locomotives present in other shops.
Parting thoughts
A reasonable conclusion of why these assets make sense.
01
While this process is an ongoing effort, the discovery process has helped us understand and narrow down on important data points needed to create a strong suite of applications​
02
Most stakeholders other than product owners are unfamiliar with locomotive maintenance and the range of applications, functions, and data that are involved; the discovery process provides a whole lot of insight into the same and highlights the existing synergy ​
03
The journey maps provide a visual aid of all functions being performed and helpful indicators of where the experience is lacking and needs improvement.​
04
Personas are helpful in providing context and understanding the users better and what applications are crucial for their functions ​
05
Overall, the discovery efforts were widely appreciated and supported by the clients, as they provided new insights and gave opportunities to experience the difference provided by design-led thinking.
​
​
Discovery
What this case study is all about
01
As mentioned, I worked alongside a team of designers, SAP specialists, developers, and others to create and enhance applications for simplified locomotive maintenance operations​
02
The client on this project worked using a Dual-Track agile process of Discovery and Delivery​
03
The goal was to do all of the discovery out front (Research, Interviews, CJMs, Low-Fidelity Designs, Information Architecture, and User Testing) and get buy-in from all of the critical stakeholders before transitioning the work to the Delivery Process.
04
Once in the delivery process, we would further refine the agreed-upon flow and designs from the discovery track to patch holes and expand on missing details​
05
This process was done by working closely with the lead UI and backend developers to ensure what was created was feasible in an SAP-backed environment​
06
The outcome was a clear vision for the product before it ever reached the hands of the development team, and that work could be queued up in the backlog and picked up with minimal churn at a designated time