Case studies
Six design systems that I built or helped to build, from 2011 to 2026. Each one taught me one part of the method.
Six systems, one template: problem, what was built, what it taught, what is still open. Cases 4 to 6 were arrived at separately. That is the best evidence that this is a method.
One ordering system in three countries
M-Objednávka, a B2B ordering system for Makro Cash & Carry in Czechia and for METRO in Slovakia and Ukraine. One front-end code base, three build targets.
Level 1 · 2015 to 2016Two brands from one code base
After a merger, ČP Invest and Generali Investments needed two investment sites at once. Both came from one graphic framework, with brand as a parameter.
Level 2 · 2022 to 2024Tokens as a product
At Notino, tokens moved between the design tool and code in both directions, automatically, and shipped as versioned packages for many internal teams.
Level 4 · 2026A design validator for a banking app
A deterministic validator that finds whether a UI bug comes from the implementation, an inconsistent design file or the analysis. It reports and routes; it never blocks.
Level 4 · 2026An agent-first design-system foundation
Built for a banking software vendor. The agent never writes HTML; it fills a typed page spec, and scripts build and judge the page.
Level 4 · 2026Governance for a team of two
A B2B car-loan platform front end built by two people with no designer. Vendored shadcn/ui, one skin file, and numbered decisions that each name a lint or a test.