Building the System behind GOPACS

GOPACS (EDSN) coordinates the balancing of the Dutch electricity grid. A data-dense platform where consistency isn't a nice-to-have, it's operational risk. I was brought in to build the design system from the ground up: token architecture, component library and the structure to keep both in sync as the product and the team grow.

Client

Client

GOPACS , EDSN

Role

Role

Design Systems Lead

Duration

Apr 2026 - Present

Industry

Energy / Grid Infrastructure

Challenge

The product had grown without a shared design language. Multiple designers built similar components independently, each slightly different, with no token structure to keep colors, spacing, and states consistent as the platform scaled. Every new feature risked adding another inconsistency instead of reusing what already existed.

Results

  • Multiple components and variants organized under one token architecture, replacing ad-hoc, per designer patterns

  • A structured roadmap (v1.3 dark mode, v1.4 AI-assisted workflows via Figma/Storybook MCP, v1.5 expansion) replacing reactive, unplanned delivery

  • Currently absorbing a full brand refresh into a DS 2.0 major version, including new patterns like 3D data visualization with no existing equivalent to build from

Process

Understand: Built a full component inventory: 76 components, 270 states, directly from existing product screens


Structure: Designed a three-layer semantic token architecture and a five-layer Atomic Design structure to organize everything that followed


Build: Documented components and release notes across versions, with a delivery timeline planned in Jira


Align: Ran comparison sessions across three designers work to resolve inconsistencies before they shipped


Scale: Set up Figma Variables across primitive colors, semantic colors, spacing scales, typography, and component-level tokens, built to hold up as the system keeps growing


AI Integration: Connected Figma MCP with Claude Code and set up ZeroHeight, building toward AI-assisted workflows, a documentation drafter, a token-naming linter and a state-coverage checker as part of the v1.4 roadmap

"Most design systems are built once and maintained forever. GOPACS taught me to design for the second version before the first one even shipped."

Conclusion

GOPACS is Bluyon's clearest proof that a design system isn't just a component library. It's the infrastructure that lets a product keep shipping consistently as complexity, team size, and scope all increase at once. The system is still evolving: DS 2.0 and a component-library merge project are both underway, which is arguably the more honest story: a design system is never "done," it's maintained.

Let's Scale Together.

Let's Scale Together.