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 flexibility, I built a lightly styled component library around native web behaviors where possible. This let us establish a functional UI quickly while keeping future theming options open.
Approach
I built the core components with React and Tailwind CSS, keeping them lightweight and easy to customize. To support consistency and adoption, I also developed a Next.js and Storybook documentation platform that gave teams quick access to standardized components.
Leveraging native behaviors minimized complexity, making the system intuitive. As iteration got faster, developers needed fewer design specs, freeing the UX team to focus on product problems rather than repetitive UI work.
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 the team adopted the system, its scope grew. I expanded the documentation and created space for shared ownership through training sessions and open contributions. Designers and developers could shape both the technical and visual standards together.
Results
The system gave FLO teams a shared foundation for internal tools and customer-facing platforms. Developers could reuse and adapt components instead of rebuilding them, while UX could spend more time on product problems than repetitive UI work.
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 the way she structured and documented components, the system reached a whole new level of quality and cohesion. Merci Kath!
