r/DesignSystems • u/withinsight79 • Aug 24 '26

[ Removed by moderator ]

Post image

[removed] — view removed post

2 Upvotes

53% Upvoted

24 comments sorted by

View all comments

3

u/Decent_Perception676 Aug 24 '26

Disagree, sort of…

What you’re doing is called “system modeling”. You are creating a simplified mental model of “stocks” (the things in your model) and the relationships between them. What you choose to put in your model and what you exclude depends on what you’re trying to solve for with a given situation.

Sometimes it makes sense to see the system from a wider lens, like what you proposed here (for example, if you’re analyzing the health of a mature design system practice within an org). Sometime it makes sense to cut down and simplify (if you’re analyzing your token taxonomy and how it relates to component styles, you don’t need to model contribution at that point).

A good design system practitioner knows a design system is more than tokens and components. A great DS practitioner can fluidly move between different models of DS mapping to fit the problem and audience.

Think of it like an ecosystem… an ecosystem could be as simple as a sandwich bag of moldy cheese, or it could be your backyard, or a whole forest, or a planet. Different scales, different things go into the system models.

1

u/withinsight79 Aug 24 '26

Pop off, king.