Stakeholder Interviews & Qualitative Research
To understand the shipment collaboration process and business requirements, I worked closely with the Business Analyst, Product Manager, and Engineering team. These discussions represented the needs and workflows of the primary usersโSuppliers and Buyers.
Key Insights
Suppliers need a simple and flexible way to create, update, and submit ASNs.
Buyers require complete shipment information before approving inbound deliveries.
Manual communication and disconnected workflows reduce shipment visibility.
Clear status tracking is essential throughout the shipment lifecycle.
Complex scenarios such as ASN revisions, partial shipments, direct deliveries, and landed costs should be supported without increasing user complexity.
Large datasets require efficient search, filtering, and bulk actions for enterprise-scale operations.
Pain Points
Based on stakeholder discussions and workflow analysis, the following key pain points were identified:
Manual communication through emails and phone calls.
Limited visibility into inbound shipment progress.
No centralized platform for supplier-buyer collaboration.
Manual shipment planning increased processing time and errors.
Limited warehouse readiness due to lack of advance shipment information.
Scattered shipment documents across multiple systems.
No standardized ASN workflow for creation, approval, and tracking.
Research Insights
The research study revealed several key findings or insights which has connection with the data which reveal key areas where the system can be improved to enhance user experience and operational efficiency.
Digital Wireframes
Created digital wireframes to visualise the structure and layout of the platform, focusing on user-friendly navigation and core functionality.
Affinity Mapping
Organized research data through affinity mapping and themes. It really helped to increase the usability of the product and also their feelings and emotions in different situations.
Warehouse teams
had little advance
notice of incoming
deliveries.
D
Shipment info
was shared
through emails
and phone calls.
A
Shipment updates
were difficult
to communicate
consistently.
B
Approval feedback
lacked a structured
communication
process.
D
No centralized
platform for
supplier and
buyer collaboration.
C
Shipment progress
was difficult to
track in real time.
E
Shipment
documents, tracking
information
were scattered
across systems.
B
Buyers had limited
visibility into
inbound shipments.
C
Proof of Delivery
Exception Management & Communication
Workflow Complexity
Frequent
revisions made
tracking changes
difficult.
D
Managing large
purchase orders
and shipment lines
was challenging.
C
Approval and
revision cycles were
time-consuming.
B
Multiple shipment
scenarios increased
process complexity.
B
Managing shipment
documents required
multiple manual
steps.
E
Shipment creation
involved repetitive
manual data entry.
C
Handling packaging
and landed costs
required additional
effort.
E
Users switched
between different
systems to complete
the workflow.
D
Communication & Collaboration
Shipment Visibility
Process Efficiency
Advance Shipment Notice
Designing a seamless last-mile delivery experience for Managers & Drivers


Project Overview

Advance Shipment Notice (ASN) is a feature within Infor Enterprise Collaboration Portal (ECP) that enables suppliers to digitally create, manage, and submit shipment information before goods are dispatched. It provides a centralized platform for suppliers and buyers to collaborate throughout the shipment lifecycleโfrom ASN creation and approval to shipping, goods receipt, and closureโwhile seamlessly integrating with Infor LN.
Business Goals
Digitize the ASN process for suppliers and buyers.
Improve shipment visibility before delivery.
Streamline ASN creation, approval, and tracking.
Reduce manual communication and receiving errors.
Enable efficient warehouse planning.
Integrate seamlessly with Infor LN.
๐ฏ The Challenge
Managing shipment information across multiple stakeholders involved fragmented communication, manual approvals, and limited visibility into shipment status. Supporting complex scenarios such as ASN revisions, packaging, landed costs, direct deliveries, and inspection while keeping the experience simple was the primary UX challenge.
๐กThe Solution
Designed an end-to-end ASN workflow with guided shipment creation, status-driven collaboration, and contextual information architecture. The solution enables suppliers and buyers to create, review, approve, track, and manage shipments efficiently through a single enterprise portal.
My Role and Responsibilities
User interviews, defining user personas, empathy mapping, information architecture, developing design system, designing visual mockups, prototyping, usability testing.
๐ฅ Primary Users
Supplier
Creates, updates, and manages Advance Shipment Notices.
Uploads shipment details and supporting documents.
Tracks shipment progress and responds to buyer feedback.
Buyer
Reviews and approves submitted ASNs.
Monitors inbound shipments.
Coordinates with suppliers before warehouse receipt.
Design Thinking Process




Empathize

