Digging into the BudBuddy- project

November 1st 2019

The carriers’ everyday life is changing, and will keep doing so in the time to come. In the future, carriers will deal less with set routes containing set addresses, and deal more with routes that consist of different addresses from day to day. In addition, new product types will be introduced, which the carriers don’t necessarily have much knowledge about. This is where our project “BudBuddy” comes into the picture: through this project we wish to create a tool which is robust enough to handle these new distribution characteristics. Ideally, it should ensure that the carriers’ work doesn’t get too complicated than it is today.

We have several ambitions for this project. First of all, we hope that the tool will make the carriers as independent as possible, and allow them to solve challenges they encounter without involving others. We hope to achieve this by giving the carriers the information they need when they need it. But we also want to facilitate the sharing of information between carriers - this way they can more easily share their unique local knowledge. Our ambition is to make the tool detect this information, and make it available for those who need it. Lastly, we wish to personalize the tool, to more easily motivate the carriers. This entails personal log-in for each carrier, and the use of gamification to illustrate the carrier’s achievements at work.

Each week we work with a main hypothesis. Examples of such hypotheses can be focus on navigation , onboarding or parcel handling , and by building on the hypotheses we try to make a physical prototype which we can test. We’ve therefore spent quite some time with the carriers on site. Over a relatively short period of time we’ve decided whether we’re on the right track or not.

The hypothesis we started with was navigation. And why is that? Well, we believe that there is a great value in easily helping the carrier to each delivery point without the use of external apps like Google Maps or 1881. In a dynamic future with more and more new addresses we think this will become even more important.

Our goal is to explain to carriers how they can get to each delivery point in an easy and intuitive way. One of the first things we tried to integrate into the tool was therefore a navigation solution (a map), where the carrier can get a visual presentation of each delivery point, which is updated based on the carrier’s current position. We also thought about different ways of making the delivery point more clear (e.g. delivery on door or mailbox) by using different symbols.

What have we learned?

  • We’ve understood that we’re on the right track by focusing on navigation, and we therefore have to explore the topic further!
  • During our first testing we had only implemented a map with an aggregated overview of all delivery points, but there was no function that could navigate the user between delivery points. After the testing we understood that navigating the carrier between point A and B is also crucial!
  • We’ve understood the importance of good data, and the in-tool navigation must therefore be precise, based on good data, and be updated at all times.
  • The tool must always be updated about where the actual delivery point is, and not navigate the carrier to the point where the mailbox used to be.

That’s it for now. We hope that you feel a bit more informed about the BudBuddy-project than you did before reading this article.

Besides, we appreciate your feedback, whether it is good or bad. If you have anything on your mind, please reach out by sending an e-mail to nxt@di.no

💙 The DI NXT-team