Design review workflows in Figma - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the purpose of design review workflows

Why are design review workflows important in Business Intelligence projects?

A They ensure data accuracy and consistency before visualization.

B They speed up the coding process by skipping testing.

C They focus only on the visual style without checking data.

D They replace the need for user feedback entirely.

💡 Hint

Think about what happens if data errors reach the final report.

Design review workflows help catch data and design issues early, ensuring reports are accurate and trustworthy.

🎯 Scenario

intermediate

Choosing the right review step for a dashboard

You created a sales dashboard. What is the best next step in a design review workflow?

A Skip testing and start a new project.

B Publish the dashboard immediately without review.

C Delete the dashboard and start over.

D Share the dashboard with stakeholders for feedback.

💡 Hint

Think about involving others to improve the design.

Sharing with stakeholders allows gathering feedback to improve the dashboard before final release.

❓ visualization

advanced

Identifying issues in a design review workflow visualization

Look at this workflow diagram showing design review steps. Which issue would cause confusion?

Diagram steps: Draft design → Internal review → Stakeholder review → Final approval → Publish

A Including stakeholder review before internal review.

B Missing feedback loops to earlier steps.

C Publishing before final approval.

D Having too many steps in the workflow.

💡 Hint

Think about how feedback is handled in workflows.

Without feedback loops, reviewers cannot request changes, causing confusion and poor quality.

🔧 Formula Fix

advanced

Fixing a broken design review workflow in Figma

You notice reviewers are skipping the 'Internal review' step in your Figma workflow prototype. What is the most likely cause?

A The prototype link skips the internal review frame due to incorrect navigation setup.

B The internal review step is too detailed and reviewers avoid it.

C The colors used in the internal review frame are dull.

D The prototype has too many frames overall.

💡 Hint

Check how users move between frames in the prototype.

If navigation is not set correctly, users can skip steps unintentionally.

❓ data_modeling

expert

Optimizing a design review workflow for BI projects

You want to optimize your design review workflow to reduce delays but keep quality high. Which approach best balances speed and thoroughness?

A Only do final approval without earlier reviews.

B Remove stakeholder review to save time.

C Automate data validation checks before manual reviews.

D Skip internal review and rely on publishing feedback.

💡 Hint

Think about using automation to reduce manual work without losing quality.

Automating data validation reduces errors early, speeding up the process while keeping quality high.

Practice

1. What is the main purpose of design review workflows in Figma?

easy

A. To export designs as images only

B. To create new design files from scratch

C. To write code for design automation

D. To help teams give and track feedback easily

Solution

1. Step 1: Understand design review workflows

   Design review workflows focus on collaboration and feedback during design creation.

2. Step 2: Identify the main goal in Figma context

   Figma uses comments and approvals to track feedback and finalize designs smoothly.

3. Final Answer:

   To help teams give and track feedback easily -> Option D

4. Quick Check:

   Design review workflows = feedback tracking [OK]

Hint: Think collaboration and feedback tracking in design [OK]

Common Mistakes:

• Confusing design creation with review process
• Thinking workflows are for coding or exporting only
• Ignoring feedback tracking as a key purpose

2. Which Figma feature is primarily used to link feedback directly to specific parts of a design during review?

easy

A. Layers panel

B. Comments

C. Prototype links

D. Export settings

Solution

1. Step 1: Identify feedback tools in Figma

   Comments allow users to leave notes tied to exact design areas.

2. Step 2: Compare with other features

   Layers panel organizes design elements, prototypes link screens, exports save files; none link feedback directly.

3. Final Answer:

   Comments -> Option B

4. Quick Check:

   Feedback linked to design = Comments [OK]

Hint: Feedback linked to design parts means comments [OK]

Common Mistakes:

• Choosing Layers panel which only organizes elements
• Confusing prototype links with feedback tools
• Selecting export settings unrelated to feedback

3. In a Figma design review, if a comment is marked as resolved, what happens to it?

medium

A. It is hidden from the main view but can be accessed later

B. It sends an email notification to all team members

C. It automatically deletes the related design element

D. It disappears permanently from the file

Solution

1. Step 1: Understand comment resolution in Figma

   Resolved comments are hidden from the main view to reduce clutter but remain accessible.

2. Step 2: Eliminate incorrect options

   Comments do not delete design elements or disappear permanently; email notifications are manual.

3. Final Answer:

   It is hidden from the main view but can be accessed later -> Option A

4. Quick Check:

   Resolved comment = hidden, not deleted [OK]

Hint: Resolved comments hide but stay accessible [OK]

Common Mistakes:

• Thinking resolved comments delete design parts
• Assuming comments vanish permanently
• Believing resolution triggers automatic emails

4. You notice that team members cannot add comments on a shared Figma file during review. What is the most likely cause?

medium

A. The file has too many layers to comment on

B. Comments are disabled by default in Figma

C. The file is set to 'View only' access for those members

D. The file is not saved properly

Solution

1. Step 1: Check access permissions in Figma

   Only users with 'Can edit' or 'Can comment' access can add comments; 'View only' restricts commenting.

2. Step 2: Review other options

   Layer count does not block comments, comments are enabled by default, and saving issues do not restrict commenting.

3. Final Answer:

   The file is set to 'View only' access for those members -> Option C

4. Quick Check:

   Access level controls commenting ability [OK]

Hint: Check if users have comment or edit access [OK]

Common Mistakes:

• Blaming layer count for comment issues
• Thinking comments are off by default
• Assuming saving errors block commenting

5. A team wants to finalize a design in Figma after multiple rounds of feedback. Which workflow step ensures the design is officially approved and ready for handoff?

hard

A. Resolving all comments and marking the design as approved

B. Deleting all comments to clean the file

C. Duplicating the file for backup before sharing

D. Exporting the design as PNG images

Solution

1. Step 1: Understand finalizing design workflows

   Final approval involves resolving comments and marking the design approved to confirm readiness.

2. Step 2: Evaluate options for official approval

   Deleting comments removes feedback history, exporting images is for delivery, duplicating file is backup but not approval.

3. Step 3: Identify the best step for official approval

   Resolving comments and marking approved is the key step to finalize design for handoff.

4. Final Answer:

   Resolving all comments and marking the design as approved -> Option A

5. Quick Check:

   Final approval = resolve comments + approve [OK]

Hint: Final approval means resolve comments and mark approved [OK]

Common Mistakes:

• Deleting comments instead of resolving them
• Confusing backup with approval
• Thinking exporting images finalizes design