ShipTrack
Elevating global logistics with enhanced tracking, seamless customs, and on-time deliveries for ultimate customer satisfaction
Product Experience
Problem Space
Problem Statement
We’re aiming to minimize DHL Express Customers’ frustration and uncertainty when tracking their shipments, so that they are more likely to receive their shipment on time which will cut costs, increase revenue, and positively impact business.
Problem Background
DHL achieves a 96% on-time delivery rate for 1.67 billion parcels annually in Canada. However, the remaining 4% (66.7 million parcels) pose disruptions for customers in various aspects. The emphasis is on investigating the reasons behind these occurrences, even when customers provide accurate information. The goal is to enhance tracking visibility and proactively address issues, ensuring on-time deliveries for customers.
Research Insights
User Pain Points
- Visibility: Customers face frustration due to limited and high-level tracking information, causing uncertainty about their shipments. Internal employees have more detailed insights, but this disparity creates a disconnect.
- Customs: Issues during the customs stage, such as missing information, unclear shipment details, and lack of easy communication methods, lead to delays and potential rejections.
- Delivery: Missing or incorrect contact details, customs duties, and inflexible delivery options contribute to delivery challenges. Inconsistent alignment between the booking system and local delivery routes adds complexity.
Supporting Data
- Despite DHL's 96% on-time delivery rate for 1.67 billion parcels annually in Canada, the remaining 4% (66.7 million parcels) present challenges for customers and businesses.
- In the customs stage, issues like missing information, unclear shipment details, and lack of easy communication methods can lead to shipment rejections, delays, and additional costs.
- The last-mile delivery accounts for 53% of the total shipping cost, and failed first delivery attempts cost retailers an average of $18 USD per delayed delivery.
Feedback
- Users desire detailed and real-time tracking information to reduce frustration and enhance on-time delivery.
- Customers seek earlier notifications for delivery options, aiming to avoid delays and make informed choices in advance.
- Business owners need reliable information for operational planning, ensuring resources are available for timely use of incoming shipments.
Landing on the Solution
- Easy use & Visibility: Introduce a user-friendly portal for DHL clients, providing detailed tracking information with timestamps for stagnant shipments, proactive notifications for critical missing data, and ability to upload missing data & speak to DHL staff
- Real-Time Data Platform: Create a centralized platform accessible via app or web, offering comprehensive, real-time information about shipments,customs and delivery through data from automated AI assessments in warehouses.
Explanation of Solution
- Enhanced User Interface: Empower DHL clients with a seamless portal experience, mirroring internal insights, and facilitating easy access to crucial shipment details, flight information, and local updates.
- Proactive Notifications: Implement a notification system for DHL Express users, offering earlier delivery options, aligning with driver routes, and ensuring accurate address and contact details, reducing unnecessary delays.
- Customs Transparency: Provide clear tracking indicators for customs stages, notify customers about potential delays, and allow them to update missing information, submit necessary documents, and manage broker details for a smoother customs process.
User Flows/Mockups
User Tracking Information:
- Safe and efficient link-based access to detailed shipment data.
- Access to detailed customer service/sales representative level insights, including location, timestamp, and status updates.
- Country/city-specific information on local holidays, weather impacts, and updates from warehouses.
Earlier Delivery Options Notification:
- Notification upon final destination flight scan for users to choose delivery preferences.
- Aligned time range with driver routes and a countdown timer for "hold for pickup" option.
- Confirmation of address and phone number accuracy to avoid delivery issues.
Customs Delay Resolution:
- Notification of shipment entering, held by, or released by customs.
- Detailed information on why a shipment is held by customs.
- User ability to update missing information, submit documents, and manage broker details.
Future Steps
Future Steps: Design & Prototyping
Week 3: Finish Design
- Dev & Design Meeting: Set timelines and assess feasibility.
- Define Metrics: Choose portal metrics, plan data tracking.
- UI/UX Creation: Develop and test user interface.
- User Feedback: Collect and iterate on prototype assumptions.
Week 4: Development & Prototype
- Prototype Testing: Test with users for feedback.
- Core Feature Build: Start building core features.
- Agile Development: Use agile and sprint format.
- User Feedback Loop: Incorporate user feedback.
- Thorough Testing: Ensure comprehensive testing.
Weeks 5-6: Beta Testing
- Limited Release: Beta test with user group.
- Feedback Collection: Gather and address feedback.
Week 7: Launch
- Product Launch: Prepare and execute launch.
- Marketing: Promote through marketing channels.
Post-Launch and Beyond - Week 9 + Ongoing
- Regular Updates: Provide ongoing enhancements.
- User Feedback Addressing: Address user feedback continuously.
- Performance Monitoring: Monitor performance and usage.
- AI Integration: Explore AI for automated monitoring.
- DHL Collaboration: Partner for live internal data use.
Note: Emphasis on iterative cycles, continuous improvement, and user-centric development.
Images
Learnings
Product Manager Learnings:
Katharine Sliwinski
Overall Co.Lab Learning Experience:
- Learning to think about the problem space without solutioning was a huge shift for me
- Struggling to collaborate with so many people in our teams and different groups was challenging. However
Survey insights/possible changes:
- For tracking-related questions, in-person interviews were more effective, as online responses often provided minimal information, with many "Yes" answers accompanied by "N/A" or mentioning the presence of a tracking number.
- Questions with an "overall" section yielded valuable detailed information.
- Simplifying Yes/No questions by eliminating the "other" option, focusing on "Yes," "No," "Neutral," or "Don't have an opinion/feeling," proved more effective.
- Data cleanup, though manageable with 40 responses, highlighted the importance of streamlining quantitative data collection.
Surprising Findings from the Survey Collection:
- Many respondents couldn't recall their DHL experience, prompting a shift in survey targeting to recent users.
- Positive experiences were common, contrasting with the negativity often encountered while resolving client issues.
- Aiming to focus on customers with negative experiences for insights on specific process stages.
- Unexpectedly, cost emerged as a key concern, challenging assumptions about tracking and customer service as primary issues.
Designer Learnings:
Designer Learnings:
Jo Sturdivant
- Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
- Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
- Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.
Developer Learnings:
Developer Learnings:
Vanady Beard
&
As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.
Developer Learnings:
Stephen Asiedu
&
As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.
Developer Learnings:
&
Developer Learnings:
Maurquise Williams
&
- Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
- Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
- Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.
Developer Learnings:
Jeremiah Williams
&
All in all this experience was very awesome I learned that in coding with others being transparent is key
Developers Learnings:
Justin Farley
&
I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.