Joining the fleet
Most of the problems I faced during my iFood period were the same at Rapiddo, with less budget and few dev capacity. We had very serious problems when it comes to onboarding drivers. You can read more in detail
about the same issued I faced when in iFood here. But back in Rapiddo, as our operation was small enough, we could provide "activation" events of drivers. By that I mean that the company used to sent some of the ops team around the country to set up a talk, in some hotel room, to explain all the bits and pieces of how to be a driver in our platform.
It used to be a 60+ keynote with bunch of slides showing app screen shots and other ones explaining more in depth some of the rules of the service. That was tiring and expensive for all of the involved. We had to come up with a more scalable way of onboarding and training new drivers. We had a constraint of not changing anything in the native app. So we really had to be creative. And by that I mean: motion graphics. Yes, that's what it was. There I was, 3 months deep into After Effects tutorials.
We did some really legit startup work there. Very low budget. We got a co-worker of ours that liked and sang really well to record voice-overs for the videos. We then compromised all of the tiring keynote and talks the team used to give country wide in a set of 7 educational videos with animations, explaining every bit of detail we had in our operation and app. That was really out of the box by that time in the company and actually made an impact. The ops team really started to travel less and in conjunction with other onboarding optmizations the team done, we got a pretty stable supply-input machine going on.
One of the motion graphics made for the drivers onboarding. It was a series of 8. Theres 2 available in my Vimeo account. Take a peek!
Exploring and learning
By sometime, Rapiddo started to cool things down a bit. That's because, I guess, the iFood deal was starting to get closer and closer. Normal employees, like me, weren't aware of this. But, in the mean time, we started to dug deep into more problems we had in regards to the driver fleet. And these problems really took me off in advantage when in iFood, because they were identical. We had so much trouble trying to have a stable supply showing to take the orders. Because of that, we started to come up with ways to better enhance our promotion, the main call-out mechanism, flow in the app.
That, unfortunately, didn't pan out because the deal was close to happening. But the lesson I take from my experience at Rapiddo is to be really creative. When you set out for yourself a constraint as hard as not much money, you need to think the possibilites with the resources at hand. That's when we started to have interesting conversation about what we, as an almost product team, wanted to do. Like, vision wide. And that started to create an alignment that was special by that time.
We explored a lot of stuff at Rapiddo and those times were too special. I met people who I hold close to me to this day and I'm very happy to have had the opportunity of tackling problems over there. I didn't have a clue, before joining, that it'd be that cool.