Why design systems scale product design in Figma - Business Case Study

Scenario Mode

👤 Your Role: You are a product designer at a growing tech company.

📋 Request: Your manager wants you to explain how using a design system helps scale product design efficiently.

📊 Data: You have data on design time, consistency issues, and team collaboration before and after implementing a design system.

🎯 Deliverable: Create a simple dashboard in Figma that shows the impact of design systems on scaling product design with clear visuals and key metrics.

Sample Data

Metric	Before Design System	After Design System
Average Design Time per Feature (hours)	12	7
Design Consistency Issues (per month)	15	3
Number of Designers	4	8
Collaboration Efficiency (scale 1-10)	5	8
Rework Rate (%)	20	5

1

Step 1: Create a new Figma file and set up a clean frame for your dashboard.

Frame size: 1200px width x 800px height; background color: light gray (#F5F5F5).

Expected Result

A blank dashboard canvas ready for design.

2

Step 2: Add a title text at the top center: 'Impact of Design Systems on Product Design Scaling'.

Text size: 24pt, font: Inter Bold, color: #333333, center aligned.

Expected Result

Clear, readable dashboard title.

3

Step 3: Create a bar chart comparing 'Average Design Time per Feature' before and after using the design system.

X-axis: 'Before' and 'After'; Y-axis: hours from 0 to 15; Bars: Before=12 hours (red), After=7 hours (green).

Expected Result

Visual showing design time reduced after design system implementation.

4

Step 4: Create a bar chart for 'Design Consistency Issues' before and after.

X-axis: 'Before' and 'After'; Y-axis: issues from 0 to 20; Bars: Before=15 (red), After=3 (green).

Expected Result

Visual showing fewer consistency issues after design system.

5

Step 5: Add a numeric KPI card showing 'Collaboration Efficiency' scores before and after.

Two cards side by side: Before=5, After=8; use icons and color coding (red for before, green for after).

Expected Result

Easy to read collaboration improvement metric.

6

Step 6: Add a small text box summarizing key benefits: 'Design systems reduce design time, improve consistency, and boost collaboration.'

Font size: 14pt, color: #555555, placed below charts.

Expected Result

Clear summary reinforcing the data insights.

7

Step 7: Ensure all elements have sufficient color contrast and use accessible fonts for readability.

Check color contrast ratio > 4.5:1; use font Inter or similar sans-serif.

Expected Result

Dashboard is accessible and easy to read for all users.

Final Result

████████████

↓

███████████████

✓Design time per feature dropped from 12 to 7 hours after using a design system.

✓Design consistency issues decreased from 15 to 3 per month.

✓Collaboration efficiency improved from a score of 5 to 8.

✓Design systems help scale product design by saving time and improving quality.

Bonus Challenge

Add an interactive prototype in Figma that allows toggling between 'Before' and 'After' views to highlight changes dynamically.

Show Hint

Use Figma's interactive components and variants to create toggle buttons that switch chart states.

Practice

1. What is the main benefit of using a design system in product design?

easy

A. It helps reuse components to speed up design.

B. It increases the number of unique colors used.

C. It makes the product design more complex.

D. It removes the need for any collaboration.

Solution

1. Step 1: Understand design system purpose

   A design system is created to reuse components and speed up the design process.

2. Step 2: Compare options

   Only It helps reuse components to speed up design. correctly states the main benefit of speeding up design by reusing components.

3. Final Answer:

   It helps reuse components to speed up design. -> Option A

4. Quick Check:

   Design systems speed up design = B [OK]

Hint: Focus on reuse and speed benefits of design systems [OK]

Common Mistakes:

• Thinking design systems increase complexity
• Believing design systems reduce collaboration
• Confusing color variety with design system purpose

2. Which of the following is the correct way to describe a design system in Figma?

easy

A. A set of reusable components and styles.

B. A collection of unrelated images and icons.

C. A random assortment of colors.

D. A single static image used in all designs.

Solution

1. Step 1: Define design system in Figma

   In Figma, a design system is a set of reusable components and styles to keep consistency.

2. Step 2: Eliminate incorrect options

   Options B, C, and D describe unrelated or static elements, not a system of reusable parts.

3. Final Answer:

   A set of reusable components and styles. -> Option A

4. Quick Check:

   Reusable components = A [OK]

Hint: Remember design systems are reusable parts, not random items [OK]

Common Mistakes:

• Confusing design systems with random images
• Thinking design systems are single images
• Ignoring the reuse and style aspect

3. In a team using a design system, what is the expected result when a button component is updated in the system?

medium

A. No buttons change unless manually edited.

B. Only new buttons created after update change.

C. The design system breaks and stops working.

D. All buttons in the product update automatically.

Solution

1. Step 1: Understand component update behavior

   When a component in a design system is updated, all instances of that component update automatically.

2. Step 2: Analyze options

   All buttons in the product update automatically. correctly states this automatic update. Options A and B are incorrect because they imply manual updates or partial changes. The design system breaks and stops working. is incorrect as updates do not break the system.

3. Final Answer:

   All buttons in the product update automatically. -> Option D

4. Quick Check:

   Component update = automatic change [OK]

Hint: Component updates reflect everywhere instantly [OK]

Common Mistakes:

• Thinking updates affect only new components
• Believing manual edits are needed after update
• Assuming system breaks on update

4. A designer notices inconsistent button styles across screens despite using a design system. What is the most likely cause?

medium

A. The colors in the design system are random.

B. The design system automatically updates all buttons.

C. They used local copies instead of components from the design system.

D. The design system does not support buttons.

Solution

1. Step 1: Identify cause of inconsistency

   Inconsistent styles usually happen if designers use local copies instead of linked components from the design system.

2. Step 2: Evaluate options

   They used local copies instead of components from the design system. correctly identifies this cause. The design system automatically updates all buttons. is false because automatic updates prevent inconsistency. The design system does not support buttons. is unlikely as design systems include buttons. The colors in the design system are random. is irrelevant to style consistency.

3. Final Answer:

   They used local copies instead of components from the design system. -> Option C

4. Quick Check:

   Local copies cause inconsistency = D [OK]

Hint: Check if components are linked or local copies [OK]

Common Mistakes:

• Assuming design system updates cause inconsistency
• Thinking design systems exclude buttons
• Blaming random colors for style issues

5. A product team wants to speed up design and keep consistent branding across multiple apps. How should they best use a design system in Figma?

hard

A. Design each app separately with unique styles for flexibility.

B. Create reusable components and shared styles, then enforce their use across all apps.

C. Use only images and icons without components.

D. Avoid using any design system to save time.

Solution

1. Step 1: Identify best practice for scaling design

   To speed up design and keep branding consistent, teams create reusable components and shared styles in a design system.

2. Step 2: Analyze options for team approach

   Create reusable components and shared styles, then enforce their use across all apps. describes this best practice. Design each app separately with unique styles for flexibility. sacrifices consistency. Use only images and icons without components. ignores components. Avoid using any design system to save time. contradicts the goal of saving time.

3. Final Answer:

   Create reusable components and shared styles, then enforce their use across all apps. -> Option B

4. Quick Check:

   Reusable components + shared styles = A [OK]

Hint: Use shared components and styles for consistency and speed [OK]

Common Mistakes:

• Designing apps separately losing consistency
• Ignoring components in favor of images
• Avoiding design systems to save time