This case study describes creating the first version of a digital healthcare product from scratch with minimum effort and maximum effectiveness.

In the process, I was involved with two more teammates: the client who played the role of the Product Manager and the Full-Stack Engineer, who did a great job operating all the technical aspects. Some of the titles, diagnoses, and names in this study were changed due to the NDA contract and data sensitivity, but the UX & design process did not blur.

Blood Donation Tracker

Mobile screen displaying an app for a blood donation organization drive with a graphic of a hand and a heart, and a blue button labeled 'Lets Save a life'.
Mobile app screen showing a blood donation profile for Ethan Carter with blood type O+ and a donor ID, an upcoming donation date, and icons for Home, My Blood, Appointments, and Profile.

The Results

As a result, we’ve launched the demo version in 2 weeks as a team of 3 people, had more than 15 products compared, 4 flows tested after analyzing 1500+ interviews.

  • User Personas based on the qualitative and quantitive research results

  • Userflows, wireframing, user testing

  • UX Strategy for the future product implementation

  • UI concept for mobile App

  • Market research and benchmarking

What’s been
done:

UI Design and Prototyping

Team : 9 member

Duration: 1.5 Month

My Role : UI U X Design and Prototyping

Tools & Process: UI/ UX Design / Dev offs/ Navigation bar Layouts / Labeling/ LO-FI, HI-FI Wireframing/ Prototyping. UX Research / User Testing

A Quick Peek Into the Solution

We launched a functional MVP of Blood Donation Tracker, with:

  • Fully responsive web-based platform built around user-centered design

  • Donor login, onboarding, history tracker, and virtual rank system

  • Admin dashboard with role-based task flows for managing blood types, camps, and pathology centers

  • Unified design system for consistency across web/mobile and easier engineering handoff

  • WCAG 2.1 compliant accessible UI

  • Performance-monitored prototype backed with analytics insights for ongoing iteration

Understanding the Problem

We conducted discovery sessions, user interviews, and behavioral mapping to understand:

  • Why young users don’t return after their first donation

  • What prevents hospitals from digitizing their records

  • How to make the donor feel emotionally connected to their act

The common threads:

  • "I don’t know if my blood was used."

  • "I didn’t get any kind of update or reward."

  • "We use Excel sheets and handwritten logs."

This pointed to the need for a transparent, intuitive, and motivating experience for both sides.

Infographic showing various uses of donated blood, including 34% for cancer patients and blood diseases, 19% for patients with anemia, 18% for surgery, 13% for other medical problems like heart, liver, and kidney, 10% for orthopedic issues, 4% for obstetrics, and 2% for trauma and road accidents.

Market Reality

Most existing donation platforms are outdated, hard to navigate, or designed only for logistics teams. Our research compared 5 commonly used blood donation apps and platforms.

How We Outperformed:

  • Only platform with real-time reward/rank system

  • Designed for both donor and admin roles with tailored UX

  • Included emotional feedback: “your blood helped X person”

  • Compliant with WCAG 2.1 and EMR/FDA guidelines

  • Delivered faster workflows and a component-based design system

Table comparing various blood donation platforms, listing key features such as appointment booking, donor profiles, request tracking, and camp info, along with identified gaps like lack of donation tracking, rigid UI, and no dashboards.

Target Audience:

  • Primary Archetype: The Conscious First-Time Donor

    • Age: 22 | Gender: Female | Location: Metro City

    • Motivation: Wants to contribute meaningfully and socially

    • Frustration: Doesn’t get any follow-up or update after donating

    • Goal: Wants to donate regularly and feel part of something impactful

A woman at a hospital front desk speaking to a man on the phone. The background features a large blood donation logo and a sign about blood donation.
  • Tertiary Archetype: Mr. Rajan (The Admin Operator)

    • Age: 38 | Gender: Male | Location: Government Blood Bank

    • Motivation: Needs a clean, manageable system for large data

    • Frustration: Manual entries, Excel errors, no real-time search

    • Goal: Streamline data, reduce error, and speed up processing

Type of Users

A healthcare professional in red scrubs draws blood from a young man at a medical facility.

