SAARTHI

Project: India's first grassroots hemophilia care assistant

Description: Saarthi is a lightweight internal platform helping NGO workers track, coordinate, and respond to hemophilia care needs in low-tech areas.

Org: Hemophilia Federation — NGO with 1000+ field workers

Team: 1 PM 4 Developer 1 Designer (me!)

Timeline: September 2022 – March 2023

Role: Product Designer

(Research → IA → UX → UI → Prototyping → Testing)

Starting with a thank you

I appreciate you taking the time to review this case study. I chose this example because I feel it demonstrates:

  • My ability to work fast on a high-visibility project

  • My ability to navigate collaborations and negotations with multiple team members and stakeholders

  • My ability to work within confines of technical limitations

Headquarters

HFI, Delhi , india

Founded

1983

Industry

NGO

Skills

UX Research
Systems Thinking
Prototyping
Information Architecture
Usability Testing
Localisation
Designing for Low-Tech Environments

Company size

1,000+

Overview

What if we could bring structure, speed, and confidence to hemophilia care in India’s most underserved regions?

Hemophilia care in rural India is a high-stakes, low-infrastructure reality.
Information lives across WhatsApp chats, paper diaries, phone trees, or memory. Emergencies often require 20+ minutes of manual coordination. There was no lightweight, offline-friendly digital tool that matched the real workflows of NGO field volunteers.

This gap — between complex hospital systems and the everyday tools of grassroots workers — became the starting point for Saarthi.

Solution

A SaaS, offline-first care assistant built for NGO workers managing hemophilia in remote regions.

✔ Track infusions in <60 seconds
✔ View a complete patient profile at a glance
✔ Trigger emergency alerts with GPS
✔ Generate care reports automatically
✔ Support low literacy with icons, colors, and simple flows
✔ Work offline, sync when connected

Outcomes

Saarthi has been deployed across 3 states, supporting 150+ rural hemophilia camps and thousands of volunteer–patient interactions.

Key Impact Highlights

  • 84% faster emergency coordination (20+ min → <180 seconds)

  • 60+ seconds infusion logging (previously 5–7 mins)

  • 2× more accurate patient data due to consolidated histories

  • Higher volunteer confidence in tracking care and reporting

Initial observations and prototypes

My first week began with field visits.
I shadowed 12 NGO volunteers across 5 hemophilia camps in Rajasthan and Delhi.

What I saw:

  • Records scattered across paper, WhatsApp, and memory

  • No standardized workflow

  • Volunteers improvising with voice notes, sticky notes, phone calls

  • Major reliance on personal judgment rather than system support

  • Emergency response was slow and chaotic

The gap was obvious:
Existing health systems were built for hospitals — not for grassroots India.

Becoming My Users

I didn’t know much about hemophilia when I joined.
So I learned — deeply.

I assisted volunteers in logging an infusion manually.
It took 5+ minutes, multiple fields, and a lot of friction.
Seeing the anxiety around “missing something important” completely reframed the problem for me.

I didn’t want to design for volunteers.
I wanted to design with them.

I didn’t know much about hemophilia..
So I learned…

Pain Points

1. Tools weren’t designed for them

Hospital systems were English-heavy, complex, and required training volunteers never received.

2. Information was disconnected

Infusion history → in diaries
Emergency notes → on WhatsApp
Patient details → in memory

No single source of truth.

3. Emergency response was slow

Help required manually calling 4–6 people in a chain.
Critical minutes were lost.

Field Insights

During shadowing, one volunteer said:

If the patient bleeds, I just start making calls… whoever picks up first decides the plan.”

This wasn’t a system.
This was improvisation.

That moment became our design anchor.

Market & Context Research

Hospital Systems

Too complex. Internet dependent.

NGO Workflows

Paper-based, verbal, unpredictable.

Training

Irregular, in-person only, not digitization-ready.

Connectivity

Unreliable, 3G at best.

Design had to bend to the ground reality, not the other way around.

Hospital Systems

Too complex. Internet dependent.

NGO Workflows

Paper-based, verbal, unpredictable.

Training

Irregular, in-person only, not digitisation -ready.

Connectivity

Unreliable, 3G at best.

Design had to bend to the ground reality, not the other way around.

Existing Hemophilia Care Tool Analysis

We studied existing hospital systems and digital health apps. All had one thing in common: They weren’t designed for low-connectivity or low-literacy environments

Solution Exploration

We asked:

What if we created a mobile assistant that worked offline and in local languages — with clear, tappable cards and one-tap emergency actions?

We asked:

From that spark, Initial wire framing began.

We prioritized:

  • Icon + label structure

  • Offline data storage + sync

  • Local-language UI (Hindi + Tamil for MVP)

