Project Overview

The Everyday Reality

The Pattern I Noticed

Figma’s role in this

Major Channel for Async Feedback
Stakeholders and designers primarily rely on async, in-tool feedback during design stages to preserve visual context.

Most used Design & Collaboration Tool
Figma dominates modern design collaboration, accounting for ~40% of the global design software market.

Isn’t optimized for Good feedback
Figma’s commenting system causes “Figma comments bombs” resulting in endless feedback pins of all sorts.
The Behavioral insight

The Core Problem
So, How might we?
Q. Give feedback a clear beginning and end?
Q. Align feedback with design iterations?
Q. Help designers focus and prioritize?
The Solution

Timed Review Sessions

Comments Grouping

Review Sessions as Versions

Comment Priority Tagging

Impact on Figma

Learnings & Challenges
Feedback problems are rarely about tools alone; they’re about how work moves through time.
I realized structuring a system doesn’t mean restricting people, it means reducing cognitive load.
Small behavioral constraints can unlock large workflow improvements.
Designing for designers means respecting existing habits, not forcing new ones.
A good solution aligns with how work already happens, not how it should happen.
The hardest part was untangling feedback problems without blaming Figma or existing collaboration habits.
It was challenging to simplify a complex, emotional problem without oversimplifying it.
I struggled with deciding what not to design, especially when many ideas felt useful but added complexity.
Keeping the solution lightweight while still meaningful took multiple iterations and resets.
Turning a messy, real-world workflow into a clear narrative was harder than designing the UI itself.
