Building a Design System in Figma
Stop redesigning the same button five times. Build a real design system — tokens, components, documentation — that scales across products and outlives any single feature.
About this course
Every product team eventually realizes the design files have become unmaintainable — colors duplicated, components forked, dev handoff chaos. The fix is a design system, but most teams build them wrong (over-engineered, under-documented, ignored within six months). This course walks through a real system from first principles: tokens (color, type, spacing), foundational components, composition patterns, and the lightweight docs that keep the team using it.
What you'll cover
- 1
Why design systems fail
The 5 patterns that kill systems. What 'good' actually looks like at Vodafone, Talabat, Vezeeta scale.
- 2
Tokens: color, type, space, radius
The atomic layer. Naming that survives a redesign. Variables vs styles in Figma.
- 3
Foundations: typography, iconography, motion
Type scale that works in EN + AR. Icon kit that scales. Motion principles people actually follow.
- 4
Core components: button, input, modal, card
The components every product needs, built once. Variants that don't explode.
- 5
Composition: from primitives to patterns
Forms, lists, tables. The pattern library that lives between system and product.
- 6
Documentation that doesn't rot
What to document, what to skip. Figma docs vs Notion vs Storybook. Keeping it current.
- 7
Adoption — the hardest part
How to roll out, get buy-in, and build the feedback loop with developers.
Who it's for
Mid-level product designers, design leads at growing startups, and design-curious engineers wanting to influence system architecture.
Prerequisites
You've designed at least one full screen in Figma. Comfortable with components, auto-layout, and basic variants. Worked with a developer at least once.
Skills you'll build
- design systems
- Figma variables
- design tokens
- component libraries
- design ops
- documentation
- Figma
- product design
Who we're looking for
Open call · Apply to teachRequired skills
- design systems
- Figma variables
- design tokens
- component libraries
- design ops
- documentation
- Figma
- product design
Experience
3+ years professional experience
Languages
English or Arabic (both a plus)
Time commitment
8 sessions × 90 min over 6 weeks
Compensation
80% of seat revenue (Tahout takes 20%)
If your CV matches, apply to teach. We use AI to rank applicants by fit, then admin reviews and approves the right instructor(s).
Sign up to apply →