Get in touch with us at yashkdesigns@gmail.com
Executive Summary
A B2B compliance platform for skilled nursing facility staff managing long-term-care Medicaid applications, built around a draggable "pipeline canvas" workflow. I led iterative UX passes on the live product, a first-time tutorial for the core interaction, an accessibility audit fixing WCAG contrast failures across light/dark themes, and a simplified invite flow. Designed for an older, non-tech-forward user base and refined against real rendered screenshots rather than static specs.
Design Decisions
1
The existing product was vibecoded with just an idea of what they had in mind.
Solution:
As a UX designer, I revamped the designs and flows having users in mind and doing some market research
2
Accessibility: Theme, Guidance & WCAG.
Solution:
I brainstormed, redesign and created design tokens considering the target audience and laws of UX
1 - Redesigning the vibe-coded core
The primary surfaces users rely on all day, started as AI-generated builds. The issue wasn't broken functionality; it was that the AI had built exactly what was asked for, with no judgment about what the workflow actually needed.
Main UX principles anchored the redesign decisions:
1) Visibility of system status — The staff needed to always know what the product was doing and what to do next, especially on first use. place.
2) Consistency — interaction patterns that meant the same thing looked and behaved the same way.
3) Hick's Law — reducing choices to speed up decisions.
4) Miller's Law — chunking information to avoid overload.
Before
After
Grouped options into named categories, merged duplicate controls into one, and introduced accordions so users only see fields relevant to what they're currently configuring, reducing overload and cutting decision time.
All configuration options were surfaced on a single flat page, every input competed for attention at once, with no grouping to guide the eye.
The chart and its supporting table were stacked one above the other, forcing users to scroll back and forth to connect a trend with the numbers behind it.
Placed side-by-side so trend and underlying data are readable together and a change in the numbers is immediately traceable to the chart, which matters given how much of this product runs on live data.
_edited.png)
Staff had to recall from memory which document they were approving, no way to preview it or cross-check details without leaving the panel entirely.
Staff can click directly into a document to preview it, review the actual consent language, and approve multiple documents in a single action.
Few Other Design Decisions
Icons
Designed a full icon set for the product's core features and navigation, translating the brand's visual guidelines into a consistent, legible system, something the original vibe-coded build hadn't defined at all.
Top Bar
Search, notifications, history:
Added a global search, notification, and activity-history bar, giving staff a single place to track their own actions and other users' activity across the platform, rather than reconstructing that context manually case by case.
Problem
Has to remember the tips every time
Proposed Solution
Interactive Guidance: AR tooltips and focus indicators to help users capture better photos.
Problem
No freedom of what to be scanned
2- Accessibility: Theme, Guidance & WCAG.
The Audit
An audit of every text and border color in the design system, checked against the real WCAG relative luminance formula rather than judged by eye. Two tokens were failing outright; a third was passing with no real margin.
Given the user base, business-office staff aged 20 to 70, working in dense forms for hours at a stretch, I recalculated every token in the system against the actual WCAG formula, not by eye, and pushed the fixes to roughly 6:1 and 4:1: past the legal minimum, because the audience and the all-day use case warranted the margin.
Token-based theming
Light and dark themes were built on a shared token system rather than hardcoded per screen, so the same contrast-tested values apply across both, a fix in one theme can't silently regress the other.
01522E
Guidance - OnClick Trigger
Added tooltips that surface on click rather than by default, so explanations for new features or complex data are available exactly when a user needs them, without cluttering the interface for people who already know the feature.
Guidance - Hover Triggered
For file status specifically, used a hover tooltip with a subtle bump animation, a lighter-weight pattern than click, suited to information that's useful to glance at but doesn't need a deliberate action to reveal.
System Status
Surfaces the current state of what's happening in real time, so staff are never left guessing whether an action registered or a process is still running.
Responsiveness
Scoped by access pattern, not applied uniformly. Internal staff work the pipeline canvas from fixed desktop workstations all day, so those views stayed desktop-first.
Family members, by contrast, are invited in over email, to create an account, upload requested documents, and check a resident's case status, and open that link on whatever device is in hand, often a phone.
Responsive design was applied specifically to the family-facing flow, because that's where device variability was actually real.
Impact & Results
Contrast ratio - Text (light)
Before: 3.35:1 (fails WCAG AA)
After: 6.06:1 (passes AAA-adjacent)
Contrast ratio, Text (dark)
Before: 4.90:1 (passes, no margin)
After: 6.02:1 (comfortable margin)
Contrast ratio: card/input borders
Before: 1 .30:1 (fails AA)
After: 4.00:1 (passes AA)
Navigation depth
Before: Flat text list, no active-state or icon system.
After: 6 destinations, icon + label, live active-state.
Descriptive subtext:
Before: Inline caption under figures/sections
After: Zero, by rule (state shown as a chip, a bar, a lifted target, never a sentence)
Task that previously took roughly a week to complete was finished aproximately in 4 days after the redesign, a 35% reduction in time, from initial brainstorming through design to development.
Conclusion
This project was less about designing a single feature and more about turning an AI-generated starting point into a product staff could actually rely on all day, one interaction, one contrast ratio, one confusing flow at a time. The through-line across every decision, from the pipeline canvas's drag targets to the tooltip system to the theming architecture, was the same: reduce friction for a user base that doesn't have time to learn a new interface on top of an already demanding job.
Given more runway, the clearest next step would be usability testing on the onboarding tutorial specifically, it's the one flow built entirely on inference about a first-time user's mental model, without a real new hire ever watching it.