Secondary Archetype: Neha (The Willing but Uninformed Donor)

  • Age: 24 | Gender: Female | Location: Tier-2 City

  • Motivation: Has the will to donate and help others, especially during emergencies or drives

  • Frustration: Doesn't know where, how, or when to donate blood lacks guidance or access to verified information

  • Goal: Needs a trustworthy, step-by-step system that tells her where to go, when she's eligible, and what to do before and after donation

A man donating blood at a donation center, with a woman seated nearby. A red banner with white text about donating blood, plasma, and stem cells hangs on the wall.

Research & Key Findings

We conducted:

  • User surveys and interviews (n=256)

  • Competitive benchmarking (15 platforms)

  • Accessibility audits

  • Real-user scenario simulations

Findings:

  • 84% of users wanted to know where their blood went

  • 73% responded positively to gamified ranks

  • Admins completed critical workflows 25% faster

A woman writing on a wall covered with research papers, charts, and sticky notes.

Modules Designed

  1. Donor Onboarding (Email/Phone registration, password recovery)

  2. Blood Recipient ( Email/Phone registration, password recovery)

  3. Request & Search Panel (By blood group, urgency, hospital)

  4. Admin Controls (Add/View blood types, camps, pathology info)

  5. Analytics & Performance Metrics Impact (Donations vs. usage tracked)

Hand-drawn sketches and notes of a blood donation app interface on a whiteboard, including screens for login, home page, blood donor sketching, and blood recipient screening, with labeled sections for donation information, profile switching, schedule donation, and navigation icons.
Hand-drawn sketches and notes for a blood donor and recipient login system, including login screens with fields for mobile number, user name, password, and account creation options, along with handwritten instructions and explanations in red and purple ink.

Information Architecture

1. Hierarchical Relationships

  • Dashboard

    • Donor (Profile, Ranks, History)

    • Admin (Add, View, Search Modules)

2. Associative Relationships

  • Ranks ↔ Blood Type ↔ Location ↔ Time

  • Requests ↔ Donor history ↔ Admin logs

3. Dependency Relationships

  • Ranks and rewards depend on verified donation logs

  • Admin view is filtered by Search/Request modules

Diagram showing three types of relationship models: Hierarchical Relationships with nested modules, Associative Relationships with connected elements like buttons and forms, and Dependency Relationships illustrating how modules rely on each other. The diagram is titled "Visualizing Relationship" and includes explanations for each model type.
A hand-drawn diagram of a blood donor and blood recipient flowchart, including steps for login, donation scheduling, donation history, and matching donors with recipients, with colorful sticky notes and handwritten notes.

System Visualisation

  • UI designed using Figma, with responsive grids and a scalable component library

  • Final designs tested on both web and mobile via screen-share and clickable prototypes

  • Feedback captured via usability logs + emotion mapping

Team of people working on a design project at a desk with colorful sticky notes, sketches, a laptop screen displaying a diagram, and office supplies, including a potted plant and a clock.

Process Breakdown

  1. Brainstorm & Discovery

  2. Competitor & User Research

  3. Low-Fi Wireframing in Figma

  4. Mid-Fi Prototyping (Clickable)

  5. Usability Testing & Iteration

  6. Final UI Design + Developer Handoff

  7. Performance Setup & Rolloutg

Main Login Screen for Organization and if the user is Donor or Blood recipient he will have two different login screen

Hand-drawn diagrams and notes on white paper describing a blood donor and recipient login interface, including fields for username and password, and instructions for creating and logging into accounts via blood donor card or social media. Notes explain login options for donors and recipients, account creation, and organizational steps.

Low-Fi Wireframing in Figma

These are the final two main flows of our app donor tracking system and Blood Recipient System.

Low-Fi Wireframing For Navigation Bar

Main Navigation Bar (Visible to All Users):

Regardless of the user type, the main navigation bar includes:

  • Search: To quickly find blood types, donation centers, or user profiles.

  • Home: A personalized dashboard based on the user type.

  • Impact: Showcases how the platform and its users are creating positive change through blood donations and funding.

  • Notifications: Real-time updates on appointments, blood requests, or donation impact.

  • Profile: Access and manage personal account details.

Donor-Specific Navigation:

