

Challenge
• A platform that showed everything, all the time. The busiest screens tried to display every possible function at once, no matter the situation. An appointment that was finished looked identical to one that needed payment same layout, same weight, same clutter. Admins had to read the whole screen every time just to find the one thing that actually needed their attention. • No shared visual language. Because the product had grown piece by piece, the same elements looked different depending on where you were. A status, a button, a card each had been styled by eye in isolation. There was no system enforcing consistency, so nothing felt like it belonged to the same product. • Cluttered flows that fought the user. Key tasks like booking an appointment were tangled with redundant controls and awkward layouts fields fighting for space, filters mixed with sorts, actions duplicated. The screens asked users to do more work than the task itself required.

Outcome
• A design system that holds the whole platform. I built 57 color tokens across semantic scales, 44 type styles, an icon library, and reusable components. Every screen now pulls from the same foundation, so a dense billing table and a simple form finally read as parts of one coherent product. Consistency stopped being something to police and became something the system enforces by default. • Screens that surface the task, not the clutter. I rethought the busiest flows around a simple rule: the interface stays quiet unless there's something to do. A settled appointment shows no action; one that needs payment surfaces that one task clearly, with nothing competing. Cluttered toolbars were cut down to only what's used, and every empty state collapses instead of taking up space. The CEO's response to the redesign was that it became "cleaner and more functional." • A second platform, integrated as one. LX needed the capabilities of Spruce, a separate patient-messaging product. Rather than bolt it on, I brought it into the LX design system and structure so the two read as a single platform, same language, same patterns, instead of two tools stitched together.



















