> A lack of actual (not assumed) alignment within teams and leadership around what a design system is, what problems it solves, and how it will provide value.

> A lack of actual (not assumed) alignment within teams and leadership around what a design system is, what problems it solves, and how it will provide value. Definitely. In a retro recently I heard, "We need a design system!" followed shortly by, "We already have a design system!" and "What's a design system?" Speaking as a developer, this discussion is slightly out of my lane, but I appreciate the article's discussion of when to start investing in a design system and what you might get in return.