CallDobi is a location based mobile app on laundry service in Malaysia.The centerpiece of this app will be the fellow Malaysian people who will be the main users of the app as well. People will be able to download this app from both of the world renowned platforms i.e. from Android(Google Play) and IOS(Apple Store) platforms. After downloading and installing the app, a registered person can knock CallDobi to pick his/her laundry at any required time and at any place, CallDobi pickup person will be there right at the doorsteps within ten minutes to collect their laundry!The person will also be inserting all the details of the laundry into the app simultaneously as well!
The users are also given the upper hand to view the status of their laundry through his/her CallDobi app. After all the processing being done, CallDobi delivery person will be there with the newly pristine laundry at the doorsteps of the users! and they wouldn't even need to pay for the pick up and delivery service as its completely free of charge!!
Since, the client didn’t have any existing product and they were not sure how their idea would work, we thought Design Sprint methodology would be the best solution to validate their idea within a short period of time. We were super excited because as a product idea CallDobi was very challenging in terms of features. Though, it had a couple of technical obstacles as well as physical. We had decided to run Design Sprint for each feature.
As per Design Sprint methodology, we needed participants and therefore, we invited some of their company employees who are directly connected to the CallDobi project and they are: Founder, Head of marketing, Account manager. From our end, we selected one UX expert (myself), Team lead of product, Copywriter, Product Owner. In total 7 people participated in our first Design Sprint.
According to their concept there were a couple of challenges. Some of the major challenges were:
We all came on time in the morning and started our first day of Design Sprint along with coffee. According to Design Sprint methodology, someone from the group has to play the role of “Facilitator”. We made their founder the facilitator since he was the person who came up with the CallDobi idea. He knew most of the story and he knew what he wanted. He explained the whole project idea and also explained why he thinks CallDobi would help people’s daily busy lives.
According to the facilitator’s project concept, we created a quick usermap of CallDobi user journey.
User will open CallDobi app and send a request to collect his/her laundry. Users will be able to set a specific time frame for collecting laundry.
A person from CallDobi will get notified that someone sent a pickup request. He/she will accept that request. CallDobi person will reach the user's place in time and collect all the laundry. After collecting Calldobi update the app status.
Users will get a notification on their app that all of their laundry has been collected. Also, they will see the detail cost and expected delivery time. Users will be able to see the status of their laundry on their app.
CallDobi will drop all the laundry in the CallDobi washing factory and will update the status.
All laundries will be washed in CallDobi washing factory and after that all items will be fry and iron. Each stage will update order status.
CallDobi will deliver all laundries to the user's doorsteps and after update delivery status.
Users will pay through the CallDobi app.
Find out a quickest and reasonable solution for picking up laundry and deliver them to the user’s door steps.
Now at this stage we asked our queries to everyone as much as possible about the project and at the end of this stage, the facilitator and the decider (Team lead of product) prioritize all the questions. Here are prioritised questionnaires.
Collecting varieties of clothes and tracking individual items and providing real time status to the user.
This was the main big problem. We clearly understood what the problem is. Now we have a goal and we need to solve that.
This is the stage where we all have participated. Based on the prioritised questionnaires, we all did quick hand sketches and presented our concept/solutions one by one to the team. The decider and the facilitator picked one of the solutions out of all those solutions. This is the chosen solution:
TNow it was my job to convert that sketch into an interactive prototype. It took me the whole day to make it interactive. For the prototype I used the Flinto app.
We invited 14 random people from different sectors to validate our design concept for the CallDobi project. We divided them into 2 groups.
We provided our prototypes to them and we observed their every pain and gain during the prototype journey. We found so many pros and cons from them. Some of the major points are:
It takes time to enter info of each item manually in the app during pickup
Yes, this was the only problem we couldn't solve at the beginning. Letter, we had another Design Sprint to solve this big problem and we solved that successfully. We introduced “Barcode” along with a barcode reader machine. And this idea solved this problem like a charm.
After validating the prototype, we started designing the main mockup and here are some outcomes.
Parallely, we also started to design and develop a functional Design System for CallDobi project.
During CallDobi design and development I have learned a lot. The first thing is with the help of Design Sprint you can validate not only a digital product but also you can validate a physical product. For example Bar code along with the bar code scanning device was the conventional decision.
At the beginning, we didn't invite any engineer to any of our Design Sprint process. Because of this mistake, we faced technical issues during the development phase. If we had involved them in the early stage then we would not have compromised any features.