Stakeholder Interviews
Qualitative Analysis
Pain Points
Define
Empathy Map
User Personas
User Stories
Ideate
Brain Storming
Story Boarding
Information Architecture
Work Flow
Prototype
Digital Wireframes
Visual Mockups
Interactive Prototype
Test
Usability Study
Usability Tests
Refining Mockups
Next Steps
Affinity Mapping
Empathy Map
This process was done to define the target audience with more clarity, as well as illustrate their needs and actions. Empathy mapping helped to gain perspective on their thoughts and feelings. The data in the empathy map are based on insights from user interviews.
I need a faster way to create and submit ASNs.
I want buyers to receive accurate shipment information.
Keeping shipment details up to date should be easy.
I need to know the status of my shipment.
Says
Reviews purchase orders and selects shipment lines.
Creates and updates Advance Shipment Notices.
Uploads shipping documents and packaging details.
Monitors approvals, shipment status, and revises ASNs when required.
Does
Have I entered all the required information?
Will the buyer approve my ASN without changes?
How can I avoid shipment delays?
I need complete visibility throughout the shipment process.
Thinks
Frustrated by manual and repetitive processes.
Pressured to meet shipment deadlines.
Concerned about approval delays and errors.
Confident when shipment progress is transparent and easy to track.
Feels

User Personas
Created user personas representing ideal users of the application. The personas helped us arrive at better solutions as they gave an in-depth understanding of the user goals, frustrations and the overall personality.
Proactive
Collaborative
Organized
Sanjay Patel
Personality
Breif Story
Detail-Oriented
Sanjay being a supplier, manages shipments. He is responsible for creating Advance Shipment Notices (ASNs), maintaining shipment information, uploading supporting documents, and ensuring shipments are delivered according to customer schedules.
Create and submit ASNs quickly with accurate shipment details.
Minimize shipment delays and approval cycles.
Maintain accurate packaging and shipment documentation.
Track shipment and approval status in real time.
Frustations
A centralized platform to create and manage ASNs.
Simple workflows for updating shipment information.
Real-time approval and shipment status tracking.
Easy document upload and management.
Uses enterprise procurement and logistics applications daily.
Regularly monitors shipment and order statuses.
Frequently uploads shipping documents and attachments.
Prefers guided workflows with minimal manual effort.
Age
Role
Experience
Proficiency
38
Supplier
Mumbai, India
Advanced
Goals
Needs
Digital Behaviour
Manual communication with buyers delays shipment processing.
Repeated ASN revisions increase operational effort.
Limited visibility into approval and shipment status.
Managing shipment documents across multiple systems.

Breif Story
Analytical
Responsible
Decisive
Collaborative
Praveen oversees supplier collaboration and inbound procurement activities. He reviews submitted ASNs, verifies shipment information, approves deliveries, and coordinates with suppliers to ensure goods arrive on schedule.
Personality
Praveen Kumar
Complete shipment information before approval.
Real-time visibility into shipment status.
Centralized communication with suppliers.
Easy access to shipment history and supporting documents.
Frequently reviews procurement dashboards and shipment updates.
Monitors ASN statuses throughout the approval lifecycle.
Uses enterprise ERP systems for procurement operation.
Prefers actionable dashboards and streamlined approval workflows.
Age
Role
Experience
Location
Proficiency
30
Buyer
12 Years
Bengaluru, India
Advanced
Goals
Review and approve ASNs efficiently.
Monitor inbound shipments before warehouse receipt.
Ensure shipment information is complete and accurate.
Improve collaboration with suppliers.
Frustations
Needs
Digital Behaviour
Incomplete shipment information delays approvals.
Limited visibility into inbound shipment progress.
Difficulty tracking ASN revisions and status changes.
Manual follow-ups with suppliers increase workload.

Customer Jouney Mapping
Created user personas representing ideal users of the application. The personas helped us arrive at better solutions as they gave an in-depth understanding of the user goals, frustrations and the overall personality.

Design System
Followed Infor Design System - SOHO
Visual Mockups
Created detailed visual mockups incorporating insights and feedback gathered from the users through usability testing sessions which helped us to make key design decisions.
Delivery Visibility Dashboard
The existing dashboard offered limited delivery visibility and required separate navigation for assignment tasks. We expanded delivery statuses and embedded assignment actions within the workflow, enabling managers to monitor and manage deliveries more efficiently from a single screen.
Initial Iteration


Final Design
Driver Experience

Initial Iteration

Final Design
Optimized Load Management
As delivery statuses increased, the tab-based navigation became difficult to scale. We replaced status tabs with a dropdown filter, added an Assign Load action, and grouped deliveries by customer to create a more efficient and scalable management experience.
Load Assignment
The initial flow focused on individual shipments, making assignments harder to manage. We redesigned the experience around loads, grouping related shipments together to simplify assignment and improve efficiency.

