B2B SaaS

2026

5min to <1min: Democratising Logistics Data for Non-Technical Teams

The app suffered from raw database that forced users to scan thousands of technical rows to find a single vehicle. This complexity locked out field teams, making them dependent on IT to answer: "Where is my cargo?"

I led the UX audit and redesign of the Tracking App, pivoting the product from "row management" to "mission monitoring." By abstracting complex data structures to pass the "Grandma Test," I empowered non-technical users to triage assets instantly—reducing asset location time from five minutes to under ten seconds.

Role

Lead Product Designer

Team

2x GIS Technicians

1x Data Analytics

2x Designers

2x Engineers

Impact

1. 5 Minutes → 10 Seconds (Operational Velocity)

Zero-Training Adoption (Usability ROI)

100% Visibility Restoration (Risk Mitigation)

Role

Lead Product Designer

Team

2x GIS Technicians

1x Data Analytics

2x Designers

2x Engineers

Impact

1. 5 Minutes → 10 Seconds (Operational Velocity)

Zero-Training Adoption (Usability ROI)

100% Visibility Restoration (Risk Mitigation)

Problem area

UX Problem: Stakeholder Rejection & the "Grandma Test"

A stakeholder audit revealed the legacy UI was operationally unusable, leading the Director of Units to reject it for its lack of clarity. This failure defined our mandate: the "Grandma Test", transforming a complex database view into an interface where non-technical users can monitor assets and verify arrivals instantly.

The "Grandma" Barrier

The technician-centric interface forced commanders to scan raw data tables, locking them out of the real-time operational loop.

The "Grandma" Barrier

The technician-centric interface forced commanders to scan raw data tables, locking them out of the real-time operational loop.

Fragmented Data

Assets appeared as disconnected database rows without "Trip" or "Convoy" context, making it impossible to visualize journeys or confirm arrivals.

Fragmented Data

Assets appeared as disconnected database rows without "Trip" or "Convoy" context, making it impossible to visualize journeys or confirm arrivals.

Critical Alert Blindness

The system failed to distinguish between minor connection drops and life-threatening emergencies, making it impossible for users to identify and prioritize real crises.

Critical Alert Blindness

The system failed to distinguish between minor connection drops and life-threatening emergencies, making it impossible for users to identify and prioritize real crises.

Design decision 01

Domain Separation (Viewer vs. Operation)

To solve the "Excel Effect," I decoupled the live operations from data administration. I moved technical tables to a dedicated "Management View" and introduced "Live Trips," prioritizing instant situational awareness for commanders while preserving raw data access for IT staff.

01

The "Live" View

I created a dedicated "Live Trips" interface where users monitor active trips and statuses, allowing them to click into specific trips for details.

02

The "Macro" View

I introduced a High-Level Dashboard to provide immediate insight into fleet health; for viewer to get a brief understanding of any critical situations.

Before & After: From static tables to live trips accordions
The "Macro" view Dashboard

Design decision 02

Operational Intelligence (Solving Alert Blindness)

To fix the "False No Location" crisis, I replaced generic red error codes with Human-Readable Statuses. I implemented a strict semantic system.

IN TRANSIT

(Blue): Informative, live updates.

AT ORIGIN

(Grey): Neutral, no action required.

STATIONARY

Safe but not moving.

ARRIVED

(Green): Mission complete.

SIGNAL LOST

(Red): Critical risk, immediate action required.

Confirmation screen

Design Strategy

Bypassing Low-Fidelity with AI

To overcome stakeholder hesitation, I bypassed traditional low-fidelity wireframes. Instead, I used a "Vibe Coding" workflow treating natural language as a design tool to rapidly generate and validate high-fidelity prototypes. This allowed stakeholders to react to the actual "Grandma-Friendly" experience in real-time, cutting weeks of abstract debate.

Eliminated Guesswork

Replacing abstract wireframes with a live prototype shifted the conversation from "interpreting sketches" to "testing reality." This clarity cut the time-to-consensus by 60%, as stakeholders could finally validate the logic in action.

Eliminated Guesswork

Replacing abstract wireframes with a live prototype shifted the conversation from "interpreting sketches" to "testing reality." This clarity cut the time-to-consensus by 60%, as stakeholders could finally validate the logic in action.

Bridged the "Imagination Gap"

The prototype cleared up the fear of complex data. It helped non-technical stakeholders to see the product's simplicity, allowing for rapid, informed design iterations to refine the UX together in real time.

Bridged the "Imagination Gap"

The prototype cleared up the fear of complex data. It helped non-technical stakeholders to see the product's simplicity, allowing for rapid, informed design iterations to refine the UX together in real time.

Retrospective

20% Efficiency Gain & Stakeholder Validation

Passing the 'Grandma Test'

Shifting the focus from "managing rows" to "monitoring missions" transformed the app from a passive log into a proactive tool for high-speed decision-making.

Passing the 'Grandma Test'

Shifting the focus from "managing rows" to "monitoring missions" transformed the app from a passive log into a proactive tool for high-speed decision-making.

From 5 Minutes to <10 Seconds

Decoupled the "Viewer" (Commander) from the "Operator" (IT), providing high-level situational awareness.

From 5 Minutes to <10 Seconds

Decoupled the "Viewer" (Commander) from the "Operator" (IT), providing high-level situational awareness.

Increase in Stakeholders Trust

Replaced "alert noise" with a strategic hierarchy. Distinguishing technical glitches from life critical emergencies restored stakeholder trust in system reliability.

Increase in Stakeholders Trust

Replaced "alert noise" with a strategic hierarchy. Distinguishing technical glitches from life critical emergencies restored stakeholder trust in system reliability.

I can finally see what’s happening without asking for help. This is a very well-designed user experience.

Create a free website with Framer, the website builder loved by startups, designers and agencies.