A Design System People Trust

We had a design system. It just wasn't the source of truth anymore. Developers shipped small, ad-hoc fixes because each one looked simple and harmless on its own. Over time those little decisions drifted out of sync with the system, the inconsistencies compounded, and eventually nobody treated the library as the source of truth. The big-ticket widgets held up. It was the small stuff that fell apart, the bits and pieces the original system never really accounted for. I found it by auditing what we already had. The whole library lived on one sprawling board: hard to parse, disorganized, and missing the small components the site actually ran on. Everything the site needed was crammed into a single screenshot. That was the evidence: we didn't need another patch, we needed a new approach.

• What drifted: the disclosure control, every label (filter pills, search-result labels, campus and location labels, the accepting-patients label, the distance indicator), the single card block, the condition-search result card, plus drop shadows, strokes and borders, accents, and text highlighting.
• What held: the large widgets stayed consistent, provider cards, location cards, CTA blocks, and stories.
• The gap: we needed a system comprehensive enough to govern the small pieces of the site, not just the big-ticket widgets.

This is a 30,000-person academic medical center serving 1.2 million patients across the region. When the system drifts and design and engineering stop speaking the same language, the cost lands on patients.

Three steps: two I owned, one I drove with engineering. First I had to earn executive buy-in, which I did by reframing the problem in terms leadership cared about: the cost of teams working from different sources of truth.

1. 01

   Problem Framing

   I owned

   I started with the developers, not the components. They showed me why the old library had failed: it covered the big widgets but never the small pieces teams reached for, so it had stopped being trusted. The fix wasn't more components, it was one comprehensive source of truth.

2. 02

   Token Architecture

   I owned

   I rebuilt the foundation and defined the full token set: type, color, grid, spacing, iconography, animation, borders, and shadows. This stops drift at the root. The small pieces now inherit from one source instead of being hand-styled on every page.

3. 03

   Engineering Partnership

   Collaboration

   I built every component alongside developers, not across a handoff wall. If something couldn't be built cleanly, the design changed. That's what made the system trustworthy enough to adopt, and it cut review time after handoff.

Most design systems document the big components and stop there. What distinguishes this one is that every widget, down to the small pieces that used to drift, gets the same rigorous documentation, so developers and content editors can act without pulling each other off real work. Every widget answers the same six questions. That consistency is what turned the library from a liability into something the team actually reached for, and it moved reviews from "I don't like the blue" to "does this serve what the patient needs?"

Once the core library was trusted, I extended it to the medical school with a bespoke pattern library, sharpening student storytelling to encourage applications while preserving clinical brand coherence across very different audiences. The same foundation now serves both patient-facing care and academic recruitment.