For designers and design system leads who already build components and want to keep a shared system working. You will be able to manage tokens, flexible components, governance, adoption and handoff to code.
7 lessons · 3 hr 9 min
Beginner (not covered)
Intermediate
Advanced
What you’ll learn
✓Organise primitive and semantic tokens and keep them consistent across the system
✓Build flexible components with Slots that stay linked to code
✓Set up lightweight governance with clear ownership, contribution rules and versioning
✓Judge how to drive adoption among designers and developers
✓Plan and track design system work using roadmaps, backlogs and release cycles
Start here: learn the token foundations of primitive, semantic and aliased variables that later videos assume.
A Figma tutorial in the Intro to Design Systems series, following a product designer as they introduce design tokens into a design system. It covers aliasing, primitive, semantic and component-specific tokens, implementing them with variables and styles, and naming tips.
Apply your variables to flexible components by adding Slots that designers can fill within instances.
Shows how to create Slots, customizable containers inside Figma components that let designers add, modify and organize assets within an instance. Aimed at designers who already build components and design systems in Figma.
Connect finished components to code with Code Connect, so developers see the system's snippets in Figma.
A Config 2024 session from Figma's Tom Lowry and Jake Albaugh on using Code Connect to show a design system's code snippets directly in Figma, so developers can adopt the system more readily. It is aimed at teams maintaining a design system and working between design and code.
Set up the basics of governance: ownership, contribution and review, release rhythm and semantic versioning.
A guide to governing a design system, covering who should own it, how to run contribution and review, setting a release rhythm, semantic versioning with a changelog, showing component lifecycle, writing usable docs, and measuring adoption. It is aimed at people who maintain design systems in practice.
Question how much governance is worth keeping and which practices to drop once the basics are in place.
Michelle and Luke discuss how much governance a design system actually needs, what level is good enough, and which governance practices are not worth keeping. The episode is aimed at people who already maintain a design system.
Weigh adoption as a tactical or cultural challenge, building on how governance shapes who uses the system.
Michelle and Luke discuss why design system adoption has been a persistent problem and whether it should be approached as a tactical or cultural challenge. They also consider whether the goal belongs with design systems teams or the wider organisation. The episode suits people working on design systems who are trying to drive adoption.
Finish with Nathan Curtis on turning system work into roadmaps, backlogs and tracked releases.
Nathan Curtis walks through the process he has used across design system teams over ten years to organise design system work, record scope, assign and track tasks, and release features over time. The talk covers workflow challenges such as repetitive reviews and when to discuss requests, using tools like Asana and Jira.
For designers and content specialists ready to move beyond single assets, this path shows how to build, scale and govern brand identity systems using real company cases and guidelines.
For intermediate designers who want developers to build their designs accurately. You will learn to structure Figma files, prepare designs for handoff, and work alongside engineers.
For designers who already make basic vectors or digital drawings and want polished, distinctive illustrations. You will be able to produce detailed Figma and Photoshop work and set up an illustration system that a whole team can use.
5 lessons · 3 hr 21 min, plus 1 optional
Learning pathIntermediate → AdvancedDesign Systems
For design system leads and designers who want components, guidelines and code to work reliably with AI agents and Figma Make. You will learn to make the system readable to AI and check its output.