Reshaping Cargohandling for40,000+ employees

Solution in 15 steps

Migrating the Cargo Details feature in SALOG to a web-based version will address these issues by providing a more accessible, user-friendly, and scalable solution, ensuring better performance and future-proofing the application.

1. Participant Selection in Collaboration with Program Manager

To ensure relevant and diverse user insights, participants for the research were carefully identified and selected in close collaboration with the Program Manager. This step involved analyzing user roles, frequency of platform usage, and familiarity with the Cargo Details feature to recruit individuals who could provide meaningful feedback and represent the broader user base effectively.

2. Interview Scheduling and Participant Coordination

Once participants were finalized, interviews were systematically scheduled based on their availability to ensure maximum participation. Calendar invites, including meeting details and context for the discussion, were sent out in advance to prepare participants and streamline the coordination process across different time zones and departments.

3. Conducting and Recording Interviews via MS Teams and stored in Dovetail

User interviews were conducted through Microsoft Teams to facilitate seamless remote communication. Each session was recorded—with participants' consent—to ensure that no insights were missed during analysis. This allowed the team to revisit conversations for deeper understanding and accurate synthesis of qualitative data.

4. Survey Distribution for Chinese User Group

To accommodate our one of the most important markets - China, a tailored survey was distributed to Chinese users via Microsoft Forms. This approach ensured inclusivity and allowed users to share their feedback conveniently and in a format suited to their context, helping us gather structured quantitative input from a key user segment.

5. Adoption of a Mixed Methods Research Approach

A mixed methods approach was employed, combining both qualitative and quantitative research techniques to gain a comprehensive understanding of user needs and behaviors. Qualitative insights were gathered through in-depth interviews, while quantitative data was collected via surveys. This dual approach ensured a balanced perspective—capturing user sentiment, uncovering pain points, and validating patterns with measurable data.

6. Data Analysis Using Thematic and Descriptive Methods

Insights from user interviews were analyzed using thematic analysis to identify recurring patterns, needs, and pain points across different user roles. In parallel, survey responses were examined using descriptive statistics to quantify trends and preferences. Together, these methods provided a well-rounded understanding of user behavior, supporting data-driven design decisions.

7. Sharing Insights with Key Stakeholders

The synthesized insights from both qualitative and quantitative research were compiled and presented to cross-functional stakeholders—including the design team, Program Managers, and system architects. This step ensured alignment across teams, enabling informed decision-making and prioritization of features based on real user needs and pain points.

8. Design Decision: Separate Development of Tree Structure Navigation

A key design decision was made to develop the tree structure—intended to serve as the primary navigation element—separately from the rest of the interface. While the tree structure was under development, placeholder components were incorporated into other screens to maintain continuity and context. This approach allowed the team to parallelize efforts, enabling focused discussions and efficient progress on both the navigation system and the main content layouts.

9. Iterative UI Design and Collaboration Using Figma and Jira

The user interface was meticulously crafted in Figma through multiple design iterations, incorporating continuous feedback from UX peers to refine usability and visual appeal. Each design update was tracked and managed via Jira tickets, ensuring clear communication, organized task management, and efficient collaboration across the design and development teams.

10. Completion of Overall Flow and Migration-Ready Layouts

The complete user flow, including the newly designed tree structure navigation and all associated screen layouts, has been finalized and prepared for migration. This milestone marks a cohesive and well-integrated design framework, ready to be implemented in the web-based version, ensuring a smooth transition from the legacy Swing interface.

11. Creation of an Interactive Prototype in Figma

The finalized designs were transformed into an interactive prototype within Figma, enabling stakeholders and users to experience the planned workflows and interface behavior firsthand. This prototype served as a valuable tool for validating design decisions, facilitating usability testing, and gathering early feedback before development commenced.

12. Usability Testing with Original Interview Participants

The interactive prototype was presented to the same users who participated in the initial interviews, allowing for targeted usability testing. Engaging these familiar users helped validate the design improvements and ensured the solution effectively addressed their needs and pain points, while maintaining continuity in feedback throughout the process.

15. Feature Tracking and Ongoing Usage Monitoring via Matomo

After deployment, tracking mechanisms were enabled for the Cargo Details feature to monitor how users interact with it in real time. This continuous monitoring ensures the feature is being used as intended, helps identify any usability issues, and provides valuable data to inform future enhancements and optimizations.