Initial Iteration

Final Design

Initial Iteration

Final Design
Simplified Load Reassignment
The reassignment flow was updated from shipment-based to load-based, removing unnecessary route, shipment, and completion details. This simplified the selection process, allowing managers to quickly reassign loads by focusing only on the relevant driver and customer information.
Drivers Overview
The driver experience was redesigned around loads instead of shipments to provide better visibility into workload and delivery progress. The Drivers Overview offers quick access to driver status, while the Driver Summary presents load-wise metrics and customer details for faster monitoring and decision-making.

Drivers Overview
Driver Summary


Live Tracking

Live Tracking Details
Live Tracking
The live tracking experience was designed to provide real-time visibility into load progress of the customer from a single interface. By combining map tracking, delivery information, and load details, managers can monitor deliveries more efficiently and respond to delays or exceptions faster.

Live Tracking
Proof of Delivery

Enhanced Delivery Visibility
Designed a unified last-mile delivery experience that brings together live map view, shipment management, customer communication, and proof of delivery in one place. This reduced unnecessary navigation, improved operational efficiency, and made delivery completion faster and more reliable.
Simplified Driver Dashboard
The dashboard was simplified to highlight key delivery statuses in a clean overview, while Settings, About, and Logout were organized under the navigation menu. This reduced visual clutter and helped drivers focus on their daily delivery tasks.

Dashboard
Menu

Usability Testing
After designing visual mockups, we have conducted another round of usability testing to validate the design and gather further feedback.

Before

After
Enhanced Exception Handling
During usability testing, users found the term "Failed" unclear and wanted more context for incomplete deliveries. Based on this feedback, it was renamed to "Not Delivered", and Reason & Driver Notes were added to provide clearer delivery context and support faster follow-up.
Improved Communication
During usability testing, users expressed the need for a quick way to contact customers before delivery. Based on this feedback, a Call Customer action was added to the Load Details screen, enabling faster communication while keeping all delivery information and key actions in a single workflow.

Before

After
Streamlined Proof of Delivery
Capturing proof of delivery involved multiple actions and could slow down the delivery process. Simplified the experience by bringing photo capture, signatures, and delivery confirmation into a single workflow. This made proof collection quicker, more reliable, and easier to complete.

Proof of Delivery
Live Map View


Suppliers needed a streamlined process to
create and manage ASNs.
1
Buyers required complete shipment information before approving deliveries.
2
Real-time shipment visibility was essential for effective planning and coordination.
3
A centralized platform was needed to improve supplier-buyer collaboration.
4
Enterprise workflows had to support revisions, partial shipments, packaging,
and landed costs.
5
Users preferred guided workflows over complex, form-heavy interfaces.
6
Clear status updates and notifications were critical for tracking shipment progress.
7
Integration with Infor LN was essential to maintain data consistency and eliminate duplicate effort.
8
Accessibility Considerations
Maintained sufficient contrast between text, icons, buttons, and backgrounds to ensure readability in bright outdoor conditions and for users with low vision.
High Color Contrast
Designed buttons and interactive elements with adequate size and spacing, making them easy to tap accurately while drivers are on the move or wearing gloves.
Large Touch Targets
Used descriptive labels alongside icons instead of relying on icons alone, improving usability and making actions easier to understand for all users.
Clear Labels & Icons
Key Takeaways
๐ Impact
Average task completion time reduced from 3.2 to 2.0 minutes, driven by simplified load-based workflows.
Navigation steps decreased from 8 to 5, as users could access key actions from a single workflow.
User satisfaction improved from 3.5/5 to 4.7/5, following iterative refinements based on usability testing.
โ User Errors with clearer labels, improved information hierarchy, and standardized exception reporting.
โ Operational Visibility with centralized dashboards, load-based tracking, and enhanced delivery status summaries.
๐ Lessons Learned
Early collaboration with stakeholders helped align business goals with user needs.
User research uncovered operational challenges that influenced key design decisions.
Iterative usability testing refined the experience and improved workflow clarity.
Next Steps
Integrate AI-powered load assignment based on driver availability, location, and priority.
Add predictive delivery alerts for delays and delivery exceptions.
Introduce offline-first capabilities with automatic data synchronization.
Enable voice-assisted proof of delivery for hands-free operation.
Enable managers to cancel assigned deliveries with predefined reasons and automatic driver notifications.



Thank you for watching!
Thank You
Information Architecture
Mapped the customer journey to understand how suppliers and buyers interact with the platform, uncovering pain points and opportunities to streamline procurement and shipment workflows.
