Design Systems, Oversimplified: The Team (2 of 5)
This is a 5-part series to explain the who, what, when, where, and why about design systems in its most simplest form. Once you understand the nuts and bolts of a design system, you’ll appreciate its deeper nuances more and might even want to build your own.
The Oversimplified Team
In the last post, I defined a design system as a set of standards that help a product development team ship to market faster. The heart of a design system is in the who — as in, who uses it and whom does it benefit? While having a set of unifying standards can profit an entire company and its end-users, the people who stand to benefit the most are in the product development team. Who makes up a product development team? Here’s my maddening simple explanation below:
A product development team is made up of designers and developers.
That’s the core of the team. Are there researchers, and content strategists, accessibility experts, engineers and product managers? There are. And I could break down those roles. But then the series wouldn’t be simple. So now you’re probably asking, what are these standards that designers and developers are using to ship a product? I’m so glad you asked. Check out the next post to find out what a product development team uses within a design system to improve elements like their workflow.
