Eryk Orłowski · hretheumhretheum.com/questions/multi-brand-design-system
Question P3 of 8
All questions3Can they lead a design system for many brands?
For an energy group with 7–9 brands from acquisitions, from a brand book in PDF to full component libraries in Figma, proposed a competence center strategy and pointed out the business problems it can solve. The design system is developed by a 6-person competence center in which mostly designers from the team they lead work. Single-handedly built a toolchain with AI agents: 12 command-line tools with 78 test files. Thanks to it, a new company in the group is one configuration file, and WCAG 2.2 contrast is checked in every mode, including the mourning one.source sources: ds-01, ds-11, ds-09, ds-07, ds-03, ds-05, ds-06
Evidence
The starting point was 7–9 brands from acquisitions, ranging from a PDF brand book to full component libraries in Figma.”
I came up with, designed and built the toolchain myself, working with AI agents.”
I designed and built Gromatik and blind.ds myself, as a private project.”
Contrast is checked against WCAG 2.2 for every mode, including mourning, and failing the threshold stops the pipeline.”
A new company in the group is one configuration file, with no code changes.”
The toolchain is a monorepo of 12 command-line tools with 78 test files, built in June 2026.”
I proposed the strategy of the centre of excellence and identified the business problems it can solve.”
A person reviews every drift between Figma and the canon and decides what to do with it.”
The client did not know such tools could be built; I pointed out the business problems they solve.”
I co-hosted a webinar on the European Accessibility Act with Michał Jankowski and a lawyer.”
In the toolchain for the multi-brand group, WCAG 2.2 contrast is checked for every mode, including mourning.”
Skills Factory is a library of tools on an adapter pattern that carries the design system into code.”
I co-created the foundations of the design system for business banking products.”
Generating component code is one model call per component, with no agent loop and no code execution on the server.”
A measurement on the live stack showed that 5 repetitions of the same prompt gave 5 byte-wise different results.”
Gromatik was built in 256 commits between 5 August and 13 September 2026, with about 1000 passing tests.”
Every run records its settings and a fingerprint of its input, so you can trace where a result came from.”
At the start of every project, when everyone is still sure they won't need one. […]At the start of every project, when everyone is still sure they won't need one. That feeling usually lasts until the third team ships the third version of the same button. Which is a bit of a shame, because the start is exactly when a design system is cheapest: a few shared decisions made early cost far less than untangling three products later.”
The things that break are usually the same, whichever system it is, and I've seen all of them, though luckily not all in one project. […]The things that break are usually the same, whichever system it is, and I've seen all of them, though luckily not all in one project. The first is drift: design and code slowly stop matching, one small exception at a time, and nobody notices until a rebrand or an audit shows how far apart they are. That's why in my recent work I measure consistency with tools instead of relying on reviews. The second is ownership. A design system gets launched like a project and then left without a team, a budget or a roadmap, and it ages within a year. The third is adoption. If using the system is harder than building the component yourself, product teams will build it themselves, and they'll be right to. None of these is a technical problem at heart; they're about how the system is run.”
I take it as a sign that design and engineering are working in sequence instead of together. […]I take it as a sign that design and engineering are working in sequence instead of together. When designers hand over finished screens, engineers wait, then find problems late, and both sides lose time. So the first fix is to bring designers in earlier, into discovery and workshops with engineers, the way my team worked at Sportradar, where designers owned the process from discovery to workshops inside their product teams. The second is to shorten the handover itself. A good design system and the right tools take a lot of manual translation out of moving a design into code; at Efigence I built a library of tools for exactly that. Once both are in place, the complaint usually turns into a shared plan.”
I keep that client anonymous on purpose, and I'd do the same for any client of yours. […]I keep that client anonymous on purpose, and I'd do the same for any client of yours. What I can describe in detail is the work. The design system for an energy group with seven to nine brands is developed by a centre of excellence made up mostly of designers from my team. I give it strategic support and add a set of tools I built with AI agents to measure how consistent the brands really are.”
Limit
On the design system I give the CoE team strategic support, and my own contribution is the toolchain.”
E-mail: [email protected] (kt-01) · LinkedIn: linkedin.com/in/eofek (kt-02)