Design system Oviva Patient Management System

The Problem - No design system. No consistency. Lots of headaches.

Over the years, the health coaches' patient management platform had grown fast but without much design oversight. Every team implemented UI elements however they saw fit, leading to messy inconsistencies, lots of duplicated work, and design elements that didn't follow UX principles and standards. It was clear: the app needed a design system. Not just to speed up the development process but also to improve the design quality of the platform to minimize UX friction to the health coaches whose time was so valuable.

The Goal

To bring order to the chaos: create a reusable component library and a design system that provides clear guidelines and specifications — making the UI more consistent, scalable, and efficient for developers and designers alike.

My role

As the owner of the project, my role was to align with the front-end engineering teams, bring a common understanding of what we'd like to achieve, and produce the research, design, specification and guideline creation to each component in our system. After the development of the component library, my last task was to review the quality and sign it off.

Where we started

We kicked things off by auditing the entire platform:

• What components already exist (and how many versions of each)?

• Which pages were being migrated next?

• Which components would be needed soonest?


We then held an in-person workshop to get alignment across the front-end & design team. We discussed how to define our components, how to document them, and how to structure the system in a way that matched our web-app’s design system — for a more unified product experience.

The key outcome of our workshop:
We aligned on a clear component development process from start to finish.