Why advanced components reduce design debt in Figma - Business Case Study

Scenario Mode

👤 Your Role: You are a product designer working with a team to build a user interface.

📋 Request: Your manager wants you to explain how using advanced components in Figma can reduce design debt over time.

📊 Data: You have data on design updates, bug fixes, and time spent on redesigns for projects using basic components versus advanced components.

🎯 Deliverable: Create a simple report showing the impact of advanced components on reducing design debt and explain it clearly.

Sample Data

Project	Component Type	Design Updates	Bug Fixes	Redesign Hours
Alpha	Basic	15	10	20
Beta	Advanced	5	3	8
Gamma	Basic	12	9	18
Delta	Advanced	4	2	7
Epsilon	Basic	14	11	22
Zeta	Advanced	6	4	9

1

Step 1: Group data by Component Type and calculate total Design Updates, Bug Fixes, and Redesign Hours for each type.

Use SUM aggregation grouped by Component Type for columns Design Updates, Bug Fixes, Redesign Hours.

Expected Result

Basic: Design Updates=41, Bug Fixes=30, Redesign Hours=60; Advanced: Design Updates=15, Bug Fixes=9, Redesign Hours=24

2

Step 2: Calculate average Redesign Hours per Design Update for each Component Type to understand efficiency.

Average Redesign Hours per Update = Redesign Hours / Design Updates for each Component Type.

Expected Result

Basic: 60/41 ≈ 1.46 hours per update; Advanced: 24/15 = 1.6 hours per update

3

Step 3: Create a bar chart comparing total Design Updates, Bug Fixes, and Redesign Hours between Basic and Advanced components.

X-axis: Component Type; Y-axis: Values; Series: Design Updates, Bug Fixes, Redesign Hours.

Expected Result

Chart shows Basic components have higher totals in all categories compared to Advanced components.

4

Step 4: Interpret the results to explain how advanced components reduce design debt.

Summarize that Advanced components lead to fewer design updates and bug fixes, reducing redesign time and design debt.

Expected Result

Advanced components reduce design debt by lowering the need for frequent updates and fixes, saving time and effort.

Final Result

Basic

↓

Advanced

✓Projects using advanced components have significantly fewer design updates and bug fixes.

✓Redesign hours for advanced components are less than half compared to basic components.

✓Using advanced components reduces design debt by minimizing repetitive work and errors.

✓This leads to faster development cycles and better product quality.

Bonus Challenge

Create a dashboard in Figma that visually tracks design debt metrics over time using advanced components.

Show Hint

Use Figma's component variants and auto-layout features to build reusable charts and update them easily.

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