Dynamic location of donor | Up to date databases | Data privacy | Transparent communication | Intuitive UI | |
---|---|---|---|---|---|
Donor2Donor | ✅ | ✅ | ❌ | ❌ | ❌ |
BloodDonorMobile | ✅ | ❌ | ❌ | ❌ | ❌ |
eBloodBank Mobile | ❌ | ❌ | ✅ | ❌ | ❌ |
Infinity Blood | ❌ | ❌ | ❌ | ❌ | ❌ |
OurBlood | ❌ | ❌ | ❌ | ❌ | ❌ |
BloodLink | ✅ | ✅ | ✅ | ✅ | ✅ |
A detailed explanation of the problems with the current system are below:
After compiling all this research onto a miro board and showcasing the findings to the product owners, I started creating different personas that may use the system and the particular user scenarios in which these users may encounter using the system.
After realizing what solution would bring the most value for my users, I started creating an app navigation diagram on how will the user be able to make requests for blood or even donate blood to a nearby blood bank.
I created the UI kit that reflects BloodLink's brand adjectives, since it helps users get linked to a relevant blood supply or donor.
Due to my lack of experience in UX design I had jumped directly into the UI without creating any sketches or wireframes which was difficult to visualize. The entire UI can be found here : Click here!
I tested the first version of the prototype with 5 users to determine the necessary revisions to make the overall experience quick and pleasant. Here are some outtakes.
Main points that were discovered during the tests and addressed in the iteration:
Due to my lack of subject knowledge in the field of medicine and lack of availability of medical
professionals, I had to go through a large number of medical records and books to understand what
conditions are required if a person wishes to donate blood and based on that create the structure of the
database in the backend. I had to learn compatibility of different blood types to ensure a person
requesting for blood is able to find only compatible donors because most users may not be aware of blood
compatibility issues which may be fatal for the recipient.
Learnings: It taught me the value of medicine and healthcare professionals and how crucial
subject knowledge is in order to ensure the right experience for the user. It introduced me to incorporating Empathy in my design.
As mentioned above, India does look at a blood scarcity every year and unfortunately the gap is only widening. For this reason, it was difficult to find people who had used these systems before and had registered their information on the systems because a lot of the data had become outdated. Hence, linking the database with the Aadhar system will ensure that all fields are up to date.
Once the app was launched to the public it was hard to keep up with the medical examinations of people who wished to become donors. The scaling part of this project was not well thought out since I was working alone and I put in a fair amount of time on the product rather than the actual growth of the product.
This was a very hectic end-to-end project since I was working solo from inception to launch without much
feedback and guidance. My lack of awareness of design thinking can be seen through the project gaps such as
not testing the current systems with actual users and not creating any sketches and jumping straight into the
UI aspect and not properly testing it before launch which meant a lot of crashes and bug fixes.
Overall the app is doing what is supposed to do with further improvements and changes since it has now been
handed over to an entire software development team who keep track of the bugs and issues. Journey wise, the
app remains mostly the same which is a good sign that people are not having complaints with it.