Why advanced components reduce design debt in Figma - Dashboard Impact

Dashboard Mode - Why advanced components reduce design debt

Goal

Understand how using advanced components in design tools like Figma helps reduce design debt and improves project efficiency.

Sample Data

Project	Component Type	Number of Components	Design Debt Score	Time to Update (hours)
App Redesign	Basic Components	50	75	20
App Redesign	Advanced Components	30	30	8
Website Refresh	Basic Components	40	65	18
Website Refresh	Advanced Components	25	25	7
Marketing Campaign	Basic Components	35	70	15
Marketing Campaign	Advanced Components	20	20	5

Dashboard Components

• KPI Card: Average Design Debt Score
  Formula: Average of 'Design Debt Score' grouped by Component Type.
  Result: Basic Components = 70, Advanced Components = 25
• KPI Card: Average Time to Update (hours)
  Formula: Average of 'Time to Update' grouped by Component Type.
  Result: Basic Components = 17.7, Advanced Components = 6.7
• Bar Chart: Number of Components by Project and Type
  X-axis: Project
  Y-axis: Number of Components
  Bars grouped by Component Type (Basic vs Advanced)
• Line Chart: Design Debt Score vs Time to Update
  X-axis: Design Debt Score
  Y-axis: Time to Update
  Lines for Basic and Advanced Components showing correlation
• Data Table
  Shows all sample data for detailed view

Dashboard Layout

+----------------------+----------------------+
|  KPI: Avg Design Debt | KPI: Avg Time Update |
|        Score          |       (hours)        |
+----------------------+----------------------+
|                                              |
|           Bar Chart: Number of Components    |
|                                              |
+----------------------------------------------+
|                                              |
|    Line Chart: Design Debt vs Time to Update |
|                                              |
+----------------------------------------------+
|                                              |
|                 Data Table                    |
|                                              |
+----------------------------------------------+

Interactivity

A filter for Component Type (Basic or Advanced) updates all components: KPI cards, charts, and table. Selecting 'Advanced Components' shows lower design debt and update times. Selecting 'Basic Components' highlights higher design debt and longer update times.

A project filter lets users focus on one project, updating all visuals accordingly.

Self Check

If you add a filter for Project = "Website Refresh", which components update?

• Both KPI cards update to show averages for Website Refresh only.
• Bar chart shows number of components for Website Refresh projects only.
• Line chart updates to show Design Debt vs Time to Update for Website Refresh.
• Data table filters to Website Refresh rows.

Key Result

Dashboard shows how advanced components reduce design debt and update time across projects.

Practice

1. Why do advanced components help reduce design debt in Figma?

easy

A. Because they allow changes to update everywhere automatically

B. Because they make designs look more colorful

C. Because they increase the file size significantly

D. Because they require manual updates for each instance

Solution

1. Step 1: Understand design debt

   Design debt happens when many manual fixes are needed across files, causing extra work.

2. Step 2: Role of advanced components

   Advanced components update all instances automatically when changed, reducing repeated manual fixes.

3. Final Answer:

   Because they allow changes to update everywhere automatically -> Option A

4. Quick Check:

   Automatic updates = Reduced design debt [OK]

Hint: Think: one change, many updates [OK]

Common Mistakes:

• Confusing color changes with design debt
• Thinking manual updates reduce debt
• Believing file size affects design debt

2. Which of the following is the correct way to create a variant in Figma's advanced components?

easy

A. Create separate files for each component variant

B. Manually copy and paste components without grouping

C. Use the 'Flatten' option on components

D. Select components and click 'Combine as Variants'

Solution

1. Step 1: Identify variant creation method

   Figma allows combining components into variants using the 'Combine as Variants' feature.

2. Step 2: Eliminate incorrect methods

   Copy-paste, flattening, or separate files do not create variants properly.

3. Final Answer:

   Select components and click 'Combine as Variants' -> Option D

4. Quick Check:

   Combine as Variants = Correct variant creation [OK]

Hint: Variants combine components in one set [OK]

Common Mistakes:

• Using flatten instead of variants
• Copy-pasting without grouping
• Separating variants into different files

3. Given a nested advanced component with variants for button states (default, hover, disabled), what happens when you update the color in the main button component?

medium

A. No variants update unless edited individually

B. All button variants update their color automatically

C. Only the default variant updates, others stay the same

D. The file crashes due to nested variants

Solution

1. Step 1: Understand nested components and variants

   Nested components with variants share properties from the main component.

2. Step 2: Effect of updating main component

   Changing the main component's color updates all variants automatically because they inherit from it.

3. Final Answer:

   All button variants update their color automatically -> Option B

4. Quick Check:

   Nested variants inherit updates = All button variants update their color automatically [OK]

Hint: Main component changes affect all variants [OK]

Common Mistakes:

• Thinking only default variant updates
• Believing manual edits are always needed
• Assuming file crashes with nested variants

4. You notice that after updating a nested component's style, some instances do not reflect the change. What is the most likely cause?

medium

A. Figma does not support nested components

B. The main component was deleted accidentally

C. Instances have local overrides blocking updates

D. Variants were not combined properly

Solution

1. Step 1: Identify why instances don't update

   Local overrides on instances prevent automatic updates from the main component.

2. Step 2: Rule out other causes

   Main component deletion or variant issues cause errors, but not selective update blocking. Figma supports nested components.

3. Final Answer:

   Instances have local overrides blocking updates -> Option C

4. Quick Check:

   Local overrides block updates = Instances have local overrides blocking updates [OK]

Hint: Check for local overrides on instances [OK]

Common Mistakes:

• Assuming main component was deleted
• Blaming variant combination errors
• Thinking nested components are unsupported

5. How can using nested advanced components with variants improve scalability and reduce design debt in a large design system?

hard

A. By allowing centralized updates and flexible variant combinations

B. By forcing designers to recreate components for each use

C. By increasing manual work for each design change

D. By limiting component reuse to only one variant

Solution

1. Step 1: Understand nested components and variants in scalability

   Nested components with variants let you build flexible, reusable parts that update centrally.

2. Step 2: Benefits for design debt

   Central updates reduce repeated fixes and manual changes, lowering design debt and improving efficiency.

3. Final Answer:

   By allowing centralized updates and flexible variant combinations -> Option A

4. Quick Check:

   Central updates + variants = scalable, less debt [OK]

Hint: Centralize updates, combine variants for scale [OK]

Common Mistakes:

• Thinking components must be recreated each time
• Believing manual updates increase efficiency
• Assuming variants limit reuse