Designing systems that survive the team.

At Config 2026, we presented a case study on one of the harder problems in brand work: building a visual system that engineering teams actually use after the agency leaves. The recording is below, but here are the core ideas for those who'd rather read.

The problem with most brand guidelines

Most brand guidelines are written for brand managers. They document what the brand looks like in controlled conditions — the logo on a white background, the color palette as swatches, the typeface as a specimen. They say nothing about how the brand behaves in code.

Engineers inherit these guidelines and have to translate them into tokens, components, and logic. That translation is where brand systems break down. Not because engineers don't care, but because the guidelines weren't written for them.

"A brand system that lives only in a PDF is a brand system that will diverge from reality within six months.

What we build instead

• Design tokens as the single source of truth — colors, spacing, typography scales all live in a JSON file that both Figma and the codebase consume.
• Component documentation that includes interaction states, not just visual specs.
• An 'escape hatch' protocol — documented rules for when and how engineers can deviate, so deviations are intentional, not accidental.
• A quarterly brand audit built into the retainer, where we check the live product against the system and note drift.

The goal isn't a perfect system — it's a living one. A system that can absorb the reality of a growing product team without losing its coherence.

The talk runs 34 minutes and covers three client case studies in depth. If you're building a design system for an engineering-heavy team, it's worth watching. If you'd like us to run a workshop version of this for your team, reach out.