Nimber is a community delivery service where you can ship anything with someone already going that way, anyway. Through the years, the p2p model is working mainly in the Norwegian market. Last year, there was a need to incorporate a b2b model. For a small number of daily deliveries, we already have our Nimber platform where you can post one task at a time and match with a driver to deliver your task. To embrace businesses though, we needed a more advanced tool to handle multiple deliveries easily. We come to the conclusion that we will need to create a managing tool for retailers, a dashboard.
- Retailers (users that need to send a big number of deliveries per month)
- Some small businesses who want manage multiple deliveries
As being in a small team, I worked closely with our CEO, our product lead, our business account manager, and our front-end developer. We worked on an early release and based on a framework called Bulma so we can quickly test this also as a concept. I initially created some wireframes to discuss with the team. On the sidebar I have added these tabs/sections:
- Overview: Stats about deliveries comparison/savings, saved Km/CO2, completed total deliveries, deliveries updates).
- Create: Upload a .csv/excel file with many deliveries, create one task from scratch, create bundled distributions (combine deliveries and assign them to one bringer, with Nimber recommendations), set your own price, preview & publish.
- Deliveries: Edit posted deliveries, select bringers (based on experience, ratings, car brand/size, etc.), view delivery statuses, read/send messages to bringers and recipients.
- Community: Filter and search for bringers, search for recipients info.
- Ratings: Read recipient ratings about bringers, read bringers ratings, rate bringers
- Stats: More detailed stats about deliveries comparison/savings, stats about completed vs canceled deliveries, saved Km/CO2 per year/month or custom time range.
- Payments: Check statuses of payments to bringers, edit payments, report issues.
- Settings: Account settings, payments settings.
- Notifications: Web notifications, e-mails and sms.
So many features so little time to add them all on our first version of the dashboard. We agreed only to add these initially:
- Create - Upload a .csv/excel file with many deliveries, create one task from scratch, create bundled deliveries (combine deliveries and assign them to one bringer, with Nimber recommendations), set your own price, preview & publish.
- Deliveries - Edit posted deliveries, select bringers (based on experience, ratings, car brand/size etc.), view delivery statuses, read/send messages to bringers and recipients.
- Ratings - Read recipient ratings about bringers, read bringers ratings, rate bringers
- Settings - Account settings, payments settings.
We also decided on having the ability to manage all this info with tables and sidebars when needed. Also, we focused on working thoroughly on our first-time users with step by step - feedback messages so they can learn quickly how to use this tool.
Because we used a specific framework, I decided to create a Sketch file with all elements of the dashboard and discussed with the front-end developer on consistently naming UI elements, so he can make changes quickly. Also, this will help to create future features on next versions easily. Every tool we designed at Nimber, is to cover specific user needs in different contexts (web platform, iOS app for senders & bringers, iOS app for pro bringers, dashboard) but this will help us in the near future to discuss, compare, change or combine our design decisions.