I built Marrow from scratch. One design system for five EverHealth brands, replacing five broken Flowbite libraries with a single, token-driven source of truth. Audit to rollout in two weeks.
RoleSenior Designer
TeamSolo · Brand & Creative (cross-function with Engineering)
Timeline2 weeks · Audit, build, rollout
ToolsFigma / Variables · Claude Code · Zeroheight
StatusLive Design System
5 → 1
Five disconnected brand libraries replaced by a single token-driven system
2 weeks
From audit to live rollout, including stakeholder walkthrough and SOPs
Team-wide
Every designer operating from one system. SOPs and onboarding videos in place for every future hire.
The problem I found
01
Five separate Figma libraries with nothing shared between them. Every new board meant rebuilding from scratch.
02
Hundreds of unused Flowbite components in each library. Designers couldn't find the assets they actually needed.
03
Brand assets full of errors. Wrong hex values on color tokens. Wrong fonts in styles. Logos incorrectly built into components.
04
Zero governance. No documentation. No onboarding path. Brand inconsistency was shipping to production and nobody caught it.
What I built
01
One Figma file with variable modes. Switch brands by changing a mode, not by opening a different file. All five brands from one source.
02
Three-layer token architecture. Brand primitives feed into semantic tokens, which feed into component tokens. Change one value, it flows everywhere.
03
Style guidelines for each brand. Correct typography, color palettes, logo usage, and imagery direction. Verified against actual brand standards.
04
Zeroheight as the live source of truth. Connected to Figma. Includes governance SOPs, onboarding guides, and a rollout plan.
What I owned
Every layer. No handoffs. Just me.
01
Audited brand inconsistencies across every product surface
02
Built the token architecture: color, typography, spacing for five brands
03
Created a component library with shared primitives and accessibility baked in
04
Wrote five brand style guides covering logo, color, type, and imagery
05
Set up Zeroheight and connected it as the live documentation site
06
Built the Product & Engineering bridge: tokens, accessibility, breakpoints, spacing
07
Wrote governance SOPs: naming conventions, export settings, asset management
08
Planned and ran the rollout: leadership walkthrough, team onboarding, video guides
Before
After
Before: what I inherited
Flowbite dependency with hundreds of unused components per board
Brand colors mislabeled with wrong hex values in variables
Wrong fonts baked into component styles
Five disconnected libraries with no shared primitives or rules
After: what I shipped
Single variable-driven file with brand switching via Figma modes
Three-layer token hierarchy cascading from primitives to components
Per-brand style guidelines with correct typography, color, and logo
Live Zeroheight documentation as the digital source of truth
System comparison: fragmented Flowbite libraries vs. unified token architecture
Token hierarchy
Style guides
Rollout walkthrough
Token architecture · Style guides · Rollout plan
EverHealth
DrChrono
CollaborateMD
Updox
iSalus
Brand guidelines for all five EverHealth brands · Click to enlarge
Approach
I started with tokens, not components. One Figma collection for color, one for typography. Each has modes per brand. Any component built on top automatically gets the right visual identity just by switching a mode. No duplicating. No hunting.
Key decision
I built from scratch instead of fixing the existing Flowbite setup. Adapting it would have meant inheriting hundreds of unused components, mislabeled tokens, and errors that were already causing confusion. Starting clean took discipline, but it meant everything in the system was correct and intentional from day one.
Driving adoption
I started with leadership. Showed them the scope of the problem next to the solution. That created buy-in. Then I ran a hands-on session with the design team. After that, I documented SOPs for future onboarding. The product team keeps their own component system, but it now references Marrow's brand tokens as the visual foundation. Both teams own their domain without stepping on each other.
The best design system is the one the team actually reaches for. It has to be easier than the alternative, not just more correct.
Zeroheight: Marrow homepage
Zeroheight: EverHealth brand page
Live Zeroheight documentation: the digital source of truth for all EverHealth brands
Naming the system mattered more than I expected. “Marrow” gave the project weight. It told the org this wasn't a Figma cleanup. It was infrastructure.
Governance needs design too. The naming conventions, export checklists, and the Zeroheight connection are what keep the system clean over time. Without that, you just end up with a new version of the same mess.
Design systems are about building something other people can carry forward. That's what separates a system that lasts from one that gets abandoned.
5 → 1
Five fragmented libraries replaced by one token-driven system
2 weeks
Audit to live rollout, including stakeholder walkthrough and SOPs
Team-wide
Every designer operating from one system. SOPs and onboarding videos in place for every future hire.
