A photo of the final mock-up which featured the design solution for the reloads project.
carrier 360: Reloads
A WORKFLOW MODIFICATION WHICH STREAMLINES THE LOAD PLANNING PROCESS FOR DRIVERS AND PLANNERS.
WHAT IS CARRIER 360?
Carrier 360 by J.B. Hunt is a web and mobile based app which allows fleet owner-operators, manager, and/or drivers to operate efficiently by allowing for purchasing loads for transport, planning that load on the appropriate resource (truck, driver, or both), and provide scheduling capabilities for their entire operation.

Year

  • 2020 (Q3)

duration

  • Research - 3 Sprints
  • Design - 3 Sprints
  • Dev - 3 Sprints

scope of work

  • User Research
  • User Experience

Collaborators

  • 3 UX Designers
  • 3 FE Devs

Company

  • J.B. Hunt
Original Loadboard
the process
identifying the problem
Through analytics, the team was able to identify an increase in abandonment during the load process checkout over a 12-month period prior to this project. The most interesting aspect of our findings was that the users choosing to find an alternative platform had already successfully bought and booked a load for transport. We in turn reached out to many of those individuals in hopes of gaining more concrete insight and we’ve discovered the following:
initial insights
Brainstorming Session results
With this information, UX designers and researchers conducted brainstorming sessions with areas of the business which best support these companies to uncover any additional pain points from their perspective. The result of these sessions yielded the following aspects of a strategy for addressing the issue(s):
With these things in mind, the general consensus was that modifications to the “Loadboard” and “In Transit” pages within the app would best address the user issues in both the short and long-term
The Designs
The Modified loadboard
What's changed?
The Modified loadboard > Preview
What's changed?
The Modified loadboard > Preview > no Reloads
What's changed?
My loads > In Transit
What are in transit loads?
what changed?
My loads > In Transit > Reloads
My loads > In Transit > Reloads > no reloads
What's changed?
What we’ve learned
user testing results
The majority of participants had no issue in the discovery or understanding the intention behind the new feature. There were a few whom got slightly confused about the new naming convention but we were able to support them in understanding the intention quickly. There were no abandonments when tasked with navigating the wireframes and prototypes during each testing session.
post-release insights