Design Process

Discover

Research Methods

  • Field shadowing

  • Diary studies

  • Contextual inquiry

  • Journey mapping

  • IA audits of existing workflows

  • Competitor analysis (hospital systems, NGO tools)

What emerged

A system wasn’t needed.
A guide was.

Something that could support volunteers in real time.

Define

How might we…

  • simplify infusion logging so volunteers don’t hesitate?

  • make emergency response as simple as a tap?

  • unify scattered patient information into one clear panel?

  • create a system that works offline, on low-tech phones?

  • support multiple languages and literacy levels?

This phase produced:

  • Problem statements

  • Persona variants (Volunteer, Supervisor, Patient Family)

  • A new IA prioritizing primary → secondary information

  • A simpler, more visual layout

Develop

(Early Explorations)

Usability Testing & Iteration

We tested clickable prototypes in Hindi and Tamil with 150+ NGO workers (literacy range: class 6 to graduate-level).

Top insights that shaped the product:

Insight What We Changed
Button positions were confusing Re-aligned based on RTL
“Donate” felt ambiguous Replaced to “Donate” with Blue 500
Users hesitated with multi-step forms Combined fields into tappable cards


Key UX Decisions (and Why)

Infusion Tracking – From 5 mins to < 60 secs

Before: Volunteers filled long paper forms, then called supervisors to update records
After: Tap “Log Infusion” → Select preloaded factor → Auto-filled timestamp & ID

Emergency Flow – One Tap, Real Impact

Before: Phone trees, form filling, panic
After: Tap “Alert” → GPS locates patient → Notifies ambulance + auto-generated report sent via SMS

Why this mattered ?

  • 84% faster incident response

  • Critical in areas with no stable internet


Starting With The Patient Summary

We designed the profile to be:

  • Color-coded by severity (mild/moderate/severe)

  • Tappable summary tiles for infusion frequency, last visit, aid status

  • Minimal text + icon-based cues

MVP 1

Core Modules

After a design jam and journey mapping session, I distilled the tool into

6 field-friendly modules:

🔹 Patient Profiles – Demographics, diagnosis, severity tag, assigned center

🔹 Infusion Log – Quick tap to log dose, factor batch, time, admin method

🔹 Emergency Assist – One-tap alert with GPS + auto-notify coordinator

🔹 Aid & Insurance – Pre-filled PM-JAY forms, Aadhar uploads, real-time status

🔹 Volunteer Log – Route planner, visit checklists, visit time

🔹 Reports – Auto-generated PDFs of treatment status and vial inventory


Deliver

Emergency-First
Onboarding (Skip Login)

What it is: A giant Emergency button that lets volunteers trigger help without logging in.


Simple Login

What it is: Familiar Login Approach

Patient Profile
(Multilingual + Role-Aware)

What it is: A clean, comprehensive “at-a-glance” patient overview.

Landing Screen With Emergency Priority

Why this matters: Volunteers often share phones, forget passwords, or rush to help during a bleed We removed the authentication barrier completely in emergencies.


Patient Profile
Clean Hierarchy With Editable Cards (Center Panel)

This is the heart of Saarthi.
The video beautifully captures how each middle-section card is modular, editable, and adaptive.

Downloadable Patient
Profile

A one-tap, auto-generated medical summary designed for rural connectivity and cross-center coordination.

Downloadable Patient History

A downloadable report that converts a patient’s entire medical history into a clean, visual bar-graph format, This feature automatically transforms raw patient data into clear clinical insights using simple charts volunteers and doctors can understand immediately.

Patient–Hospital Tracking with Doctor Availability

A simple dotted-line visual map that shows exactly who is connected to the patient — and who is available right now.


Minimal Viable Product

Dashboard

“ Saarthi isn't just a system—it's a reliable partner in the journey of hemophilia care, bringing confidence and coordination to the people who need it most.. ”

For full detailed journey view this on a desktop ….

~Pawan

CEO,| Hemophilia Federation India

Final Design

We kept the interface extremely simple:

  • Color-coded tiles based on severity

  • Easy tap-to-log infusions

  • GPS-enabled Emergency Assist

  • Clear categories for Aid, Insurance, Visits, and Reports

Set severity in patient profile
Log infusions in 60 seconds
Send emergency alert in one tap

Reflections

Designing for constraint is liberating
What seemed like limitations (low-end phones, no Wifi) helped us strip things to the essential and users loved the simplicity.

Localisation isn’t just translation
Icons, field names, even button positions mattered. We tested designs in Hindi and Tamil, which brought huge usability insights.

Advocating for design in NGOs
Working with an operations-led team meant pushing for design-led decisions. Sharing usability test recordings helped win buy-in.


Enter Password