WExData: bringing order to a logistics network's internal systems

A redesign of the internal platform W Express uses to run its nationwide delivery, warehousing, and customer-service operations-without breaking what already worked.

CLIENT

WExpress | Wide Wide World Express

DURATION

January 2025 - Present (8 Months)

PLATFORM

Website Application

MY ROLE

UI/UX Designer

Research, User Experience, Design System, and Interactive Prototype.

TOOLS

OVERVIEW

A system that already worked — just not for the people using it

W Express runs delivery, warehousing, and customer-service operations across a nationwide branch network. The internal system supporting that later named WExData already carried the business's core logic. What it didn't carry was clarity: as modules were added over time, the interface grew harder to navigate for the operations and customer-service teams who relied on it daily.

My job wasn't to replace it. It was to restructure the experience navigation, hierarchy, and interaction patterns — while preserving every business rule the system already enforced.

I led the information-architecture restructuring - auditing the existing module structure, presenting reorganized navigation concepts to stakeholders, and translating their operational feedback into a design system used across both the Operations and Customer Service modules.

The challenge, module by module

Six problems the old system had accumulated

Each pain point below maps directly to a decision made in the redesign — this wasn't a cosmetic pass, it was a response to specific friction the teams were living with.

Pain point → Decision

Navigation required going through multiple modules to find one function

Reorganized the module structure into clear, task-based categories, cutting down the number of steps between login and the function someone actually needed.

Pain point → Decision

Related functions weren't grouped, so their place in the system was unclear

Regrouped functions by workflow rather than by system origin, so the structure matches how operations and customer-service teams actually think about their work.

Pain point → Decision

Dense screens made it hard to scan for what mattered

Rebuilt hierarchy and spacing so the most important data and actions are identifiable in a glance, not buried in a wall of fields.

Pain point → Decision

Inconsistent UI patterns across modules slowed people down

Standardized components and interaction patterns into a shared design system, so a behavior learned in one module carries over to the next.

Pain point → Decision

The structure wouldn't scale as more modules were added

Designed the navigation and layout model to absorb new modules without another restructuring — a system built for the company's next few years, not just its current state.

Pain point → Decision

Business logic had to survive the redesign untouched

Every rule and requirement from the existing system was mapped before any screen was touched, so the redesign improved the experience without breaking operations.

Research & discovery

Where the findings came from

Existing system audit

• Mapped the current navigation and module structure

• Flagged screens with dense or unclear information

• Catalogued existing interaction patterns

Business requirements

Documented rules that had to be preserved

• Traced how modules supported operations vs. customer service

• Identified constraints for the new structure

Stakeholder feedback

• Design reviews with operations leads

• Iterated navigation based on real workflow gaps

• Validated module groupings before build-out

Results & reflection

What changed for the teams using it

1%
reduction in steps to complete a common task
1
modules consolidated into clearer categories

Reflection

• Working on WExData taught me that enterprise UX is often about making complex systems easier to understand rather than simply making interfaces visually appealing.

• When a system contains many modules and workflows, the way information is organized can have a significant impact on how easily users navigate the product.

• The redesign process showed me the importance of continuously refining solutions through stakeholder feedback and iteration.

• Using consistent components, patterns, and interaction behaviors makes a large system feel more predictable and easier to navigate.

WexData -internal logistics platform redesign for WExpress. Case study by John Rey Sisa.

Design is a process.

Collaboration makes it meaningful.

Let's build experiences that makes an impact

Let’s Build Together

UX/UI Designer

I design with purpose, empathy, and simplicity. I turn complex ideas into intuitive and meaningful experiences. Every interaction should make life easier, better, and more enjoyable.

CONTACT

John Rey Sisa

johnreysisa1@gmail.com

johnreydesigner.framer.website

2026 John Rey Sisa - All rights reserved.

John Rey Sisa

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