Design review workflows in Figma - Step-by-Step Guide

Introduction

Design review workflows help teams check and improve designs together. They make it easy to share feedback and track changes in a clear way.

When you want to get feedback from your team on a new dashboard design before publishing

When you need to share a report layout with stakeholders for approval

When multiple people need to comment on a prototype to improve usability

When you want to keep all design feedback organized in one place

When you want to track changes and decisions made during design discussions

Steps

Step 1: Open the design file

- Figma desktop app or web app

The design you want to review appears on screen

Step 2: Click the 'Share' button

- Top-right corner of the Figma window

A sharing dialog opens with link and permission options

Step 3: Set permissions to 'Can view' or 'Can comment'

- Sharing dialog under 'Invite people' section

People with the link can view or comment but not edit the design

💡 Choose 'Can comment' to allow feedback without changing the design

Step 4: Copy the shareable link

- Sharing dialog link field

Link is copied to clipboard for sharing

Step 5: Send the link to reviewers

- Email, chat, or project management tool

Reviewers receive the link and can open the design

Step 6: Reviewers add comments

- Figma design canvas using the comment tool

Comments appear as pins on the design for specific feedback

Step 7: Track and resolve comments

- Comments panel on the right side

Comments are marked as resolved when addressed, keeping workflow organized

Before vs After

Before

Design file is shared only with editors, no external feedback collected

After

Design file is shared with reviewers who add organized comments visible to the team

Settings Reference

Sharing permissions

📍 Share dialog > Invite people section

Control what reviewers can do with the design file

Default: Can view

Comment visibility

📍 Comments panel

Filter comments to focus on open feedback

Default: Show all comments

Common Mistakes

Sharing the design with 'Can edit' permission to all reviewers

Reviewers might accidentally change the design instead of just commenting

Set permission to 'Can comment' to allow feedback without editing

Not resolving comments after addressing feedback

Unresolved comments clutter the workspace and confuse the team

Mark comments as resolved to keep the review process clear

Summary

Design review workflows let teams share designs and collect feedback easily.

Use sharing permissions to control who can comment or edit.

Track and resolve comments to keep feedback organized and clear.

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