Lumedic
Carbonara Design System
Context
At Lumedic, a fast-growing healthcare startup, I was one of the earliest designers brought in as the company began to scale rapidly. At the time, Design and Engineering were relying on fragments of Salesforce’s Lightning Design System alongside custom UI, which wasn’t scalable in Figma or in code. To support our fast-growing team, I helped adapt IBM’s Carbon Design System into a scalable, Figma library of atomized components, designed for speed, reuse, and multi-product adoption.
Team and Timeline
📎
My Role
Design Systems Designer
🙌🏼
The Team
2 Design Systems Designers
1 Engineer
⏳
Our Timeline
2 months
My Work
Organizing Chaos
As the design team grew, components were duplicated and patterns diverged across products. I focused on reorganizing and rebuilding the system to create structure, shared standards, and long-term scalability.
Key Problems and Solutions
👥
Rapid Team Growth
Built a system that allowed multiple designers to work in parallel without creating divergence.
🧱
Inconsistent Components
Replaced fragmented UI patterns with a single, shared source of truth.
⚙️
Scaling Without Variants
Enabled scalability through structure and naming before variants existed.
Carbonara in Action
Carbonara powered multiple product surfaces across the Lumedic platform. The system enabled consistent UI patterns across web, mobile, and tablet experiences while supporting embedded designers across teams.
 |  |  |  |
|---|---|---|---|
 |  |
My Process
From Fragments to a Scalable System
Starting with the IBM Carbon library we selected, I led the adaptation of the componentry into an atomic structure with clear hierarchy and naming. I handled much of the hands-on rebuilding, publishing, and designer walkthroughs as the team scaled, collaborating closely with our design lead. We shipped updates to the library weekly.
The Outcome
As Carbonara rolled out across teams, success showed up in how consistently designers used shared components and how easily the system supported work across multiple products as the team grew.
📐
Consistent Component Usage
Designers relied on shared patterns instead of rebuilding custom UI across products.
⏱️
Faster Design Workflows
Clear structure and reusable components reduced setup time and repetitive design work.
🧑💻
Scalable Team Adoption
New designers were able to onboard and contribute quickly using the shared system.
As adoption increased, ownership transitioned to a dedicated Design Ops Lead to support ongoing maintenance and evolution. The work also gained external recognition when we spoke to the IBM Carbon team who wanted to discuss how we had adapted and structured the Figma library for real-world use. Overall, this project shaped how I approach design systems today, with an emphasis on clarity, scalability, and real team needs.
