In order to truely understand the problem we spoke directly to the Fulfillment Managers and Delivery Drivers who requested help. It quickly revealed why a solution was under was soarly needed.

Fulfillment Managers have been using multiple stat tracking apps to monitor the performance of products at locations, and was only tied to store ID’s. This made it hard to associate ID’s with real locations, people, and even other metricsin other applications, leaving these managers frustrated and more open to mistakes.

Delivery drivers had similar issues. While they do not use as much of the metrics shown to Fulfillment Managers, they do need the visual association and quick access to directions.

Diving into the details, we found that some drivers would route their next location while driving away from the last to maintain efficiency. Many complained the process of finding the next location and routing was cumbersome and required more effort than services they used outside of their job like Google or Apple Maps. This is where the bonus request was added for stringing together multiple locations into a single automated route.

Meeting with the project's PM and a few of the RedBull developers, we quickly defined solution concepts, requirements, a timeline, and the limitations:

One fact I love when working on internal tools is the direct access to my users. No prolonged studies sourcing test users and sorting out times. With this in mind I dove quickly into the iteration and testing phase.

This page would serve as the home/landing page and allow users to search, filter, and select the location they are looking for. I focused on providing 2 key features:

History view is toggles by the history icon that uses the users account and recent selection history to build a list of location the user. This history was to be used as a proto-feature to allow users to build their own routes by reversing their history.

The details page had a finite list of information and graphics, but some data sets or graphics were larger than others. To keep this page functional on mobile and usable with a single hand I wanted to keep all the information for a particular data set visible on any device which led to one of the more interesting challenges of this design.

Once we got sign off for these screen and buy in from dev, managment, and our users, the next step wa delivering Hi-Fidelity interaction design for testing through a comprehensive prototype.

I love this step as it begins to iron out design decisions made earlier in the process including the microfeatures/ interactions involved in things like dropdowns, drawers, and page transitions.

Using the prototype above we were able to build out and test this application with our user base, gaining critical insight and making the last design tweaks before we handed over designs for development.

The last part of this project was to provide the team with direction on the next iteration involving the implementation of Establishing and using routes. While the history feature was scraped for the MVP it gave way to additional discussion around this feature and the ability to take a list of locations, optimize a route, and pass that new route back to the driver for directions.

Best for consistant/ rarely changing routes, this version allows the user to add locations to a custom group/list with feature to tweak these lists as needed.

Best for day by day routes, this route builder lets the user create a route quickly from the map or add location screen. Combined with the first direction the user could save these routes for future use.

Best for drivers or managers with a fixed list of managed locations. Here the user can add location to "My Locations" in the locations details page. Once the list is created the user can go to "My Locations" in the menu and select directions.

Additionaly in this version the user can long press a single direction to switch to an "Add more stops" mode, letting the user set up their route without leaving the page.

This project was completed in 3 weeks which included additional minor tweaks as the project went through development and some requirments were changed for production needs. My last contact with the project was an enthusiastic sign off from the PM and overwhelmingly positive reception of the prototype by the Fullfillment Managers and Drivers.

Unique to this project was the intent to ideate on a solution for a V2 while the MVP was being designed. While I spent time designing for the route builder, the route optimization faces a few challenges that will need to be researched before the next faze of this project.

I think this project went particularly well and I enjoyed getting to work with the talented people at RedBull. I was delighted to get to work with a Design System as fleshed out as RedBulls was with their own custom Wiki and developer component intergrations. This project was also a perfect example of MVP design getting the low hanging fruit early and quickly without bogging down development timelines so we can deliver an impactful product quickly then make iteration on that product based on real world usage and feedback.

Thank you for getting this far. I put a lot of effort into these case studies and its nice to see people get to the end... even if they skip some pieces. Have a great rest of your day!