Cross-Company / 2020-Present
Design Systems
Built shared foundations across five product organizations to cut implementation time by 3–4x, reduce design debt, improve accessibility, and support customer branding at scale.
Design Highlights
Overview
I have built and led design systems across five organizations with very different products, stacks, and adoption constraints. Today I lead Docebo's Design System team and the evolution of Elemental. That leadership builds on hands-on system work at Knak, Arctic Wolf, InFlight, and D2L, from reusable components and theming architecture to accessibility, governance, and organization-wide adoption.
Challenge
Every organization faced the same core problem: teams rebuilding familiar interface patterns, creating inconsistent experiences, slowing delivery, and increasing design debt. Each organization required a different operating model. Docebo needs a shared foundation that can support a broad enterprise learning platform and emerging AI experiences. InFlight needed hundreds of customer brands in one system. Knak needed to modernize a legacy product incrementally. D2L required WCAG AA Gold certification, while Arctic Wolf needed to unify a rapidly growing product surface.
Approach
At Docebo, I lead the team responsible for Elemental, connecting system direction and governance to active product work so designers and engineers can build consistently at scale. At InFlight, I created shared components and an abstraction layer that supported hundreds of brands without changing the components. At Knak, I adopted Shadcn and Tailwind for new work and established a Design Systems working group to align requirements, Figma assets, and legacy replacement. At Arctic Wolf, I co-led React system development; at D2L, I designed within the mandatory accessible platform system.
Solution
I tailored both the component strategy and the team model to each organization's adoption reality. At Docebo, that means leading a dedicated Design System team that stewards Elemental while keeping its reusable foundations connected to real product delivery. InFlight used brand-agnostic components with a theming layer. Knak introduced its modern system gradually through design and engineering partnership. D2L embedded accessibility at the component level, contributing to WCAG AA Gold certification.
Impact
Designers and engineers gained shared patterns that reduced repeated decisions, improved accessibility, and cut implementation time by 3–4x. Customers received more consistent experiences, including WCAG AA Gold accessibility at D2L and reliable brand support across hundreds of InFlight themes. Across five organizations, the systems lowered maintenance and design debt, including a 20% reduction at Arctic Wolf, while giving each company a foundation for faster product delivery; at Docebo, I now lead the team, direction, governance, and adoption behind that foundation.
Key Learnings
Design-system adoption has to match the organization. Compliance can drive mandatory adoption; legacy products often need a working group and gradual migration; platform-scale systems require a dedicated team with clear direction and close connection to product delivery. The hardest problem is not building components. It is creating the leadership, governance, and flexibility that let many teams move faster without losing consistency.