Patrick Sobrak-Seaton

Product Designer & Design Engineer

Douglas Design System

UP42

Tokenized, accessible design system: designed in Figma, built in React, adopted across design, engineering, and marketing.

Douglas components as monochrome wireframes on translucent gray islands, over a photo of Earth from orbit Douglas components as monochrome wireframes on translucent gray islands, over a photo of Earth from orbit
DDS Storybook Coming soon

Past

When I joined UP42, there was no design system in place. On the design side there was only an outdated and broken Figma library and lots of everyday components that lived within the product initiatives in which they were created. On the code side, frontend was in the middle of a massive transition from Vue to React and that only made problems worse.

Teams were re-inventing components and patterns each initiative, color values were hard-coded and varied between teams, and that caused end-to-end turbulence with each feature, which was costing us immense amounts of time, energy, and goodwill.

The solution I offered to these problems was to create a comprehensive design system that codified processes and patterns and lessened the delta between design and code. I called our system "Douglas" after the incomparable Douglas Adams.

Present

  • Figma
  • Storybook
  • React
Our current design system stack

Now, that picture is practically inverted. Design and code sit in much closer alignment, anchored by a state-of-the-art Figma library, a primitive and semantic token system, and a refactored React component library. Additionally, accessibility became a central focus with every new component.

Today, Douglas is used across product, engineering, design, and marketing.

Douglas components side by side: buttons, map controls, a switch and checkbox, status tags, a progress ring, search, tags, radios, paging, a date and a toast button Douglas components side by side: buttons, map controls, a switch and checkbox, status tags, a progress ring, search, tags, radios, paging, a date and a toast button
A small handful of Douglas components

That being said, it's not perfect. For example, the semantic tokens are sometimes too prescriptive, baking in semantic decisions before the patterns were fully matured.

Future

The next chapter of the Douglas Design System addresses that problem directly with a redesigned semantic token layer and the implementation of the OKLCH colorspace. This way we can create unified color experiences programmatically to guarantee accessibility and visual hierarchy regardless of semantic meaning. This also aids the creation of color themes for new modes and white labeling.

  • Figma
  • Storybook
  • React
  • Claude
Our design system stack, plus Claude

As the industry moves toward design and code that begins with LLMs, Douglas needs to be redocumented to make it more machine-readable. This is the work ahead: to build a version of the system that models can consume and compose with directly and efficiently.

Douglas's ten color scales in ten steps, each swatch with its text contrast ratio Douglas's ten color scales in ten steps, each swatch with its text contrast ratio
Douglas's ten colors in ten steps, each with its text contrast ratio