In addition to the main nav bar, donors have access to:

  • My Blood: A history of their donations, with details on how and where their blood was used.

  • Schedule Appointment: Allows them to book or manage upcoming donation slots.

This the Main Homepage of the app where you login and then if you want to donate or Require blood from “ From right corner click on Switch Profile Icon” then you can switch from Donors profile to Recipient Profile.

Hand-drawn diagram of a blood donor and recipient flow process, with multiple screens and steps in purple, black, and red ink.
Handwritten notes and sketches for a blood donation app with diagrams of mobile screens and descriptive instructions.
Hand-drawn diagram of a Blood Donation and Blood Recipients app interface, featuring main navigation, donation and recipient sections, and related icons.

Blood Recipient-Specific Navigation:

Alongside the main nav bar, blood recipients have:

  • Impact: A detailed view of how their blood purchases contribute to social initiatives (e.g., child education, foster care).

  • Blood Request Form: Submit and track requests for blood types.

Hi-Fi Wireframing in Figma

Flow 1

Donor Flow Summary:

The donor journey begins with logging in through the Donor Login screen.

  1. Schedule Donation:
    The donor selects a date, time, and location for their blood donation. Once scheduled, they are taken to a confirmation screen with an option to add it to their calendar.

  2. View Donation History:
    After confirmation, the donor is redirected to the "My Blood" page, where they can track past donations and see how often they've donated.

  3. Real Impact Stories:
    To encourage continued donations, the platform shares feedback from families who received their blood, showing exactly how it helped and who it impacted.

  4. Return to Home:
    The donor can return to the Home page at any time to begin a new action or explore more

Flow 2

Blood Recipient Flow Summary:

  1. Login:
    The user logs in through the Blood Recipient portal.

  2. Request Form:
    Fills out a form with patient details and required blood type.

  3. Match & Select Donor:
    The system shows matching donors, and the user selects one.

  4. Confirmation:
    A confirmation screen appears with the allocated donor and an option to thank them directly.

  5. Impact:
    Each blood unit costs $50, which is donated to causes like foster care and elderly homes—showing the user how their purchase is making a difference.

Testing Methodology

  • Participants: 256+ users (donors + admins)

  • Platform: Localhost prototype with Figma flows

  • Sessions: 1-on-1 guided tasks + surveys + feedback loops

  • Metrics Collected: SUS score, time-to-complete, feedback sentiment

Two young women working together at a desk with a laptop in a classroom or office setting.
A person wearing a green sweater, sitting with crossed legs, writing on a notebook with a red pen, and wearing rings and a silver bracelet.

Test Results

Quantitative

MetricResultOnboarding Completion93%Simulated Donations82%SUS Score78.6/100Would Use Again84%Admin Task Completion92%Design Task Efficiency+25% improvement

Qualitative

  • “Ranks made me feel appreciated.”

  • “This feels like something I’d check often.”

  • “Admin flow is cleaner than anything we’ve used.”

A graph on dotted paper shows trends in sucking behavior over time, with axes labeled 'Sucking' on the vertical and 'The Past' to 'The Future' on the horizontal, surrounded by pens and a ruler on a wooden desk.

Key Outcomes

  • 🧠 Improved UX task efficiency by 25%

  • 🚀 Accelerated design handoff speed by 30% through systemization

  • 🩸 Boosted re-engagement intent by 84% through emotional UI

  • ♿️ Complied with WCAG 2.1 for accessibility across user groups

  • 📋 Followed EMR/FDA principles for data compliance-readiness

Person with red painted fingernails writing the word 'Done' in blue marker on a pink sticky note.

Final Reflection

This wasn’t just about blood it was about emotion, trust, and action.

With limited time, we created a platform that elevated donor experience, streamlined operations, and laid the foundation for scalable public healthcare systems. The design didn’t just meet user expectations it reshaped them.

With cross-functional teamwork, system-level thinking, and user-centered care, we proved that healthcare UX can be both beautiful and deeply impactful.

Two people discussing in front of a whiteboard filled with sketches and notes. One person is holding a laptop and writing on the whiteboard with a marker, while the other is observing and wearing a smartwatch.

"Design is not just what it looks like. Design is how it works and how it makes you feel seen.