E.ON Next
Energy / Utilities
1K-5K employees
Jun 23 - Jun 25
E.ON Next was scaling fast—but their design tools weren’t. Multiple teams were working in silos, redoing the same UI work, and struggling with inconsistent user experiences.
I helped create Horizon: a fully tokenised, flexible design system that gave product teams the power to move faster, stay aligned, and deliver more polished, accessible interfaces—every time.
Product teams were moving quickly—but not together. Each team was designing and building in isolation, creating inconsistencies across journeys, duplicating work, and slowing down releases.
There were only some basic shared components. Accessibility wasn’t guaranteed. Developers struggled to translate UI decisions into code. The lack of a single source of truth was costing time, clarity, and quality.
E.ON Next didn’t just need a design system. They needed the infrastructure and guidance to build one properly—and make it stick.
We started from pretty much scratch and built Horizon: a design system focused on real-world use, speed, and collaboration.
Horizon was a shared language, helping designers and developers ship better work, faster.
Early adoption showed just how much Horizon was improving consistency and speed—while laying the groundwork for long-term design maturity.