I design complex workflows for decisions that need to make sense.
My work spans clinician tools, access governance, explainable AI, financial recommendations, and public service interfaces. I turn dense systems into usable workflows without hiding the tradeoffs.
Experience
3+ years, shipped end to end
Practice
Research to implementation
Availability
Open to product design roles
Selected work
Every product here answers a question someone has to get right.
I like complex products. I make them easier to use.
Product and UX designer. The work is mostly healthcare, AI, financial tools, civic services, and enterprise software. I work from research through interaction and visual design, and I stay close to implementation so the idea survives the build.
Prakhar Jain · Product and UX designer
How I work
Six modes. One practice.
I work in six overlapping modes. The role changes with the problem, but the goal stays the same: make complexity easier to understand and act on.
01 · Product designer
Product designer
I connect user needs, product constraints, and interaction decisions into one coherent experience. I focus on the decisions the product must support, not only the screens it needs.
Product strategy
Interaction design
Prototyping
Workflow design
A shared system map turns scattered context into a product decision.
02 · Systems thinker
Systems thinker
I map relationships, dependencies, edge cases, and ownership before polishing an interface. Understanding the system makes the final experience clearer and more resilient.
Systems mapping
Information architecture
Complex workflows
Decision models
Systems mapping helps me see dependencies before I focus on interface details.
03 · Research led
Research
I use interviews, testing, synthesis, and critique to reduce uncertainty. Research is useful when it gives the team evidence they can act on.
User interviews
Usability testing
Synthesis
Validation
Observation becomes valuable when a team can use it.
04 · Visual storyteller
Visual storyteller
I use hierarchy, typography, motion, and narrative to make complex ideas easier to understand. Visual craft should clarify the product rather than decorate it.
Visual design
Motion
Hierarchy
Product storytelling
Hierarchy, typography, and narrative help complex product ideas scan clearly.
05 · Builder
Builder
I use prototypes, practical implementation, and AI assisted workflows to close the distance between an idea and a working experience.
Interactive prototyping
AI assisted implementation
Design systems
Product evaluation
MS Human Computer Interaction · Arizona State University.
06 · Teammate
Teammate
I work best with teams that make thinking visible, invite useful disagreement, and stay present with one another. Observation, shared context, and time beyond work help me collaborate with more patience and perspective.
Observation
Collaboration
Presence
Shared context
Shared context and open critique make collaboration more useful.
Beyond the pixels
Ask the questions after the interview.
The case studies show how I work. These answers are about what I am like to work with.
Because it sits where people, systems, and decisions meet. I like understanding a complicated situation, finding the part that matters, and giving a team something clear enough to build and challenge.
Workflow heavy products where the information is scattered, the stakes are real, and the answer cannot be reduced to one attractive screen. I enjoy making the system understandable without making it simplistic.
Sport, travel, learning, and time with people who do not speak in product language. Those parts of life keep me curious and stop the work from becoming the only lens I use.
I like the discipline of showing up prepared, asking for critique, and improving the next attempt. Sport made that rhythm familiar long before design did.
Structured but collaborative. I like making the problem visible early, sharing rough thinking, and tightening the work through evidence and useful disagreement.
How to build more of what I design. I am deepening AI assisted implementation, motion systems, and product evaluation so the distance between concept and working experience keeps getting smaller.
Still here?
You have seen the work. The rest is a conversation.
I like ambitious problems, direct feedback, and teams that care about getting the details right.
3 years shipping healthcare, enterprise SaaS, and AI products end to end. Lifted usability scores 20% and launched 40+ production screens to medical-grade standards. Prototypes in Claude Code rather than handing off static files.
Improved design review consistency across 200+ AI-generated product evaluations by assessing usability, visual hierarchy, interaction quality, and accessibility in each submission.
UX Developer
RVCO Lab, Arizona State University
Led end-to-end design for 3 research products, turning insights from 15+ user interviews into validated prototypes.
Grew usability scores by 20% with 20+ reusable Figma components for data-heavy interfaces.
UI/UX Designer
Welldoc Inc
Shipped 40+ screens to medical-grade UX standards by designing 3 health products, including an AI chatbot.
Unified the visual language across 3 products with an 80+ component design system used daily by 5 engineers.
Elevated patient-facing flows with 10+ Lottie-based micro-interactions and motion design.
UX Grader
Arizona State University
Raised the critique bar each semester by giving 80+ students structured feedback across 500+ design submissions on visual craft, interaction quality, research methodology, and accessibility.
UI/UX Designer
Alliant Infotech · Indore, India
Delivered high-fidelity UI across web and mobile for 3 B2B edtech platforms, owning the process end to end.
Boosted customer retention by 25% and cut support tickets by 15% by tying decisions to real user behavior.
Available for product design roles
Bring me the workflow, decision, or system that needs untangling.
Send a role, product problem, contract brief, or a simple hello. I’ll reply with context, availability, and the fastest next step.
No analytics, no cookies on the public site, and a contact form that never reaches a server. This page exists so you can check that rather than take my word for it.
Last reviewed 8 September 2026
What the site keeps
One thing: whether you chose light or dark. It lives in your browser under prakharux-appearance so the site looks the way you left it. It is never sent anywhere, and clearing your browser data removes it.
Cookies
None on the public site.
Analytics
None running.
Session storage
Not used.
Accounts
There is nothing to sign up for.
About that “no analytics”
The code does carry a small adapter written for a privacy-friendly analytics service, but it is switched off: no measurement script is loaded and no events leave the page. If that ever changes, this page changes with it.
The contact form
It does not send anything to a server, because there is no server to send it to. Pressing Send message opens your own email app with a draft addressed to me. What you type stays in your browser until you decide to send it. After that it is just an email.
Where the page comes from
Fonts, images and video are all served from this domain. No font service, no CDN, no embedded third-party players. Loading a page here contacts one place.
Leaving the site
A few links point outward: LinkedIn, the App Store, Figma, and the live prototypes. They open in a new tab. Once you are there you are on their terms and their privacy policy, not mine.
The password-protected case study
One case study is access-controlled because the work is under NDA. Entering the password sets a single session cookie so you are not asked again on every page; it expires after eight hours or when you clear your cookies. It holds no personal information.
Hosting
The site is hosted on Netlify, so their servers handle the request that delivers this page. That is the ordinary mechanics of putting a website on the internet.
Who made what, what you can do with it, and which parts belong to somebody else. It takes about a minute.
Last reviewed 8 September 2026
What this is
A personal portfolio. The case studies describe design work I did: how a problem was framed, what I decided, and what the product looked like. They are accounts of design work, not product documentation, and not an offer of anything.
Work made for other people
Much of what you see was made while working for employers and clients. Those products, their names, their brands and their trademarks belong to them, not to me. Screenshots appear here to show design thinking and craft. They are never a claim on the product itself.
Pages and writing
Mine.
Products shown
Their owners’.
Logos and marks
Their owners’.
The protected case study
One case study sits behind a password because the underlying work is under NDA. If you have been given access, please keep the password and what is behind it to yourself.
Using what is here
Link to it, quote it, send it to someone who is hiring. All welcome, with credit. Please do not republish the writing, layouts or images as your own work.
Accuracy, honestly
Case studies describe products as they were when I worked on them. Software keeps moving after a designer leaves, so what shipped later may differ from what is shown. Where a project was a concept rather than a shipped product, the case study says so.
Links to other places
Some links lead to sites I do not run. I cannot vouch for what is on them or what they do with your visit.
The lawyerly bit
This is a portfolio, not a contract, and no lawyer has reviewed this page. It is written plainly and in good faith to describe how the site works. If you need something formal, a contract or an NDA or a licence, email me and we will write one properly.
