
Design systems done differently

Design-first software engineering: Craft – with Balint Orosz
Topic 7 of 14
Published Mar 5, 2025 · Clip 37:05–44:10 (7:05)
The guest explains why most companies get design systems wrong. Atomic design systems (atoms → components) emerged when design fought for a CXO seat and needed a shared language with engineers; they work well for static brand identities and scaling quality, but scaling quality differs from innovating. At Craft, any frontend engineer can recreate their standard button in two minutes — that needs no system. Instead, Craft builds systems for genuinely hard things: an animation engine that synchronizes all movement (compared to dancers moving in time), enforced across the team so everything — even the whole document on a new line — animates fluidly. They also build reusable behaviors like a fading label that replaces ellipsis cropping, preserving characters and working against any background including dark mode.