Help Every Team Use the Design System

A design system helps teams make a product in a shared way. It can include examples of screens and rules for using colour. The people who build with it need to know these details. But other teams may need a different kind of explanation. They often want to know what the system helps them do.

Early design systems had guides and examples for people making websites. Over time, they grew to cover more parts of product work. A small team may use a system with only a few parts. A larger team may need more rules, tools and support. This is one reason the same name can describe different systems.

The author says listing the parts can make a conversation harder. People outside the design team may stop paying attention to it. The author suggests starting with what each group wants to know. One group may ask how the team will build a product. Another group may want to know why the company pays for it.

The author often calls it a shared service in these conversations. That idea helps show why many teams can depend on it. A shared service needs people to look after it over time. Each group can use words that make sense for its work. The goal is for teams to know when the system helps them. Then it can become part of how they build things every day.