This talk analyzes three existing design systems (Carbon, Atlassian, Workbench), highlighting their unique structures despite sharing common components. The speaker emphasizes that design systems should solve specific problems, advocating for a needs-first approach. Five key steps for building a design system are presented: 1) Identify problems, 2) Identify gaps using a provided framework, 3) Start with a strong foundation (tokens, core systems, then components), 4) Document design system language, and 5) Assemble the right team. The talk uses a visual "anatomy of a design system" chart to illustrate these points.