Senior product designer, Mumbai. I untangle healthcare, AI and complex B2B software until they feel simple and elegant.
Complicated software doesn’t have to feel complicated. I find the part that matters and make it obvious.
If I had to explain my job to a five-year-old: imagine a big box of tangled wires. Everyone’s scared to touch it. I’m the person who sits down with the box, finds the one wire that actually matters, and lays the rest out so anyone can plug things in without thinking. I do that with health records that live in ten places, money apps people are nervous to use, and AI that needs to say what it just did. Find the thing that matters. Make it obvious. Take away everything that was only there to make you nervous.
Four things I’m proud of: an AI layer inside a low-code builder, a design system any enterprise can make its own, a money-transfer app that people actually finished using, and a health record that belongs to the patient.
04Why were people abandoning money transfers halfway?TanggApp, remittance appLeadershipFintechResearchAccessibilityProblemPeople started money transfers and didn’t finish them. Onboarding leaked.What I didRedesigned send, KYC and onboarding, tested with real senders in two countries.OutcomeTransactions doubled. Activation up 37%. WCAG from 50% to 90%.Coming soon, stay tuned!
I like the problems that have too many people in them.
Almost ten years of B2B product design across fintech, healthcare, logistics and developer tools. Right now I’m designing the AI side of a low-code platform at WaveMaker.
The work I’m best at has lots of stakeholders and messy data. Care split across doctors. Money crossing borders. AI that has to explain what it just did.
I prototype in code, HTML/CSS and React, because a team reacts differently to something that moves.
Key changeBuilders see what the AI changed, and preview it, before it lands.
ProblemBuilders couldn’t tell what the AI had done to their app, or why. Suggestions got ignored, chats got lost, and every AI surface looked different.
What I didDesigned the whole AI layer: suggestions as cards, a flat chat, agent status you can trust, and one design system under all of it.
Role: Senior Product Designer & ResearcherTimeframe: May 2024 – presentTeam: PMs and engineering leads across three time zones
5–7 min readAIDesign systemsPlatform UX
Context
The setup
WaveMaker is a low-code platform. Developers use it to build real apps fast, and they trust it because it doesn’t surprise them. Then AI arrived, and the question was how to put it inside a tool like that without breaking the trust. I lead design from discovery to shipped, and partner with product and engineering on the quarterly roadmap. So this wasn’t “make the AI screen pretty.” It was “decide what the AI is, in this product.”
Suggestions as cards: a priority, a size and three filters.
Chat navigation: three levels became one list and a filter.
Recognition
On the shortlist
WaveMaker’s AI-powered app generation platform, the product this case study is about, was named a finalist for Best AI Platform at The A.I. Awards 2026.
Please use the password I provided to view the project details. If you don’t have it, feel free to contact me and I’d be happy to walk you through it privately.
Full case study · Under NDA
WaveMaker AI
Case study · Design systems on a low-code platform
Design system and Style Workspace
I built WaveMaker’s first design system and the tool that themes it, so one library can become any enterprise’s brand, in Figma, in code, and in what WaveMaker AI generates.
TL;DR
4 → 1sprints to rebrand an app
100+apps themed across 4 enterprise clients
40–60hours of frontend time saved on a first build
−86%design–dev handoff issues
Key changeOne library, re-themed from a single hue, for people and for the AI.
ProblemWaveMaker had no shared design system, so every client app was styled by hand. Then clients tested V1 with their own systems, and their tokens didn’t fit our fixed set.
What I didBuilt the UI Kit on Material 3 (45+ components), then Style Workspace to theme it: four fixed buckets, three token tiers, the full chain on hover, and rules WaveMaker AI follows to build on-brand.
Role: Design system lead and PMTimeframe: May 2024 – October 2026Team: Eight people across design, engineering and AI
9–11 min readDesign systemsDesign tokensAI
Context
The setup
WaveMaker is a low-code platform. Enterprises use it to build their own internal and customer apps, often with our in-house product services team doing the build. Every one of those apps needs to look like the client, not like us.
WaveMaker had no shared design system. I built one on Material 3, then Style Workspace, the tool that themes it. When clients tested V1 with their own design systems, their tokens didn’t fit our fixed set, so 2.0 was rebuilt to hold each team’s own tokens.
Hear more stories!
Please use the password I provided to view the project details. If you don’t have it, feel free to contact me and I’d be happy to walk you through it privately.
Full case study · Under NDA
Design system and Style Workspace
Case study · Fintech, remittance
TanggApp
A global money-transfer app, redesigned end to end. Transactions doubled. Activation went up 37%.
TL;DR
2×transactions
+37%activation
90%WCAG compliance, up from 50%
−95%implementation errors
Key changeFees moved to the front of the send flow.
ProblemPeople started money transfers and didn’t finish them. Onboarding leaked. Accessibility sat at 50% WCAG, a legal problem for an app that moves money.
What I didRedesigned the send flow, KYC and onboarding, testing with real senders in two countries, and wired design to code with tokens.
Tangg is a remittance platform. People use it to send money home, and the amounts are small, frequent, and matter a lot. A failed transfer isn’t a bug. It’s rent. I directed the end-to-end UX on a six-month contract.
Mock · the send flow, before and after
Fees moved to the front. The whole thing works one-handed.
Mock · token pipeline from Figma to repo
One source of truth, two tools reading it.
Hear more stories!
Please use the password I provided to view the project details. If you don’t have it, feel free to contact me and I’d be happy to walk you through it privately.
Full case study · Under NDA
TanggApp
Case study · Healthcare · Personal project
VITO
A health record that belongs to the patient, not the hospital. So nothing gets lost between doctors.
TL;DR
~100research conversations
~60fellow patients
~17doctors
~25peers
BuiltA working demo of the patient and doctor apps, with a live clearance thread between two hospitals.
ProblemYour health history lives in pieces across every doctor you’ve seen. Tests get repeated, allergies get missed, and the patient carries a plastic folder.
What I didFlipped ownership to the patient: consent per provider, one timeline across hospitals, and a direct line between doctors so the patient stops being the messenger.
Role: Solo product designerContext: Personal projectTools: Figma, React prototypes built with Claude
7–8 min readHealthcareConsent designPrototyping
Try the live demo →Switch between Meera, Dr. Jain and Dr. Bhave to see one record from each side. Sample data only.
Context
The setup
VITO started during a healthcare UX certification. I kept going after it ended, because the gap is real. I kept running into it, personally and professionally, and it’s a systems problem pretending to be an app.
The people I designed for have serious or long-term conditions. Their care spans several specialists, often at different hospitals, and none of those systems talk to each other.
Research
About a hundred conversations, mostly in waiting rooms
I didn’t design this from a desk. I talked to fellow patients while we waited for appointments, to doctors, and to peers who had cared for someone through complex treatment. Then I read patient communities, survivor and caregiver blogs, and research on care coordination to see if the pattern held. It did.
~60fellow patients
~17doctors
~25peers and caregivers
What kept coming up
Patients act as system integrators. They carry history, reports and medication details between providers that don’t talk.
Good hospitals still run in silos. Clinical excellence doesn’t add up to coordinated care.
Coordination becomes a full-time job. Scheduling, labs, approvals and updates eat into recovery.
Gaps are a safety risk. Missing transplant status or immunosuppression details can lead to preventable errors.
Home data lives in notebooks. Symptoms, vitals and adherence never reach the whole care team.
What exists today
Aggregation got solved. Coordination didn’t.
The closest thing already ships on every iPhone. Apple Health Records pulls records from participating hospitals into one place, and it’s easier to use than earlier attempts. It still stops at collecting.
2%of people with several patient portals used a third-party app to combine their records PubMed Central
0ways for two doctors to talk to each other inside it
Having records in one place isn’t the gap. The doctors still can’t see each other. That became the brief.
For patients managing complex conditions across several specialists and hospitals, VITO is one record that follows the patient, open to every care team they choose.
Problem 01
The record belongs to the hospital
Every portal is built for the institution, with a patient login bolted on. The person with the most at stake has the least control.
How I solved it: I flipped ownership. The patient holds the record and connects every source: hospital portals, devices over Bluetooth, and scans of paper reports. It works on a basic smartphone, because many patients don’t have the latest one.
Meera connects every source herself: hospital portals, devices and scanned reports.
Problem 02
A folder, not a story
Clinic by clinic, the history is a stack of unrelated PDFs. Finding “the last time this was checked” is a search, not a glance.
How I solved it: One timeline. Every visit, test and prescription on a single line across hospitals, filterable by type. Next to it, a daily view for vitals, medicines and symptoms. Anything Meera logs herself is labelled patient-reported, so a doctor always knows the source.
One timeline across hospitals, filterable by type.Vitals from devices, symptoms from Meera, each labelled by source.
Problem 03
All-or-nothing sharing
A second opinion meant handing over your entire history, or nothing.
How I solved it: The patient chooses the level for each doctor: full access, a summary of conditions, medicines and allergies, or specific documents. Access can end on a date, and can be removed at any time. Every view goes into an access log the patient can read.
Meera sees who has access to what, until when, and every view.
Problem 04
Doctors can’t talk to each other
This is the part existing tools skip, and where I spent the most time. I built the design around one real scenario: a transplant patient, Meera, who now needs cancer surgery at a different hospital.
Clinicians only: the platelet mismatch is flagged and settled between doctors. Meera can’t see this thread.
Dr. Jain, her gynae-oncologist, needs clearance from Dr. Bhave, her transplant doctor. Dr. Bhave clears her on condition that platelets are above 100K. Dr. Jain’s anaesthesia plan assumed 75K. In VITO, Dr. Jain spots the mismatch and asks in the thread. Dr. Bhave confirms one number, looking at the same labs.
Without VITO
Two teams at two hospitals disagree on a number. The patient finds out late, then spends a call or a few relaying between them while surgery waits.
With VITO
The doctors settle it in one thread, in real time. Meera’s treatment keeps moving, and she isn’t the messenger.
What Meera sees: “Your doctors are coordinating.” She knows where things stand, without the clinical back-and-forth.
Two conversations, two audiences:Care team holds Meera and every doctor treating her, so each doctor sees what the others told her and every question she asked. Clinicians only is where doctors align first, so she gets one clear answer instead of the debate and the cognitive load that comes with it.
Care team: Meera’s question, both doctors’ answers, and her clearance progress in plain language.
Steps for her, checks for them: pre-op checks belong to the doctors who order them. Meera only sees her own steps, like booking an appointment or uploading a report. The doctor ticks the check off once they’ve seen the result.
Shared pre-op checks. Each belongs to a doctor; Meera’s part is to book or upload.
Problem 05
Doctors couldn’t ask for just what they need
Doctors raised this in testing: how do I ask a current patient for the past records that matter to today’s treatment? Asking for everything is easy, but it isn’t fair to the patient.
How I solved it: a records request designed from all three sides.
The doctor asking picks a purpose, like surgical planning. VITO suggests the records that purpose needs, and each one carries a reason in plain words.
The patient deciding sees each record, why it’s needed and a one-line preview of what’s in it. Only the ones needed for care come pre-ticked, so the easy answer is the minimum. Counselling notes and genetic results are never shared unless she chooses to.
The doctor who already holds her data sees what’s been asked. Meera can ask him before she decides, in the care team thread.
What Meera sees: each record, why it’s needed and what’s in it. Only what’s needed comes pre-ticked.
Dr. Jain picks a purpose; VITO suggests the records it needs.What Dr. Jain gets: only what Meera approved.
Dr. Bhave sees what Dr. Jain has and what she asked for.
When treatment ends: live access closes. The doctor keeps a de-identified case for reference and teaching: no name, contact details, ID numbers or exact dates, with the clinical course shown as days from the first consult. The hospital’s own medical record stays under its own rules.
After treatment: a de-identified case, with dates turned into days and identifiers removed.
Key decisions
The calls that shaped everything else
Patient owns, doctors are invited
Ownership sounds like policy. It’s a design decision, and every screen after it changed because of it.
Status for patients, detail for doctors
The patient sees progress in plain language. Clinical messages stay between care teams.
Show where every number came from
Hospital labs, device readings and patient logs share one timeline, each with its source. AI-surfaced signals cite the records behind them.
Prototype in React, not just Figma
Medical data is dense. Real scrolling, grouping and state changes showed problems a static frame would hide.
Feedback
“How is this different from what’s out there?”
That was the first question in review, and the right one. My answer came straight from the research: VITO coordinates instead of only collecting, it works on any smartphone, and it follows the patient instead of one hospital.
“What you’re doing isn’t necessarily unique, but I like how you’re approaching it.”Reviewer feedback
Usability testing
I took it back to the people I’d researched with
I showed the prototype to the same peers, doctors and patients, many of them in waiting rooms, and watched them use it.
Doctors said
Finding a patient’s past data takes a lot of work, and it’s worst in emergencies, when the patient can’t tell them about an allergy or a pre-existing condition. VITO puts that in front of them.
Patients said
Uploading everything one by one and keeping it updated felt like a chore at first. Then they saw the upside: forget a scan or a test report at home, and it’s still on their phone.
What confused people
Everyone: how it all works, who pays for it, and whether this much personal data is safe.
Patients: the first dashboard had too much on it.
Doctors: how to ask a current patient for the past records that matter to today’s treatment.
What I changed
I worked the feedback in, made the flows simpler, and tested again.
Still open
Both groups asked about people without a smartphone or internet, people who aren’t comfortable with tech, and people who can’t use an app because of a disability. I haven’t solved these yet. A record that only works for the well-connected leaves out the patients who struggle most.
Looking back
What I’d do differently
Talk to more clinicians earlier. I designed for the patient first, which was the right call, but the provider side would have been sharper with a few more conversations before I opened Figma.
Next, I’d work on the questions I left open: access without a smartphone or internet, and for people with disabilities or little experience with tech. Then I’d sit with clinicians on the clearance flow, and design the AI layer properly, so a doctor can always see why something was flagged.
Full case study · Under NDA
VITO
Wanna take Coco and Jojo on a bizarre little adventure? Click around and find out.
About me
Hi, I’m Prajnya.
Senior product designer. Almost ten years in B2B. I like the problems that have too many people in them.
The short version
I design products for fintech, healthcare, logistics and developer tools. Right now that means the AI side of a low-code platform at WaveMaker, where I lead design from discovery to shipped and help set the roadmap with product and engineering.
Before that I was the designer who also built the thing. Four years as a no-code developer and UX designer, which is why I still prototype in code and why engineers tend to like working with me. I know what “just a small change” costs.
How I work
Prototype in code. HTML/CSS and React. A team reacts differently to something that moves. At WaveMaker it cut dev back-and-forth by 86%.
Map the system before the screen. Stakeholders, data, failure points. Then the interface. In healthcare especially, the data model is the design.
Workshops, early. I facilitate design thinking sessions in Miro and FigJam across time zones. Every good decision I’ve made at work traces back to a room where people disagreed out loud.
Say the uncomfortable thing on day two. A review that surfaces the real constraint early beats a polished deck three weeks later.
Long focused blocks. I do my best thinking in deep-work sessions, not in scattered half-hours. I plan my week around that.
Where I’ve worked
WaveMakerSenior Product Designer & Researcher · May 2024 – presentLead the design lifecycle for the low-code platform. Co-own the company-wide design system. AI suggestions, AI chat, workshops across three time zones. Platform named finalist for Best AI Platform, The A.I. Awards 2026.
TanggSenior Product Designer & Researcher, contract · Sept 2024 – Mar 2025End-to-end UX for a global remittance app. Remote usability tests in the Philippines and the US. Transactions doubled, activation up 37%, WCAG compliance from 50% to 90%.
India IndexSenior UX/UI Designer & Researcher · Sept 2023 – Feb 2024UX research and design for a B2B sourcing platform for US–India trade. Usability testing lifted engagement 25%.
GrandVision, via Wise AnalyticsUX/UI Designer & Data Visualization Engineer · Jul 2022 – May 2023Design sprints, A/B testing and usability studies for analytics products.
Flow of Work CoNo-Code Developer & UX/UI Designer · Sept 2021 – Jul 2022Kept the design library honest and worked with developers on accessibility.
Design off the BoatNo-Code Developer & UX/UI Designer · Mar 2020 – Aug 2021Workshops with engineers, user research, personas, wireframes to shipped.
TechfluxNo-Code Developer, UX Designer & Project Manager · Mar 2017 – Mar 2020Ran ideation workshops with clients, managed delivery end to end, mentored new team members on no-code.
Education
UX/UI Design, MIT Institute of Design, Pune. 2022–2023.
B.E. Computer Science and Engineering, GIT Belgaum. 2013–2017.
Started an AI/ML programme at IIT Madras in 2021 and left. No regrets, it told me I wanted to design the thing, not train it.
Based in Mumbai, with two cats and about eighteen cobalt blue glass mugs. I draw, I take photographs, I cook and film it, and I read whole series at a time. All of that is on the Off the clock page →
Practical things
Remote first. I do my best work remotely, and I’m always happy to talk about what works for your team.
Mumbai, IST. Comfortable working across US and European hours.
Looking for senior product design roles, ideally in healthcare or AI.
Wanna take Coco and Jojo on a bizarre little adventure? Click around and find out.
Off the clock
What I make when nobody’s asking.
Drawings, photographs, food, and the books I keep coming back to.
Illustration
Pen, paper, Procreate, and the occasional thing that moves. I draw the way I design: get the structure right first, then let the light do the work.
Wings within wingsBallpoint pen, sketchbookMidnight familiarDigital, ProcreateLiquid gazeDigital painting
Motion
RoséMotion, kinetic typeOne heck of a comebackInk, for Daniel Ricciardo’s return to F1aDigital, letterform studyMarginsPen, in a work notebook. The to-do list stayed.
NesquikMotion study, unofficial. Wobbly lettering to bottle.
Photography
I chase light and shadow. Most of what I shoot is on my phone, in the ten minutes when the sky is doing something worth stopping for.
The city across the waterMumbai, just after sunsetOne set of footprintsThe shore, early eveningBefore it breaksHeadland, low lightLight, breaking through IOn the way somewhereSill, sunset, a murder mysteryThe Fury, and my glassesRed, and a half-written pageA café, a slow afternoonThe city, through a cab windowMumbai, a grey eveningCheers to the pink hourSunset, from somewhere high upLight, breaking through IISame habit, different daySalad, apparentlyGarden patrolSupervisor on dutyWatching me, from the wallOff the clock, literallyAn afternoon napThe last CliftonThis Was a Man, on the sandWritten in sandBefore the tide read it
Food
Food is how I say I love you. My kitchen never stays in one place for long. I cook, style and film it as @my_culinary_journey_.
KhottoIdli steamed in jackfruit-leaf cups, served on brass with sambar and chutney.Mango sticky riceThai, with the mango fanned into a rose. Sesame, crisp mung beans, coconut cream.Neapolitan-style pizzaLeopard-spotted crust, blistered peppers, and too many green chillies on purpose.Pani puri, the whole spreadMint-lemon pani, spiced potato, boondi, and more puris than anyone needs.Gnocchi al fornoSoft gnocchi, a slow tomato sauce, pools of mozzarella, a tangle of microgreens.Tandoori chickenCharred at the edges, with green chutney and a pile of onions.Stuffed shellsConchiglie with ricotta and spinach, baked in tomato sauce.Pistachio baklava rollsRolled, not layered, and buried in pistachio.Double chocolate loafTwo kinds of chocolate chips, because choosing is hard.
Books
I’ll read anything. Honestly, it’s the act of reading I love most: the world going quiet while I’m somewhere else. But once a writer earns my trust, I want the whole arc, all of it, in order.
The Clifton ChroniclesJeffrey Archer · 7 books
Seven books, one family, most of a century. Archer ends every chapter on a hinge, and I have lost entire nights to “just one more.”
Only Time Will Tell2011
The Sins of the Father2012
Best Kept Secret2013
Be Careful What You Wish For2014
Mightier Than the Sword2015
Cometh the Hour2016
This Was a Man2016
William WarwickJeffrey Archer · 7 books
The detective the Cliftons were reading about, grown into his own series. Archer and John Grisham are my comfort shelf: clever plots, clean pacing, and somebody always getting away with something, until they don’t.
Nothing Ventured2019
Hidden in Plain Sight2020
Turn a Blind Eye2021
Over My Dead Body2021
Next in Line2022
Traitors Gate2023
An Eye for an Eye2024
Harry PotterJ.K. Rowling · 7 books
I grew up alongside this story, at an age when my imagination had no boundaries. It was a new kind of read for me, one that helped my sense of identity take shape and taught me to sit with ambivalence. Life, it turns out, is shades of grey, and sometimes people act out of their circumstances rather than what they believe in.
Philosopher’s Stone1997
Chamber of Secrets1998
Prisoner of Azkaban1999
Goblet of Fire2000
Order of the Phoenix2003
Half-Blood Prince2005
Deathly Hallows2007
Middle-earthJ.R.R. Tolkien · 4 books
You don’t have to be big, strong or powerful to change the world. The hobbits saved everyone just by being brave and stubborn, and that taught me that growth only comes after you face the fear. Sam never gave up on Frodo, even when things got terrifying, and I’m so glad to have my own Samwise. Wanting control over others ruins who you are, while mercy, even toward the difficult ones, can turn everything around. Kindness is always a choice, and even on the days you feel small, your everyday choices matter.
The Hobbit1937
The Fellowship of the Ring1954
The Two Towers1954
The Return of the King1955
Oz, from both sidesL. Frank Baum, then Gregory Maguire · 5 books
Baum’s Oz was pure wonder: a yellow road, a few odd friends, and a wizard who turned out to be just a man behind a curtain. Then Maguire turned it inside out and told it from the side of the girl everyone had already decided was wicked. Together they taught me that the story depends on who’s telling it, and that the “villain” usually had reasons nobody bothered to ask about. I try to remember that every time a user gets called “difficult.”
The Wonderful Wizard of Oz1900
Wicked1995
Son of a Witch2005
A Lion Among Men2008
Out of Oz2011
Holly JacksonHolly Jackson · 6 books
Pip is a teenager who refuses to accept the official version of events. She just keeps asking questions, making lists and following the evidence until the truth gives way, which is the most satisfying kind of stubborn. The books are also honest about what chasing the truth costs her, and I respected that. I read everything Holly Jackson has written because of Pip.
A Good Girl’s Guide to Murder2019
Good Girl, Bad Blood2020
As Good As Dead2021
Kill Joy2021
Five Survive2022
The Reappearance of Rachel Price2024
Andy WeirAndy Weir · 3 books
I watched Project Hail Mary before I even knew it was a book, and Rocky made me cry. Then I noticed the pattern: a lone scientist, an impossible situation, humour as a coping mechanism, and problems solved one small experiment at a time. Which is, honestly, how I like to design.
The Martian2011
Artemis2017
Project Hail Mary2021
Wuthering HeightsEmily Brontë · 1847
The one standalone on this shelf, and the hardest read. Almost nobody in it is likeable, and that’s the point: it’s about what obsession, pride and old wounds do to people when nobody lets them heal. Beautiful and exhausting in the same breath.
Finalist, Best AI PlatformThe A.I. Awards 2026 · shortlisted alongside EY, PagerDuty and BMC Software
