Patrick Colligan
OPen
Client:
DrChrono
Design Systems
Product Thinking
Experience Design

DrChrono

Team

Me (Design Systems Lead) — Product Managers — Front-End Engineers — Brand & Creative Team

Timeline

6+ Months

Scope of Work

Design System Lead — UI/UX Design — System Architecture — Cross-functional Collaboration

Role

Senior Designer

Building the foundation for scalable, token-based design across a growing healthtech ecosystem

DrChrono is an EHR platform serving tens of thousands of medical professionals across the US, and part of the broader EverCommerce product ecosystem. When I joined, the UI was fragmented — inconsistent components, no shared token system, and a brand migration to EverHealth on the horizon that would require the entire interface to evolve. I was brought in to fix the foundation before the house got any bigger.

The Challenge

DrChrono's design had grown organically over years of product development. The result was a UI full of one-off decisions — buttons that looked slightly different across screens, spacing that varied by team, and no single source of truth for designers or engineers.

With EverHealth's brand consolidation approaching, there was urgency to systematize the interface in a way that would survive a rebrand without requiring a full rebuild. The challenge wasn't just design — it was getting an entire organization to change how it worked.

The Outcome

The system shipped and is now the shared foundation across DrChrono's product teams. The token architecture is in place for the EverHealth brand migration whenever that transition happens — meaning that work is already done.

The before/after audit told the clearest story: what used to be a product full of one-off decisions now has a single source of truth.

My Process

1. Conducted a UI Audit
I began by auditing the platform's visual and interaction patterns. This surfaced duplicate components, inconsistent spacing, and lack of adherence to accessibility standards.

2. Leveraged Existing Frameworks
Rather than reinvent the wheel, we adopted the Flowbite design system, a well-structured Tailwind-based UI kit, to speed up implementation. I customized and extended the system to match our needs, layering in a custom brand system that aligned with DrChrono’s identity and future EverHealth direction.

3. Built a Token-Based Foundation
We implemented design tokens to define our color palettes, typography, spacing, and elevation. This semantic system allowed for consistent UI construction and set the stage for easy theme-swapping when drchrono transitions to EverHealth branding.

4. Developed and Documented a Scalable Component Library
In Figma, I constructed a shared library of atomic components with built-in accessibility and variant support. I worked closely with engineering to ensure design-to-code alignment and provided robust documentation for usage and contribution.

5. Drove Cross-Team Buy-In
Through workshops, async walkthroughs, and design reviews, I helped onboard design and engineering teams to the new system. I also established governance processes to ensure consistency and long-term adoption.

Results & Impact

✅ Projecting a 7% increase in conversions by optimizing user flows.

✅ Improved navigation & user experience, reducing friction in key journeys.

✅ Stronger brand consistency with newly setup DrChrono Design System.

✅ WCAG-compliant pages, ensuring a more inclusive experience.

✅ Established a foundational design system for EverHealth’s upcoming website launch, leveraging DrChrono as a UX blueprint.

✅ Integrated tokenization to ensure the site’s design scalability and flexibility, enabling a seamless transition from DrChrono to EverHealth with consistency across future updates.

Next Steps

The system is now positioned to scale across the entire EverHealth product suite. With design tokens and a shared foundation, we’re well-equipped to switch themes, introduce dark mode, or roll out future brand changes without major rebuilds—saving time and reducing tech/design debt.

Final Thoughts

A design system is only as good as its adoption. The technical work matters, but the organizational work — getting teams to trust and contribute to a shared system — is what determines whether it lasts.

Building on an existing framework like Flowbite was the right call. It let me focus energy on what was actually unique to DrChrono rather than reinventing solved problems.

Use this form to connect with me and let me know how I can help!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.