CASE STUDY
Enterprise UX for warehouse operations, inventory accuracy, item compliance, and shipping execution.
Enterprise UX
Workflow Architecture
Data-Dense Product Design
Product System Leadership
Role
Senior UX Designer / UX Architect
I led UX and product direction for a scalable warehouse management experience, translating fragmented legacy workflows and dense operational data into connected, role-aware product systems.
HERO PRODUCT COMPOSITE
Overview
Inventory Operations
Item Master
Shipping Execution
CASE STUDY OVERVIEW
GEODIS WMS translated fragmented warehouse workflows, dense operational data, and disconnected legacy processes into a scalable UX framework for inventory, item data, operational setup, and shipping execution.
Challenge
Warehouse teams needed to manage high-volume workflows across inventory, item data, shipping, and account configuration while working within years of legacy system growth and disconnected processes.
Users
Inventory specialists, warehouse specialists, shipping supervisors, administrators, and operations managers working across setup, accuracy, compliance, shipping, and exception handling.
Solution
A modular WMS experience with workbenches, dashboards, structured forms, reusable tables, validation, progressive disclosure, design-system patterns, and development-ready documentation.
Product Value
Supported Synapse modernization by improving workflow visibility, product consistency, operational control, and design-to-development alignment across GEODIS warehouse workflows.
Modernized Product Ecosystem
01 — Tool Hive / Admin Setup
Role configuration, account setup, and operational parameters
02 — Item Master
Item records, compliance data, and attribute management
03 — Inventory Operations
Physical Inventory, Cycle Count, location management, count progress, and inventory accuracy
04 — Shipping Execution
Shipping orders, manifests, and carrier management
PRODUCT CONTEXT
GEODIS WMS was part of a broader Synapse modernization effort to translate fragmented warehouse workflows, legacy technology, dense operational data, and disconnected user processes into a unified, scalable product experience.
Before
Fragmented workflows · Legacy technical constraints · Dense operational data · UI added around system limitations · High context switching · Limited workflow visibility
After
Unified product framework · Modern responsive UI · Progressive disclosure · Preventative validation · Role-based workflows · Dashboard and reporting visibility
01 — Legacy system complexity
02 — Structured UX and product framework
03 — Scalable WMS platform
UX focus
Translate legacy operational complexity into a structured product experience that helped users understand data, prevent errors, complete tasks, and manage exceptions with clearer workflow support.
UX ARCHITECTURE
The UX architecture connected administrative setup, item data, inventory workflows, and shipping execution into a scalable ecosystem that reduced fragmentation and helped teams work from shared operational context.
01 — Tool Hive / Admin Setup
Customer · Business unit · Account · Warehouse · Location · Labor standards · BI plugin
02 — Item Master
Item maintenance · Regulated products · Product groups · Unit of measure · Specifications · Receiving rules · Shipping rules
03 — Inventory Operations
Cycle Count · Physical Inventory · Task queues · Saved searches · Accuracy dashboards · Activity logs
04 — Shipping Execution
Single-package shipment · Multi-piece shipment · Manual shipment · Carrier and service selection · Rate results · Print and void · Validation
Reduced context switching by connecting setup, data, task management, dashboards, validation, and exception handling into reusable WMS workflow patterns.
USER CONTEXT
The experience had to support warehouse roles with different permissions, priorities, data needs, operational pressures, and exception-handling responsibilities.
Inventory Specialist
Goal: Maintain accurate item, inventory, and regulated attribute data. UX need: Fast access to records, count status, regulated attributes, exceptions, and downstream relationships.
Warehouse Specialist
Goal: Execute physical inventory and Cycle Count tasks. UX need: Clear queues, status, saved searches, include and exclude actions, and count-progress visibility.
Shipping Supervisor
Goal: Manage package shipment workflows and resolve blockers. UX need: Guided package entry, carrier selection, validation, print and void actions, and recovery paths.
Admin / Account Operations
Goal: Configure the operational backbone of the WMS. UX need: Structured setup across customers, accounts, warehouses, locations, permissions, and dependencies.
Make dense operational data understandable by matching screens, permissions, actions, and validation to role-specific decisions.
WORKFLOW DEEP DIVE
Cycle Count and Physical Inventory brought search, saved views, task queues, status summaries, dashboards, and actions into one role-aware workspace that could scale from high-permission oversight to focused task execution.
INVENTORY OPERATIONS WORKBENCH — Insert GEODIS WMS Cycle Count and Physical Inventory screenshots from case-study pages 6–7.
Search + Saved Views
Users could define, save, and reuse criteria across warehouse, item, location, role, and operational rules.
Role-Based Task Control
High-permission users could review assigned, unassigned, deleted, prioritized, and rule-driven tasks, while other roles received focused views.
Operational Visibility
Dashboards and summaries surfaced completion, accuracy, variance, performance, and activity history so teams could monitor progress and follow up.
Reduce context switching by combining search, task creation, task management, dashboards, status, actions, and role-based visibility into one inventory operations workspace.
WORKFLOW DEEP DIVE
The Cycle Count experience turned inventory rules, item and location criteria, task queues, scheduling, and count status into a repeatable workflow for managing inventory accuracy over time.
Count Request Workflow
Users could define Cycle Count criteria around warehouse, item, location, zone, status, and operational rules.
Task Queue Management
Task views helped teams review assigned work, recent counts, rule-driven activity, exceptions, and count status.
Accuracy Visibility
Overview, performance, scheduler, and activity views supported progress tracking and exception follow-up.
CYCLE COUNT WORKFLOW — Insert request, task queue, overview, scheduler, and accuracy screens from case-study page 7.
Structure dense inventory data into repeatable count workflows supporting accuracy, task control, scheduling, and exception follow-up.
WORKFLOW DEEP DIVE
Item Master became the source of truth for product attributes, compliance requirements, receiving rules, storage needs, picking behavior, and shipping workflows across the WMS platform.
ITEM MASTER AND REGULATED PRODUCTS — Insert Item Master, regulated product overview, compliance relationship, and document-preview screens from case-study page 8.
Regulated Item Visibility
Summary panels surfaced regulated products, product types, review needs, compliance-sensitive categories, and downstream attribute relationships.
Section-Based Editing
Dense details were organized into Item, Unit of Measure, Specifications, Receiving, Shipping, and Regulations sections.
Operational Rule Management
The workflow supported product groups, aliases, storage rules, valid lots, vendors, receiving capture, shipping rules, and related dependencies.
Use progressive disclosure to turn dense item data, compliance rules, and downstream workflow dependencies into a clearer source-of-truth experience.
WORKFLOW DEEP DIVE
The shipping module supported single-package, multi-piece, and manual shipment workflows while surfacing missing data, package errors, carrier decisions, and recovery paths before completion.
Guided Package Entry
Shipping details, package dimensions, ship date, carton ID, carrier and service selection, and package information were structured into a focused workflow.
Multi-Piece Shipment Status
Pending, Added, and Error states helped users track progress, identify blockers, and manage complex shipments.
Validation and Recovery
Required-field errors, ship-to details, rate results, print and void actions, and carrier service data supported exception handling before completion.
Guide users through shipping complexity by making required data, package status, carrier decisions, and recovery actions visible before shipment completion.
PLATFORM FOUNDATION
Tool Hive gave teams a structured way to manage customers, business units, accounts, warehouses, locations, labor standards, permissions, and integrations that powered downstream WMS workflows.
TOOL HIVE AND ADMINISTRATION — Insert Tool Hive landing, customer configuration, account settings, and labor-standard screens from case-study page 10.
Operational Hierarchy
Customer, business unit, account, warehouse, and location setup connected users and workflows to the correct operational context.
Configuration Dependencies
Account settings, shifts, warehouse setup, locations, labor standards, permissions, and integrations supported downstream workflows.
Scalable Admin Patterns
Reusable tables, forms, status states, search, edit, copy, save, upload, and validation patterns created consistency.
Configuration patterns created the operational backbone that downstream WMS workflows depended on.
DESIGN SYSTEM THINKING
Reusable interaction patterns helped teams navigate dense data, complete tasks, review status, recover from exceptions, and support consistent design-to-development implementation.
Data Tables
Sorting, scrolling, pagination, row actions, and status visibility.
Search and Filters
Structured criteria, saved searches, and reusable filters.
Status States
Pending, Added, Error, Active, Inactive, Assigned, and Unassigned.
Action Menus
Assigning, prioritizing, restoring, deleting, printing, voiding, copying, saving, and recovery.
Dashboards
Completion, accuracy, variance, activity, performance, and operational exceptions.
Section Navigation
Focused form sections supporting progressive disclosure.
Validation
Required fields, inline errors, disabled actions, and recovery guidance.
Custom Design System
Reusable UI patterns, documentation, shared design-to-development language, and a custom IcoMoon icon library.
Use reusable patterns to turn legacy workflow complexity into a scalable product system that development teams could build consistently across modules.
PRODUCT VALUE
Reduced Context Switching
Workbenches combined search, task management, dashboards, and actions so users could manage workflows from fewer places.
Improved Data Consistency
Structured forms, reusable tables, required fields, and validation supported cleaner data across modules.
Better Supervisor Visibility
Dashboards, queues, status states, performance summaries, and activity logs made work progress easier to monitor.
Reusable Product Framework
Shared patterns created consistency across inventory, shipping, and administrative workflows.
Exception Recovery
Validation, package states, errors, and recovery paths helped users identify and resolve blockers.
Modernization Framework
Created a repeatable foundation for combining complex GEODIS workflows into scalable enterprise applications.
MY CONTRIBUTION
I helped translate Synapse modernization goals and complex warehouse operations into structured UX flows, reusable interaction patterns, and scalable enterprise product experiences.
As the sole UX and product partner on the project, I helped stabilize and accelerate GEODIS modernization by translating legacy workflow complexity, dense warehouse data, user research, stakeholder feedback, and operational requirements into structured product workflows, reusable design-system patterns, and development-ready documentation.
Workflow Architecture
Mapped connected workflows across setup, item data, inventory operations, shipping execution, dashboards, validation, and exception handling.
Data-Dense UX Design
Structured tables, filters, forms, task queues, dashboards, status states, and progressive disclosure.
Interaction Patterns
Created reusable patterns for search, saved views, pagination, validation, actions, role-based visibility, and workflow recovery.
Research and Discovery
Conducted interviews with warehouse workers, supervisors, administrators, SMEs, and business stakeholders.
Product Ownership
Helped define product direction, workflow priorities, Agile process structure, and alignment between stakeholders, UX, and development.
Design-to-Development System
Created documentation, shared language, reusable patterns, and a custom IcoMoon icon library.
CASE STUDY SUMMARY
GEODIS WMS demonstrates my ability to translate legacy operational complexity, dense warehouse data, user needs, and modernization goals into clear, scalable enterprise UX systems.
Enterprise UX Architecture
Connected workflows across configuration, item data, inventory operations, shipping, dashboards, validation, and exception handling.
Complex Workflow Simplification
Role-aware screens, task queues, dashboards, status states, progressive disclosure, and reusable interaction patterns.
Data-Dense Product Design
High-volume tables, search, filters, forms, validation, compliance rules, and exception-heavy workflows.
Product Modernization Support
A scalable UX foundation spanning workflows, teams, development patterns, and product areas.
“This case study represents the type of enterprise UX work I do best: turning complex, fragmented operations into clear, scalable product systems that teams can understand, build, and grow.”