EchoDrive: “Batch reporting”
Platforms: iOS & Android
Year of project: 2018
Project brief: Create a way for truck drivers to report more than one load event (pickup, arrival at delivery, etc.) at a time in the EchoDrive app
My role: I worked with a team of developers, a visual designer, a project manager, and a senior UX strategist in an agile environment. I led design sprints, built wireframes, defined user and interaction flow.
Results: A streamlined way to report multiple events at once.
Background
Eight Bit Studios worked with Echo, a trucking logistics company, on their app, EchoDrive. The app lets drivers, shippers, and carriers to easily communicate with each other throughout the shipping process.
Echo asked us to create a way for truck drivers to report multiple events in the app at once. Drivers are required to report their location once a day and check in at every major milestone, or “load event.” However, Echo noticed some drivers would forget to report events and would get frustrated when they had to manually enter each event.
We referred to the process of reporting more than one load event at a time as “batch reporting.”
First design sprint: Sketches and wireframes
I led the team in a five-day design sprint. We came up with three concepts and I took the sketches from our whiteboarding sessions and upgraded them to wires in Sketch.
Option 1: Closest to current experience
We wanted to provide an option that was similar to what currently exists in the app. This option mirrors the current flow with the exception of the new “Add Another Event” button and the “Confirmation” screen.
Option 2: Vertical approach
We liked the idea of making all of the load events appear in a vertical timeline.
Option 3: Stop-centric approach
For this option, we turned each milestone into a card and reversed the way events appear on the timeline.
Second design sprint and client feedback
Clients liked the vertical approach of Option 2 and the way the information is displayed in Option 3. We combined both concepts and the two and made a prototype to share with stakeholders.
Our biggest challenges were making sure drivers knew where to tap and following existing logic for reporting events.
Third design sprint: Stakeholder feedback and a pivot
Stakeholders didn’t like the “Report xxxx” CTA in the load events tab (shown on the right in green). They expected batch reporting to replace everything on this screen.
This feedback caused us to go back to the whiteboard for another sprint.
The biggest challenge was figuring out how to allow drivers to “Send a Load Update” (i.e. report their location or report trailer drop off) once they are en route to the delivery location. We solved for this by including a “Send Load Update” card in the flow once the driver has reported “Loaded at Pickup.”
Updated flow
We went through several iterations of the “Send Load Update” functionality and ultimately made it look different from the “Pickup” and “Loaded” cards because I was worried drivers would be confused by the similar look and feel.
Revised “Send Load Update” functionality
Final “Send Load Update” flow
Final prototype
Link to final prototype: https://invis.io/ECG80WJZVPN