AI/ML Logistics Management Platform

AI/ML Logistics Management Platform

UX/UI Designer & Product Owner

UX/UI Designer & Product Owner

NOTE: The data in this case study has been obfuscated due to confidentiality requirements

NOTE: The data in this case study has been obfuscated due to confidentiality requirements

KEY ACCOMPLISHMENTS

KEY ACCOMPLISHMENTS

Designed a multi-platform predictive AI/ML analytics solution in close partnership with a cross-functional scrum team of over 15 engineers, shaping product direction and aligning design strategy with technical implementation.

Led user interviews and collaborative discovery workshops to surface workflow needs and gain consensus among PMs and executive stakeholders, ensuring the product vision was grounded in real operational insight.

Delivered fully custom, high-fidelity designs for logistics management flows and graph visualization experiences, guiding iterative design reviews to refine usability, clarity, and interaction quality across the platform.

The APPROACH: Problem Solving for a Complex Process

The APPROACH: Problem Solving for a Complex Process

Define the Problem

Contextual Research

Design the Solution

Define the Problem

Contextual Research

Design the Solution

DeFINE THE PROBLEM

DeFINE THE PROBLEM

The client was facing a dilemma of lack of data connectivity in a complex operational environment that involved multiple stakeholders and data owners that needed to be able to communicate and effectively transmit necessary data elements to one another in a secure environment.

building trust and focusing on the problems to solve

I facilitated cross-organizational workshops to define the problem space, map the data landscape, and identify requirements. The goal was also to build trust with these stakeholders who both owned the relevant data sources and housed the potential future users of the product. It was crucial to guide the multiple stakeholders with varying interests towards the same priorities. In this process, we also gained an understanding of how information flowed and where silos were hindering communication efficiency.

DOCUMENTing A SINGLE SOURCE OF TRUTH

For most projects, I believe in documenting a single source of truth for the existing state for everyone on the project to reference as we move forward with design, development, and continual client engagement. It is critically important for keeping everyone aligned on the ”WHAT” and the “WHY” of a project.

KEY INSIGHTS: Problems to solve

Data sits in disparate siloes and all coordination between stakeholders happens over email.

When customers request information, there are too many steps involved in reaching out to various parties for the relevant data.

Customers do not have proper estimates for delivery.

Stakeholders cannot easily track the responsible party when mistakes are made.

Contextual Research

To dig in deeper, I spent time physically sitting with users to better understand their mental states while engaging with the current process and document their workflows in-context to better validate our assumptions about the business problems.

Design exercise

Rather than creating user personas defined by demographic or static attributes, I sought to apply a more dynamic framework. This approach allows you to think of a user’s attitudes and behaviors over time through 2 key lenses:

MINDSET: This lens captures traits such as attitudes about technology, attitudes about their roles and responsibilities, level of experience, or working styles.

MODE: This lens more dynamic and can shift over time. Rather than a static trait, it refers to the user's current desire or task at hand.

KEY INSIGHTS: User stories

As a user, I need the ability to view complex data from multiple sources chronologically and clearly see gaps in the process in order to take remediation steps.

As a user, I need the ability to understand the chain of logistics and responsibility for the package at each step during and after the process completes.

As a user, I need to view detailed information for each event in the process so that I can easily draft reports or emails to my counterparts.

As a user, I need the ability to view complex data from multiple sources in a relational context so I can understand how events are related.

Contextual Research

To dig in deeper, I spent time physically sitting with users to better understand their mental states while engaging with the current process and document their workflows in-context to better validate our assumptions about the business problems.

Design exercise

Rather than creating user personas defined by demographic or static attributes, I sought to apply a more dynamic framework. This approach allows you to think of a user’s attitudes and behaviors over time through 2 key lenses:

MINDSET: This lens captures traits such as attitudes about technology, attitudes about their roles and responsibilities, level of experience, or working styles.

MODE: This lens more dynamic and can shift over time. Rather than a static trait, it refers to the user's current desire or task at hand.

