Why design systems scale product design in Figma - Dashboard Impact

Dashboard Mode - Why design systems scale product design

Goal

Understand how design systems help scale product design efficiently across teams and projects.

Sample Data: Design System Usage Metrics

Team	Projects Using Design System	Total Projects	Average Design Time (hours)	Rework Rate (%)
Team A	8	10	40	10
Team B	5	10	55	25
Team C	9	12	38	8
Team D	3	8	60	30
Team E	7	9	42	12

Dashboard Components

• KPI Card: Average Design Time
  Formula: Average Design Time = AVERAGE('DesignData'[Average Design Time (hours)])
  Result: 47 hours
• KPI Card: Average Rework Rate
  Formula: Average Rework Rate = AVERAGE('DesignData'[Rework Rate (%)])
  Result: 17%
• Bar Chart: Projects Using Design System vs Total Projects by Team
  X-axis: Team
  Y-axis: Number of Projects
  Two bars per team: Projects Using Design System and Total Projects
• Line Chart: Average Design Time vs Rework Rate by Team
  X-axis: Team
  Y-axis Left: Average Design Time (hours)
  Y-axis Right: Rework Rate (%)
• Table: Detailed Team Metrics
  Columns: Team, Projects Using Design System, Total Projects, Average Design Time, Rework Rate

Dashboard Layout

+--------------------------------------------------+
| KPI: Average Design Time | KPI: Average Rework Rate |
+--------------------------+-------------------------+
|                                                  |
| Bar Chart: Projects Using Design System vs Total |
|                                                  |
+--------------------------------------------------+
|                                                  |
| Line Chart: Design Time & Rework Rate by Team    |
|                                                  |
+--------------------------------------------------+
|                                                  |
| Table: Detailed Team Metrics                      |
|                                                  |
+--------------------------------------------------+

Interactivity

Filter by Team: Selecting a team filters all charts and the table to show only that team's data.

Toggle Projects View: Switch between viewing projects using the design system and total projects in the bar chart.

Self Check

If you add a filter to show only Team C, which components update?

• Bar Chart updates to show Team C's projects only.
• Line Chart updates to show Team C's design time and rework rate.
• Table filters to Team C's row.
• KPI cards update to reflect Team C's average design time and rework rate.

Key Result

Dashboard shows how design systems reduce design time and rework across teams by comparing project usage and performance metrics.

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