Senior Product Designer | Enterprise SaaS
LG Display vessel tracking
Operators required 6+ steps to detect shipment issues
Founding Product Designer · FNS · Q4 2024 – Q3 2025
FNS is a logistics platform used by operators at LG Display to monitor global shipments — tracking goods from South Korean factories to US retail warehouses. Operators work under tight timelines. The problem: detecting a single issue required 6+ manual steps across fragmented GIS panels — in a workflow where minutes matter.
PROJECT OVERVIEW
Platform & Timeframe
Web application
Q4 2024 - Q3 2025
Company & Client
FNS (Enterprise logistics platform based in Los Angeles)
Client:
LG Display
Shipment flow:
LG Display → Best Buy retail distribution
Impact
Defined the initial product direction and established the operational model for monitoring workflows across teams.
From Origin to Destination: Vessel History and Tracking Details
THE OVERVIEW
Operators monitored global shipments using live tracking tools. Signals were buried across multiple panels.
The live tracking map (GIS) was FNS's primary interface — featured in every demo. I ran recorded operator screen shares showing operators spent 70% of their time navigating, not deciding. I reframed the question from 'should we remove the map?' to 'how do we make it available without requiring operators to start there?' — which shifted it from a product identity debate to a workflow optimization discussion.
BEFORE AND AFTER (OPTIMIZING PROCESS)
From fragmented workflows → real-time signal monitoring
I restructured the experience from a map centered investigation workflow into a signal first monitoring model so operators could identify issues faster and act with less manual analysis.
Before: 01 Fragmented investigation workflow
Shipment data was scattered across multiple views and panels
Before: 02 Low signal visibility
Critical issues were buried inside geographic context, making them difficult to detect quickly
Before: 03 Delayed operational response
Operators spent time reconstructing status instead of responding to issues immediately
After: 01 Unified shipment monitoring workspace
Signals were centralized into one interface
After: 02 Signal-first visibility
Critical issues were surfaced and prioritized
After: 03 Faster operational investigation
Operators could act without reconstructing context
THE PROBLEM
This forced operators to reconstruct context manually,
delaying issue detection.
This resulted in:
- High cognitive load
- Delayed issue detection
- Inconsistent operational responses
BUSINESS ISSUES
Fragmented GIS tools created slow and inconsistent monitoring workflows.
USER ISSUES
Operators could not quickly identify critical shipment signals.
KEY UX INSIGHT
The system was optimized for geographic representation, not operational decision-making.
This required redefining shipment monitoring from map navigation to signal driven decision making. Demoting the GIS map required aligning the head of operations and engineering lead. I reframed it from a product identity question to a workflow efficiency decision.
This created a mismatch between:
- System structure (map-centric)
- User goal (signal detection and action)
01.Critical signals were not directly accessible
Important shipment issues were buried inside fragmented map based views.
02.Operators had to reconstruct context manually
Multiple panels required manual synthesis to understand status.
03.Decision-making was delayed across workflows
Operators spent time navigating instead of acting.
DESIGN HYPOTHESIS
The problem was not visibility,
but how signals were structured and surfaced.
Instead of requiring operators to search through maps, the system should prioritize critical signals first so users can identify issues and act immediately.
DESIGN TRADE OFF
Trade-off: Geographic context vs decision speed
I explored whether the interface should preserve map prominence or prioritize operational speed. Keeping the map as the primary surface preserved geographic context, but it continued to obscure critical signals and slowed issue detection. I chose a signal first layout because operators needed to identify status changes and act quickly, with the map serving as secondary supporting context.
Option A: Map-centered layout
Preserved geographic context, but obscured critical signals and slowed decision-making.
Decision:
Rejected because visibility and action speed mattered more than map prominence in this workflow.
Option B (Chosen): Signal-first layout
Prioritized critical signals, enabling faster issue detection and decision-making.
Why this worked
- Improved discoverability of urgent signals
- Reduced scanning across multiple surfaces
- Supported faster operational response
Trade off
The map became supporting context rather than the primary interface
FINAL APPROVAL
A signal-first monitoring workflow for real-time decision-making
This established a consistent decision model operators could use across shipment workflows. The final design operationalized the signal-first approach into a production-ready monitoring workflow. Instead of navigating across fragmented GIS views, the redesign shifted the system from a map-driven exploration model to a signal-driven decision system, enabling operators to detect and respond to issues without manual context reconstruction.
Critical shipment signals surfaced directly in the listinstead of being hidden inside map interactions
EDGE CASES
Operators can continue decision-making even when data is missing or partially available.
Edge Case: No Data Found
Edge Case: Revised Shipment Details
IMPACT & RESULT
Enabled real-time decision-making by restructuring how signals are surfaced
Restructuring how signals are surfaced transformed operational workflows and improved decision-making at scale. This reduced reliance on individual operator expertise and made the system more scalable across different teams and use cases.
6 →2
REDUCED INVESTIGATION STEPS FROM 6→2
50%
IMPROVED ISSUE DETECTION SPEED BY 50%
55%
REDUCED OPERATIONAL WORKLOAD BY 55%
Operators no longer needed to navigate across multiple GIS views, reducing investigation effort and enabling faster issue resolution.
Critical signals were surfaced immediately, allowing operators to detect and respond to issues without manual exploration.
By centralizing signals into a unified workflow, redundant steps were eliminated, improving operational efficiency across teams.