Challenge
When I joined FLO, there was no existing design system, yet multiple projects were already underway to build internal and external portals for managing the EV charging network. We needed to move fast while ensuring long-term flexibility.
To balance speed and scalability, I built a low-styled component library using native web behaviors where possible. This allowed us to establish a functional UI quickly while keeping future theming options open.
Approach
I built core components with React and TailwindCSS, keeping them lightweight and easily customizable. To ensure consistency and fast adoption, I also developed a Next.js + Storybook documentation platform that gave teams quick access to standardized components.
Leveraging native behaviors minimized complexity, making the system intuitive. With faster iteration cycles, developers needed fewer design specs, freeing the UX team to focus on strategic work rather than repetitive UI specs.
By keeping implementation practical, the design system became an enabler, not a bottleneck. Developers quickly adopted it, accelerating FLO's ability to build and iterate efficiently.
As our cross-functional team embraced the initiative, the system's scope expanded, building comprehensive documentation and fostering a culture of shared ownership. Through inclusive training sessions and open contributions, I carefully evolved our design ecosystem, ensuring that both designers and developers felt empowered to shape our technical and visual standards.
Results
The design system transformed FLO's product development. Development cycles became faster, reducing the need to reinvent UI patterns. Developers gained autonomy, while UX focused on higher-value challenges. A unified design language ensured consistency across both internal tools and customer-facing platforms.
Lessons
Building a design system while projects were already moving required a pragmatic approach. Instead of aiming for perfection, I focused on delivering just enough structure to accelerate development without adding friction. Early wins drove adoption, and by keeping the system lightweight, I ensured it remained an enabler rather than a constraint. More than consistency, the real impact was in empowering teams to move faster with confidence.
Shoutout
This work wouldn't have been possible without Katherine Paradis Lord. Thanks to her contributions - especially how she structured and documented components - the system reached a whole new level of quality and cohesion. Merci Kath!
