Bynder Design System Update
A full design system overhaul that modernised the product, achieved WCAG AAA compliance, and increased adoption.

Overview
After Bynder completed an acquisition and launched a bold new brand identity, the product looked nothing like the marketing. I was part of the team that closed that gap, rebuilding the design system from tokens up, achieving WCAG AAA compliance, shipping 37 new components, and documenting 16 new patterns and 16 new layouts.
Rather than a big-bang replacement, we took an incremental approach that maintained stability while delivering visible wins early. Adoption increased 42% in six months.
Solution

Incremental rollout over big-bang replacement
Prioritised the most widely used components first, building trust and momentum before tackling the full system. Each phase delivered visible improvements before the next began.
Accessibility baked in from the start
Rather than treating brand refresh and WCAG compliance as separate efforts, we aligned them into a single workstream, fixing grayscale, elevation, and colour tokens in one pass.
Patterns and layouts, not just components
Went beyond isolated components to document the flows and layouts that tie them together, closing the gap that was causing cross-team inconsistency.
Outcomes
The Problem
Bynder had just completed an acquisition and launched a new brand identity. The gap it created was immediate and visible: the product customers used every day looked nothing like the brand they were seeing in campaigns. Marketing was promising something modern, cohesive, and bold. The product was delivering something static, inaccessible, and inconsistent.
Rather than run two parallel efforts, one for brand, one for compliance, we recognised the opportunity to align them. A single, coordinated update to the core design system could modernise the product on both fronts at once.
A custom dashboard built with engineering tracked component usage and accessibility levels across product pages. The audit revealed four compounding problems: the system did not meet WCAG AAA compliance, grayscale contrast and elevation were the biggest blockers. Documentation was scattered across Figma, Storybook, and Google Docs. Accessibility was not built into daily workflows. And Figma libraries were not using the variables system, creating unnecessary handoff overhead. Teams were avoiding the design system because components were too outdated and inflexible for new features.


Key Product Decisions

What Almost Killed It
The biggest risk was not technical, it was trust. Teams had been avoiding the design system for years because of outdated, inconsistent components. Announcing a new system would not fix that. The only thing that would rebuild confidence was shipping visible improvements quickly, to the components people used most, without breaking what already existed.
The incremental strategy was not just a rollout preference, it was the primary tool for re-earning adoption.




