Design Lead: design systems and critique

01

From designer to design lead

In simple words

A box of building bricks works because every brick fits every other brick. Kids can build a castle, a car or a spaceship, and it all still looks like it belongs together. A design system is a box of design bricks, with instructions, so a whole team can build things that fit.

Before this course: Professional Design: typography, client process and files (course 11.1.3). You can already run a client job from enquiry to handoff, set professional typography, check WCAG contrast, manage revision rounds and prepare print and web files. This course is about leading: building a system that other people use, judging other people's work fairly, and teaching what you know.

Key facts

A design system is a shared set of rules and reusable parts that lets many people make consistent designs. A brand kit (course 11.1.2) is a small start; a full system adds rules for how the parts are used and who can change them.
Common layers of a design system:

Layer	What it holds	Example
Foundations (tokens)	Named values for colour, type, spacing, corner radius	"color.text.default = #1F2328"
Components	Reusable parts built from the foundations	Button, input field, card, social post frame
Patterns	Combinations of components that solve a common job	Sign-up form, event poster layout
Guidelines	When and how to use each part, with do and don't examples	"Use one primary button per screen"
Governance	Who decides, how people contribute, how changes are released	Monthly review, version numbers, change log

In Figma (Help Center wording): "Components are elements you can reuse across your designs." A main component defines the properties; an instance is a copy you reuse, and instances "receive any updates made to the component". This link between the main part and its copies is what makes a system fast to update.
A public example: the UK government publishes its GOV.UK Design System. Its contribution criteria say a new component must be useful (evidence that many teams need it) and unique (it does not repeat something already there) before it is developed (Lesson 5).
Start with an audit, not a blank page. Collect screenshots or prints of everything the team already makes (posts, posters, slides, web pages). Group the repeats: how many button styles, how many blues, how many heading sizes? The audit shows what to standardise first.
The design lead's jobs: set the standard, make the system easy to use, review work fairly, teach others, and keep a record of decisions. A lead who keeps rules only in their head becomes a bottleneck.
Decision log: a short dated list of each system decision and the reason ("2026-11-13: one blue for actions, because the audit found seven"). It stops the same argument from happening twice.

Step by step

Pick a real or pretend organisation with at least 10 existing designs (your course 11.1.3 client works well).
Collect all 10 or more designs in one board or folder.
Make an audit table with rows for colours, fonts and sizes, buttons, spacing, logos and image styles.
Count the different versions of each item you find (for example "6 blues, 4 heading sizes").
Circle the items with the most variation: these are your first system decisions.
Start a decision log with the date, the decision and the reason for each one.
Write one paragraph: who will use this system, and for what kinds of designs.
Check: someone reading your audit can see, in one minute, where the designs are inconsistent and what you plan to fix first.

Watch on YouTube

Inside a real design system: Figma's own systemFigma · YouTube · youtube.com

Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.

LESSON 01From designer to design lead

LESSON 01 / ANIMATED LESSON / AI VOICE00:00 / 01:15

Voice

Read the video script

[Host at a table covered in printed posts and posters] "Before you build a design system, look at what the team already makes."
[Screen: audit table showing 6 blues and 4 heading sizes] "Count the differences. Six blues and four heading sizes means people are guessing."
[Text on screen: Foundations. Components. Patterns. Guidelines. Governance.] "A design system has layers: foundations, components, patterns, guidelines and governance."
[Screen: one main component and five linked copies changing together] "Change the main part once, and every linked copy updates."
[Host] "A design lead's job is to make the right choice the easy choice for everyone."

Try it now

Run a design audit for one organisation: an audit table with counts, your top three inconsistencies, and a decision log with at least three dated decisions and reasons.

ClaudeStuck? Copy a ready-made prompt for Claude

Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.

For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.

I'm learning "Design Lead: design systems and critique" on The Future Market. Lesson 1: "From designer to design lead".

What the lesson teaches:
- A design system is a shared set of rules and reusable parts that lets many people make consistent designs. A brand kit (course 11.1.2) is a small start; a full system adds rules for how the parts are used and who can change them.
- Common layers of a design system:
- Layer - What it holds - Example
- Foundations (tokens) - Named values for colour, type, spacing, corner radius - "color.text.default = #1F2328"
- Components - Reusable parts built from the foundations - Button, input field, card, social post frame
- Patterns - Combinations of components that solve a common job - Sign-up form, event poster layout
- Guidelines - When and how to use each part, with do and don't examples - "Use one primary button per screen"

The exercise I'm working on:
Run a design audit for one organisation: an audit table with counts, your top three inconsistencies, and a decision log with at least three dated decisions and reasons.

I'm stuck. Please:
1. Explain the main idea in plain, simple words with one everyday example.
2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step.
3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.

I'm a parent helping my child (about 8 years old) with a lesson called "From designer to design lead" from the course "Design Lead: design systems and critique".

Here's what the lesson says:
A box of building bricks works because every brick fits every other brick. Kids can build a castle, a car or a spaceship, and it all still looks like it belongs together. A design system is a box of design bricks, with instructions, so a whole team can build things that fit.

The activity:
Run a design audit for one organisation: an audit table with counts, your top three inconsistencies, and a decision log with at least three dated decisions and reasons.

Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words.
Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.

Open Claude

Sources

Figma Help Center, Guide to components in Figma: help.figma.com/hc/en-us/articles/360038662654-Guide-to-components-in-F
GOV.UK Design System, Contribution criteria: design-system.service.gov.uk/community/contribution-criteria/

My notes

I learned this

02