How to Get Client Feedback on Figma - CourtneyR.dev's 2nd Brain

How to Get Client Feedback on Figma ![rw-book-cover](https://img.youtube.com/vi/Vk2P8TN6YoY/maxresdefault.jpg) 🔗 **Source:** [How to Get Client Feedback on Figma](https://www.youtube.com/watch?v=Vk2P8TN6YoY) > [!note]+ Document Notes > tags: #figma #design-feedback #client-collaboration #version-control #design-handoff > author: VTOS > source: YouTube > reference: https://www.youtube.com/watch?v=Vk2P8TN6YoY > date created: 2024-12-19 18:42 > > # 🏷️ Title: How to Get Client Feedback on Figma (The Right Way) >  ## 🧰 Action Inbox - [H1] Set up Figma plugin integration with collaboration platform — streamline design handoff workflow #design-handoff - [H2] Create standardized feedback process with version control — eliminate revision confusion #version-control - [H3] Configure project management automation between design tools and Jira/Asana — reduce manual sync work #automation ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [Figma Plugin Directory](https://figma.com/community/plugins) - [Design Collaboration Best Practices](https://figma.com/best-practices/) ## 📝 Summary - What happened: VTOS demonstrates a new workflow for collecting client feedback on Figma designs using a specialized collaboration platform instead of native Figma comments - Why it matters: Traditional Figma commenting lacks proper handoff organization, version control, task management, and client-focused interfaces - Key stakeholders: Design teams, clients, project managers, external stakeholders - Risks and tradeoffs: Adds another tool to the workflow but provides structured feedback management and clear version tracking - Bottom line: Structured feedback platforms offer better organization, version control, and client experience than native Figma comments ## 📖 Main Content The video demonstrates a workflow that replaces Figma's native commenting system with a dedicated feedback platform. The presenter argues that while Figma excels as a design canvas for exploration, it's poorly suited for structured feedback collection. The new workflow involves using a Figma plugin to export specific design frames to a collaboration platform that provides better organization, version tracking, and client interfaces. Key technical improvements include support for multiple file formats (PDFs, PSDs, Illustrator files, DWG), integrated project management automation, and purpose-built feedback interfaces. The system addresses common pain points in design handoffs: cluttered workspaces, unclear revision tracking, and clients getting lost in exploratory design canvases. The workflow transforms the traditional 30-minute design handoff process into a 1-minute export operation while providing superior feedback management capabilities. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/Vk2P8TN6YoY?t=0) — [H1] New file format support and Figma integration - Key idea: Platform now supports PDFs, PSDs, Illustrator files, and DWG files with direct Figma plugin access - Evidence: "You can now upload PDFs, PSDs, files, Illustrator files, and even DWG files for floor planning" #### ⏱️ [01:15](https://youtu.be/Vk2P8TN6YoY?t=75) — [H2] Standard Figma workspace challenges - Key idea: Typical Figma files contain cluttered workspaces with wireframes, iterations, and experimental elements - Evidence: "Most people coming into here would know what to kind of do with this" #### ⏱️ [01:45](https://youtu.be/Vk2P8TN6YoY?t=105) — [H3] Traditional handoff time requirements - Key idea: Standard design handoff requires significant cleanup and organization time - Evidence: "The designer now has to go through a handoff process tidying up naming the different elements... That alone takes a bunch of time" #### ⏱️ [02:00](https://youtu.be/Vk2P8TN6YoY?t=120) — [H1] Plugin workflow demonstration - Key idea: Figma plugin allows direct export of specific frames to organized feedback projects - Evidence: "I'll just click here and we go to plugins and choose other within the plugin" #### ⏱️ [03:30](https://youtu.be/Vk2P8TN6YoY?t=210) — [H2] Project organization and client instructions - Key idea: Feedback platform allows clear project organization with stakeholder instructions - Evidence: "We have this prompted asking us to give a description for the people that are going to come in" #### ⏱️ [04:15](https://youtu.be/Vk2P8TN6YoY?t=255) — [H3] Team invitation and sharing process - Key idea: Simple link sharing enables team collaboration without complex setup - Evidence: "It's really as simple as just copying this link and sharing this with others" #### ⏱️ [05:00](https://youtu.be/Vk2P8TN6YoY?t=300) — [H1] First advantage: Speed of handoff - Key idea: New workflow reduces 30-minute handoff to 1-minute process - Evidence: "You just saw me doing a handoff in literally a minute. What usually takes half an hour of setting things up was just done" #### ⏱️ [05:30](https://youtu.be/Vk2P8TN6YoY?t=330) — [H1] Second advantage: Feedback depth and control - Key idea: Advanced task management features unavailable in native Figma comments - Evidence: "You can prioritize, assign to different team members, set the status for the different task... You have due dates for the single task" #### ⏱️ [06:45](https://youtu.be/Vk2P8TN6YoY?t=405) — [H1] Third advantage: Version control tracking - Key idea: Clear version history shows design progression and iteration count - Evidence: "There's no way of knowing how many revision rounds you've had when you're working inside Figma" #### ⏱️ [07:30](https://youtu.be/Vk2P8TN6YoY?t=450) — [H2] Version control demonstration - Key idea: Adding new design versions creates trackable progression history - Evidence: "Now this one has two versions within it... you can see that now I have version two and version one" #### ⏱️ [08:15](https://youtu.be/Vk2P8TN6YoY?t=495) — [H1] Fourth advantage: Purpose-built feedback interface - Key idea: Linear feedback interface better suited than exploratory canvas design - Evidence: "Figma is an open space, a canvas that allows you to go in all kinds of different directions as you explore... while feedback is linear" #### ⏱️ [09:00](https://youtu.be/Vk2P8TN6YoY?t=540) — [H3] Project management integration - Key idea: Two-way automation with popular project management tools - Evidence: "You can streamline all of these communications into your favorite project management system. Automate the two-way comments between here and Jira and Asana" #### ⏱️ [09:30](https://youtu.be/Vk2P8TN6YoY?t=570) — [H2] Client experience demonstration - Key idea: Guest/client interface designed specifically for feedback provision - Evidence: "Let's go into the guest flow the client flow to see what has changed over there" ## 📚 References - [Figma Community Plugins](https://figma.com/community/plugins) - [Design System Handoff Guidelines](https://figma.com/best-practices/components-styles-and-shared-libraries/) - [Client Feedback Best Practices](https://figma.com/blog/design-feedback/) ## 🗣️ Paraphrase - Traditional Figma commenting creates messy feedback workflows because design canvases mix exploration with presentation, requiring significant cleanup time before client review - Dedicated feedback platforms provide structured task management with priority assignment, due dates, version tracking, and client-focused interfaces that native Figma lacks - Version control visibility helps teams and clients understand design progression and set boundaries on revision rounds that would otherwise continue indefinitely ## 📰 Newsletter **Streamline Your Design Feedback Process Beyond Native Figma Comments** Design handoffs don't have to be a 30-minute cleanup nightmare. A new workflow using specialized feedback platforms can transform your Figma collaboration process into a 1-minute export with superior organization and client experience. Key benefits include automatic project organization, advanced task management with due dates and assignments, clear version control tracking, and purpose-built client interfaces. The system integrates directly with project management tools like Jira and Asana for seamless workflow automation. **Try This**: Next time you're preparing design feedback, consider whether your clients really need to navigate your exploratory Figma workspace or if a linear, organized feedback interface would serve them better. Resources: [Figma Plugin Directory](https://figma.com/community/plugins), [Design Handoff Best Practices](https://figma.com/best-practices/), [Client Communication Guide](https://figma.com/blog/design-feedback/) ## ✅ Action Items #### DevRel - Developer advocacy: Create demo showing plugin integration workflow for design team audiences - Education: Develop workshop curriculum on design feedback tool evaluation and implementation - Developer experience: Document API integration patterns for design tool plugins - Developer marketing: Partner with design tool companies for co-marketing case studies - Community management: Moderate discussions on design workflow optimization #### Community - Maintainers: Support plugin developers with feedback platform integration guidelines - Contributors: Encourage contributions to open-source design feedback tools and standards - Sponsors: Connect design tool companies with workflow optimization initiatives - Ecosystem: Facilitate collaboration between design platform vendors and feedback tool creators #### WordPress - Design: Evaluate design feedback workflows for WordPress.org projects and core design reviews - Documentation: Create guidelines for design review processes in open-source WordPress projects - Community: Share design collaboration best practices at WordCamps and design meetups - Training: Develop lesson plans on design feedback and client communication for WordPress designers ## 🧪 Hypotheses - Design teams using structured feedback platforms complete revision cycles 50% faster than those using native Figma comments - Clients provide more actionable feedback when using purpose-built feedback interfaces compared to navigating design exploration canvases - Version control visibility reduces average project revision rounds by 25% through clear progression tracking - Integration between design feedback tools and project management systems reduces administrative overhead by 40% ### 📊 Methodology - Study design: Compare feedback cycle times between native Figma comments and structured feedback platforms across 50 design projects - Data sources: Time tracking for handoff preparation, client response quality metrics, revision round counts, and client satisfaction surveys - Experiments: A/B test client feedback quality using Figma comments versus dedicated feedback platforms with the same design content ### ❓ Questions - How does feedback quality differ between exploratory canvas interfaces and linear feedback tools? - What specific task management features have the highest impact on design revision efficiency? - How do version control visibility features affect client expectations and project scope creep? ### 🔮 Future Research - Investigate optimal feedback interface design patterns for different stakeholder types (technical vs non-technical) - Explore automation opportunities between design tools and project management platforms - Study the impact of structured feedback workflows on designer productivity and client satisfaction ### 💡 Implications - Practice: Design teams should evaluate whether their current feedback collection methods match their workflow needs and client capabilities - Policy: Organizations may need new guidelines for tool selection and client communication in design projects - Security: Third-party feedback platforms require evaluation of data protection and client confidentiality measures - Education: Design education should include training on feedback workflow optimization and client communication best practices - Funding: Investment in specialized feedback tools may provide significant ROI through time savings and improved client relationships ### 🧠 Learning Styles Assessment Reading level estimate: 10th grade #### 👀 Visual learners - Present: Screen recordings showing plugin workflow, before/after workspace comparisons - Improve: Workflow diagrams, feature comparison charts, client journey visualizations #### 🔊 Aural learners - Present: Video narration explaining each workflow step and benefit - Improve: Audio-only version highlighting key decision points and time savings #### 🗣️ Verbal learners - Present: Clear explanations of technical terms, step-by-step process descriptions - Improve: Glossary of design handoff terminology, analogies comparing canvas vs linear interfaces #### 🧩 Kinesthetic learners - Present: Hands-on demonstration of plugin installation and project setup - Improve: Interactive tutorial, downloadable Figma template files, practice exercises #### 🧠 Logical learners - Present: Four-point structured argument, time comparisons, feature matrices - Improve: Decision trees for tool selection, ROI calculations, workflow optimization frameworks #### 🧑‍🤝‍🧑 Social learners - Present: Team collaboration scenarios, client interaction examples - Improve: Discussion prompts for team evaluation, peer review checklists #### 🧘‍♀️ Solitary learners - Present: Individual workflow demonstration, personal productivity benefits - Improve: Self-assessment questionnaire for current feedback process, reflection prompts #### 🌿 Naturalistic learners - Present: Workflow ecosystem thinking, tool integration connections - Improve: Systems thinking approach to design tool selection, environmental impact considerations ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Video has spoken narration describing visual actions - Improve: Detailed alt text for workflow screenshots, structured heading hierarchy #### Keyboard navigation - Present: Plugin interfaces presumably support standard keyboard navigation - Improve: Verify all feedback platform features are keyboard accessible #### Contrast and readability - Present: Video demonstration shows interface contrast levels - Improve: Verify feedback platform meets WCAG 2.2 contrast requirements #### Text resizing and reflow - Present: Plugin interfaces should support browser zoom - Improve: Test feedback platform responsive design at 200% zoom #### Media and captions - Present: Video narration available - Improve: Add closed captions, provide transcript download #### Forms and interactions - Present: Plugin setup and feedback forms shown in demo - Improve: Verify form labels, error handling, and submission feedback #### Standards reference - Map feedback platform accessibility to WCAG 2.2 AA success criteria 1.3.1 (Info and Relationships), 2.1.1 (Keyboard), 2.4.6 (Headings and Labels) ### 🌍 DEIB Assessment #### Cultural breadth - Present: Workflow applicable across different design cultures and practices - Improve: Examples from diverse design teams, international client scenarios #### Inclusive language - Present: Professional terminology, avoids design jargon where possible - Improve: Define technical terms, provide plain-language summaries #### Neurodiversity support - Present: Structured workflow reduces cognitive load of scattered feedback - Improve: Consistent interface patterns, clear task organization #### Representation - Present: Focus on workflow rather than personal characteristics - Improve: Diverse client and team examples, inclusive imagery #### Psychological safety - Present: Emphasizes reducing client confusion and designer stress - Improve: Guidelines for respectful feedback, conflict resolution resources ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Premises about Figma's exploratory nature and feedback's linear needs logically support conclusion about interface mismatch - Inductive strength: Time savings claim (30 minutes to 1 minute) based on demonstrated example, though sample size is small - Causal reasoning: Clear causal chain from cluttered workspace to time-consuming handoff to client confusion - Analogical strength: Canvas/exploration vs linear/feedback analogy effectively illustrates core interface design difference #### Fallacies - False dichotomy: Presents only two options (Figma comments vs specialized platform) without considering hybrid approaches or Figma improvements - Hasty generalization: Extrapolates time savings from single demonstration to universal claim without broader testing #### Tone of voice - Overall tone: Professional and demonstrative with enthusiastic confidence in the solution, occasionally promotional but maintains educational focus ### 🛡️ DARVO Analysis - Deny: No denial patterns present - acknowledges Figma's strengths for its intended purpose - Attack: No attacks on users or competing tools - focuses on workflow limitations rather than tool criticism --- ## Full Transcript [00:03] We have a packed update for you today. [00:06] Let's dive in. First of all, you can now [00:07] upload PDFs, PSDs, [00:10] files, Illustrator files, and even DWG [00:13] files for floor planning, which was an [00:15] interesting use case we've been seeing [00:16] recently. Plus, this all ties together [00:19] with the brand new Figma plug-in that [00:21] you can now access directly from here. [00:23] This means that you can now collaborate [00:25] within Ador on presentations, mockup [00:27] imported directly from Figma, ad [00:30] campaigns, social media campaigns, [00:31] anything that we would need to [00:32] collaborate on from a visual perspective [00:35] beyond the web tools that we already [00:37] have. So, how about we set up a Figma [00:39] project for feedback so you can see that [00:41] handoff process, how easy it is and why [00:43] it makes sense to drop the Figma [00:45] comments in favor of this new workflow. [00:47] So, as you can see, we have a pretty [00:48] standard Figma file here with a bunch of [00:51] uh references, inspirations, starts from [00:54] like wireframing here, uh all of the [00:56] different components that may be kind of [00:58] part of this design. A bunch of [01:00] different attempts and versions that the [01:03] designer went through before he ended up [01:05] on a design that is presentable that he [01:07] wants to uh show me and the rest of the [01:10] team. Most people coming into here would [01:11] know what to kind of uh do with this. So [01:13] the designer now has to go through a [01:15] handoff process tidying up naming the [01:18] different elements and uh removing this [01:21] maybe putting this in a different uh [01:22] place where it's more presentable and [01:24] not just like a workspace which is what [01:26] Figma is designed to be. That alone [01:28] takes a bunch of time regardless of all [01:30] the additional benefits that I'll share [01:31] with you here. So let me show you what I [01:33] would do. I'll just click here and we go [01:35] to plugins and choose other within the [01:38] the plugin. You can see that I can see [01:39] the different workspaces that uh we're [01:41] operating in. I'm going to use the VTOS [01:43] uh uh playground, but as I change [01:44] between them, you can see all of the [01:46] graphic feedback projects that exists on [01:48] each one of those workspaces. I want to [01:50] choose the first uh element that will be [01:54] um adding into that project. And this is [01:56] the latest version of the first screen [01:58] from this uh fourstep uh sequence. And [02:01] so I'm just going to do this and add new [02:04] project. Perfect. So now we have [02:05] Discovery V2. And if we're going to [02:07] click on the design, we can also see [02:08] this frame four in here. Let's continue. [02:10] And I'm just going to bring in the rest [02:12] of the designs. H this is the other one [02:14] that I want to have. So I'm going to add [02:16] design and move on to here and add [02:20] design and move on. Perfect. So now I [02:23] have all of the designs that I need to [02:25] uh confirm or to get feedback on all [02:27] nested in one place without all of the [02:29] different uh the rest of the clutter. [02:31] Here I'm just going to click on shell [02:32] which is going to open this project for [02:34] me in the brand new uh graphic feedback [02:36] uh system. The first thing I want to do [02:38] is I want to make sure that everything [02:39] is nice and uh uh organized. So this is [02:42] going to be overview and save and move [02:45] on to this one. And this is going to be [02:47] the uh assets [02:52] and uh this one is going to be the [02:54] guidelines [02:58] and this one is going to be the details. [03:02] And as you can see from the sidebar [03:04] here, we have this uh prompted asking us [03:06] to give a description for the people [03:08] that are going to come in. What are they [03:10] going to be looking at? What are what [03:12] are we expecting of them? So uh hey team [03:16] and we can talk about some constraints [03:17] that we have. We can't really add [03:20] anything uh new to this. That's crucial. [03:24] And yeah, so we have some instructions [03:26] here for the rest of the team as they're [03:28] going to be invited to work on this. And [03:31] how do we invite them? We just click on [03:32] shell and we click the copy link here [03:35] and send them over to there. Now, if [03:37] they're audit members, I can just click [03:38] here and choose them and they're going [03:39] to get a notifications. But it's really [03:41] as simple as just copying this link and [03:43] sharing this with others. We're going to [03:45] go through the client experience, the [03:47] stakeholder experience later on in this [03:49] video because that has been rebuilt as [03:51] well, not only for graphics, but for all [03:53] of the collaboration methods. So, it [03:55] there's consistency throughout. And by [03:57] the way, with the rebuild of this [03:58] graphic feedback tool, we now have [04:00] completed the stack of uh collaboration [04:03] tools uh rebuild uh that we started [04:05] about 6 months ago. So very exciting. It [04:08] was a long process to bring this up to [04:09] standard with 2026 expectations of us. [04:12] So it's very cool to see this uh coming [04:14] to life. So now that we've imported the [04:16] project from Figma and uh set it up for [04:18] our review and why why not just do this [04:21] inside Figma? There's four reasons. one, [04:24] you just saw me doing a handoff in [04:26] literally a minute. What usually takes [04:28] uh half an hour of setting things up was [04:30] just done and with better clarity to [04:33] everyone involved. Number two, the [04:35] depth. The depth of functionality and [04:37] control that you gain through the [04:39] popover and the other uh features inside [04:43] is unparalleled to what's going on on [04:45] Figma. You can prioritize, assign to [04:47] different team members, um set the [04:50] status for the different task. We have a [04:51] visual that points out where the request [04:54] is specifically on the page. And of [04:55] course, we're collecting some some [04:57] technical details here. You have due [04:58] dates for the single task. You can add [05:00] tags. You can mark these tasks as [05:02] internal if you're working with external [05:04] stakeholders that should not see the [05:06] work being done. Uh you can even have [05:08] comments being done between team members [05:10] as uh notes in here. Uh plus canned [05:12] responses and of course uh you can [05:15] annotate the whole thing uh directly and [05:18] within seconds on the page itself. And [05:20] now number three, version control. [05:22] There's no way of knowing how many [05:24] revision rounds you've had when you're [05:25] working inside Figma. Changes happen all [05:28] the time. Instead of having a line in [05:30] the sand and saying like, okay, this is [05:32] what I'm presenting. Here is the [05:33] feedback. I made a made changes. I [05:36] pushed a new version into here. H which [05:38] allows everyone to see how many versions [05:40] this design went through. Let's add one [05:42] version. For example, I'm going to go [05:44] back to Figma for this uh first page [05:46] here and I'm going to add this as the [05:49] second version for this design. [05:53] Add version. As you can see, it updated [05:55] the names as well. So, this is overview. [05:58] And now this one has two versions within [06:00] it. As I go back to the project, you can [06:02] see that now I have uh version two and [06:04] version one. I can move between them, [06:06] see how the design progressed, but also [06:08] let my stakeholders, my clients, my team [06:11] members know, look guys, we've been at [06:12] it for like six, seven times already. H [06:15] it's time to move on, right? That was [06:17] never possible before. So for the first [06:19] time, you have the ability to track [06:21] versions. And the fourth one is the [06:23] interface itself designed for feedback. [06:26] Figma is an open space, a canvas that [06:29] allows you to go in all kinds of [06:31] different directions as you explore. A [06:33] canvas by design is exploratory while [06:36] feedback is linear. I'm going from top [06:38] to bottom. I'm reviewing the presented [06:41] work and I'm getting the hell out of [06:43] there. I'm not even talking about the [06:45] fact that you can uh streamline all of [06:46] these communications into your favorite [06:47] project management system. Automate the [06:50] two-way kind of comments uh between here [06:52] and Jira and Asana and all of those kind [06:55] of different elements. So, these are my [06:57] four reasons why Adarim is much better [06:59] than Figma in commenting and [07:01] collaboration. H but I would love to [07:03] learn uh from you uh get the feedback [07:05] and see what else can we do to make sure [07:07] that this workflow fits into yours or [07:10] essentially replaces this uh due to [07:12] being way better in terms of depth and [07:15] way quicker in terms of implementation. [07:17] And now let's go into the guest flow the [07:20] client flow to see what has changed over [07:22] there. So to do this I'm just going to [07:23] click share copy this link open this in [07:25] incognito so I'm not logged in and then [07:27] you will see what uh the other side [07:29] would see. Thank you very much. I'm [07:30] looking forward to getting your feedback [07:32] inside labs.io [07:35] and I'll see you on the next one.  📄 **Full text:** ![[Full Document Contents/Articles/How to Get Client Feedback on Figma|How to Get Client Feedback on Figma, YouTube]] ## Highlights - how do we invite them? We just click on shell and we click the copy link here and send them over to there. Now, if they're audit members, I can just click here and choose them and they're going to get a notifications. But it's really as simple as just copying this link and sharing this with others. We're going to go through the client experience, the stakeholder experience later on in this video because that has been rebuilt as well, not only for graphics, but for all of the collaboration methods. So, it there's consistency throughout. And by the way, with the rebuild of this graphic feedback tool, we now have ([View Highlight](https://read.readwise.io/read/01kk4gbsn9sx9p4w1y3asd3437)) - Tags: 👻 ai highlighted - the sand and saying like, okay, this is what I'm presenting. Here is the feedback. I made a made changes. I pushed a new version into here. H which allows everyone to see how many versions this design went through. Let's add one version. For example, I'm going to go back to Figma for this uh first page here and I'm going to add this as the second version for this design. Add version. As you can see, it updated the names as well. So, this is overview. And now this one has two versions within ([View Highlight](https://read.readwise.io/read/01kk4gbsp414x24gs1s8xbwktt)) - Tags: 👻 ai highlighted