Team Models for Scaling a Design System

snip.ly

Good teams have a clear sense of who documents these decisions and how they are communicated. These contributors (depicted in orange) author guidelines, build components in code, update design tool templates, and do so much more than keep the system alive.

High-performing teams establish platforms (such as github.com repositories and other content publishing tools) that enable an array of individuals to continuously evolve a system’s definition.

But, alas, some teams don’t have such platforms. More often, the individuals making decisions in a federated model aren’t always available enough to write them down.

Yes, a federated team needs a centralized component of staff dedicated enough to the cause.

Leaders create space for doers to get the job done. They ensure there’s staff for whom the library is a prioritized responsibility of or only part of their job. Without that fine work, that living style guide can seems quite dead—or at least unconscious—ten months on.

This is a great long and great article if you are working on designing a large and complex information system.

Read more...
Linkedin

Want to receive more content like this in your inbox?