Overview
Design Process
Background
Ramp worker fatigue is a growing safety risk.
Who’s Ramp Workers?
Problem Discovery
Why Do Ramp Workers Experience Fatigue?
What Systems Exist at the Safety Team and Manager Levels?
Key challenges at the organizational level:
No Fatigue Data
Complicated Injury Reporting
Lack of prevention strategies
Reframing Problem
Fatigue is a symptom of deeper root causes.
The Real Problem Lies in a Broken System Where Each Stakeholder Faces Unique Challenges at Different Levels.
Prototype
Wireframe
Iteration
Usability Testing
Key insights included:
Users felt uncertain when it wasn’t clear which data was AI-generated versus real.
Non-role-specific information overwhelmed users.
Users struggled to interpret the data and understand what actions to take.
They expected the interface to prioritize information by relevance and usage frequency.
Users feel overwhelmed by too much information
The example below shows one of several iterations we refined over time:
v1.0: All data visible, no clear hierarchy, required swiping through team members
v2.0: Click-to-expand list of members with individualized views
v2.1: Added filters, a team-wide status overview, and simplified charts
v2.2: Final version presented data in digestible sections, improving clarity and ease of use
Ramp Worker
USECASE #1
Final Design

Manager Cale receives a report from the Peer Robot regarding Bob’s fatigue and injury. Cale needs to assess Bob’s condition and determine how to adjust the work schedule accordingly to support him.
Manager
USECASE #2
Manager
USECASE #2
Safety Team
USECASE #3
Reflection
How and When AI Should Step In