KEY INSIGHTS: User stories

As a user, I need the ability to view complex data from multiple sources chronologically and clearly see gaps in the process in order to take remediation steps.

As a user, I need the ability to understand the chain of logistics and responsibility for the package at each step during and after the process completes.

As a user, I need to view detailed information for each event in the process so that I can easily draft reports or emails to my counterparts.

As a user, I need the ability to view complex data from multiple sources in a relational context so I can understand how events are related.

Contextual Research

To dig in deeper, I spent time physically sitting with users to better understand their mental states while engaging with the current process and document their workflows in-context to better validate our assumptions about the business problems.

Design exercise

Rather than creating user personas defined by demographic or static attributes, I sought to apply a more dynamic framework. This approach allows you to think of a user’s attitudes and behaviors over time through 2 key lenses:

MINDSET: This lens captures traits such as attitudes about technology, attitudes about their roles and responsibilities, level of experience, or working styles.

MODE: This lens more dynamic and can shift over time. Rather than a static trait, it refers to the user's current desire or task at hand.

KEY INSIGHTS: User stories

As a user, I need the ability to view complex data from multiple sources chronologically and clearly see gaps in the process in order to take remediation steps.

As a user, I need the ability to understand the chain of logistics and responsibility for the package at each step during and after the process completes.

As a user, I need to view detailed information for each event in the process so that I can easily draft reports or emails to my counterparts.

As a user, I need the ability to view complex data from multiple sources in a relational context so I can understand how events are related.

Designing an informed solution

Designing an informed solution

DESIGN DECISIONS

Application of color to indicate data source and stakeholder responsibility.

Visual emphasis on duration of time rather than date.

Each process can expand to allow the user to explore and investigate each step.

Only one process can expand at a time to prevent information overload.

UX OUTCOME

User can easily visualize package hand offs, delineate responsibility between stakeholders, and explore each node progressively while still understanding the context of the overall process.

DESIGN DECISIONS

Consistent color designations carried over from timeline view.

Labeled nodes and relationships to provide more context.

Information panels are consistent across the visualizations for each event node.

Predictive information for in progress events is clearly displayed in panel.

UX OUTCOME

User can easily visualize relationships between events, delineate responsibility between stakeholders, and explore each node progressively while still understanding the relational context of the data.

Key Outcomes

Key Outcomes

Centralized Data Repository and Interface

End users are now able to view data from other systems without needing to coordinate over email and can more accurately predict the duration of future parts of the process when that information is requested.

Improved Metrics Reporting for Stakeholders

Executive stakeholders can now easily monitor compliance metrics around processing time and better understand where bottlenecks occur to make organizational improvements.

High User Adoption Rates in Partner Organizations

Single platform with data integrated from 3 different organizations has now been adopted across all stakeholder organizations with over 3,500 monthly active users.

Improved Metrics Reporting for Stakeholders

Executive stakeholders can now easily monitor compliance metrics around processing time and better understand where bottlenecks occur to make organizational improvements.

High User Adoption Rates in Partner Organizations

Single platform with data integrated from 3 different organizations has now been adopted across all stakeholder organizations with over 3,500 monthly active users.

Centralized Data Repository and Interface

End users are now able to view data from other systems without needing to coordinate over email and can more accurately predict the duration of future parts of the process when that information is requested.

Improved Metrics Reporting for Stakeholders

Executive stakeholders can now easily monitor compliance metrics around processing time and better understand where bottlenecks occur to make organizational improvements.

High User Adoption Rates in Partner Organizations

Single platform with data integrated from 3 different organizations has now been adopted across all stakeholder organizations with over 3,500 monthly active users.

location

Washington, DC or remote

Contact details

bellajones.uxdesign@gmail.com

678-480-1766

location

Washington, DC or remote

Contact details

bellajones.uxdesign@gmail.com

678-480-1766

location

Washington, DC or remote

Contact details

bellajones.uxdesign@gmail.com

678-480-1766