Overview
This case study highlights Shippabo's platform redesign, enhancing workflows, shipment tracking, and supply chain efficiency through improved delivery and communication.
Objectives
This is a freight logistics platform aimed at simplifying supply chain management for businesses. This case study covers the redesign of three key features:
• Shipment Tracking - improved tracking tools for real-time updates and predictive insights.
• User Roles and Permissions - streamlined role management to enhance collaboration and security.
• Partner Logistics Management - optimized tools for managing partners and ensuring smoother operations.
MY ROLE
Senior Product Designer
TEAM
1 Product Manager, 3 Designers, 5 Developers, 1 Founders, 2 UX Writers
DONE WITH
Figma, Illustrator, ChatGPT, Relume, Lovable, Maze
INDUSTRY
Freight, Logistics, and Supply Chain Services
Process
Research and Discovery
Understanding User Needs
Conducted interviews with supply chain managers, logistics professionals, and business owners to identify challenges and pain points.
Pain Points
Fragmented workflows caused by disconnected tools.
Limited shipment visibility, leading to delays and inefficiencies.
Difficulty coordinating with global suppliers and partners.
Manual processes slowing down operations and reducing productivity.
Site Map and Navigation
I created the application site map and mapped out all the modules and sub-modules that we were going to build.
The application contains the following main and sub modules:
User Roles and Logistics – with 7 sub-modules
Shipment List – with 4 sub-modules
Container List – with 8 sub-modules
Payments – with 2 sub-modules
Administration Tools – with 7 sub-modules
Other key parts
Search entities tool
Search products and product groups tool
Component Library
To ensure a cohesive and efficient design process, I built a comprehensive component library from the ground up. This systemized approach allowed me to rapidly craft and iterate on the interface while maintaining consistency across the product. The component library not only accelerated my workflow but also served as a foundational resource for the development team, providing them with a full suite of standardized elements, patterns, and variations necessary for scalable implementation.
This groundwork helped bridge design and development, reducing ambiguity, minimizing rework, and enabling faster releases.
The application structure is organized into several main modules and submodules, including:
Dashboard – Central hub for key metrics and quick actions
Project Management – Tools for creating, tracking, and editing projects
User Settings – Personalization, account management, and preferences
Notifications – Real-time updates and alert management
Reporting – Detailed analytics and performance insights
Each module was carefully designed with reusable components to optimize maintainability and future scalability as the product evolves.
The Take Away
Regarding business requirements, it is very important to understand and interpret what the clients are really thinking and communicating. It is also our job to help them sort out their requirements when there are inconsistency and find out what they really need. As UX designers and strategic thinkers, we are here to frame the business’ problems and get a big picture first. By getting the requirements down, we avoid developing solutions that are irrelevant and be more efficient in delivering solutions they really need and work for them. The solutions must also intersect the clients’ business needs and the users’ needs as the users are the one using the application.
Testing is crucial throughout the entire process. We involved our team and collected as much input from real users as possible. Testing should be done early on to detect any issues or broken links in the workflow. This will prevent headaches and problems later on.
