Sitemap
EightShapes

A collection of stories, studies, and deep thinking from EightShapes

Follow publication

Team Models for Scaling a Design System

10 min readSep 17, 2015

--

sun.com/webdesign’s Component Library index, circa 2009

The Overlord Rules

Past the Overlord: How Should We Organize?

Team Model #1: Solitary

A solitary model sees a one team make a system available, but with efforts focused primarily on that team’s needs
A solitary model sees a one team make a system available, but with efforts focused primarily on that team’s needs

Team Model #2: Centralized

A single, central design team produces and supports a system used by others as a part of their job
A single, central design team produces and supports a system used by others as a part of their job

Team Model #3: Federated

Designers from multiple product teams decide on the system together
Designers from multiple product teams decide on the system together

Forming a Federated Team

Represent Platforms that Matter

Designers across web site and app teams provided sufficient representation to legitimize the effort

Spread Expertise Across Disciplines

Associate experts with disciplines: U for UX, I for interaction, and V for style

Mix Doers and Directors

Design system contributors across platforms, including engaged directors (D)

Invest in Documenting & Communicating Centrally

Reciprocate Contribution with Autonomy

System contributors — including builders and authors (depicted in orange) — emerge from further out

More Models Out There?

--

--

EightShapes
EightShapes

Published in EightShapes

A collection of stories, studies, and deep thinking from EightShapes

Nathan Curtis
Nathan Curtis

Written by Nathan Curtis

Design systems consultant contributing to the field through the specs plugin, writing and workshops. VT & @uchicago grad.

Responses (7)