Designers · problem and fix
Conflicting design feedback from stakeholders on Mac: how to sort it in 2026
Conflicting design feedback from stakeholders means two or more people ask for changes that cannot all happen. You fix it by sorting the comments, naming one decision owner and writing down the goal before you redesign anything. This page covers what the problem costs, why it starts, a sorting method you can run this week, and how Figma, Google Docs and Preview on Mac fit into the work.
The short answer
- Conflicting notes usually mean the review had no stated goal.
- Write the goal first, then sort every comment into act now, negotiate or clarify.
- Name one decision owner for each screen. Everyone else gives input.
- Freeze each round so you can show what changed and why.
- Lazur can explain a comment, point at it and draft your reply. It does not make the call.
What contradictory feedback from several reviewers costs you
Time you do not bill
Each round of conflicting notes adds reading, sorting, asking and rework. Most of that time sits outside the design itself. It rarely shows up in a plan or an invoice, so it gets missed. Track it for one project and the pattern is hard to ignore.
Rework on frames you already finished
When two reviewers want opposite fixes, you often rebuild the same frame twice. The first version is thrown out, along with the decision it held. Freezing each round lets you show what was kept and why.
Approvals that stall
A screen with three owners waits for all three. Each wait holds up the next task, including developers and copywriters. The delay often costs more than the design hours behind it.
Trust in the review process
A stakeholder who gets a contradictory answer may stop trusting the review. They may push harder next round or stop engaging with the goal. That habit carries into the next brief. Treat a clear decision as part of the design work.
Why it happens
No stated goal for the review
Reviewers judge what they see when nobody says what the screen must do. NN/g names missing feedback guidelines as the most common reason feedback stays subjective and impossible to act on. Without a goal, one reviewer checks color, another checks copy, and a third checks the brief.
Reviewers looking at different versions
A comment can point at a layout you already replaced. This is easy to miss when the file has several pages or a long comment thread. Check the version and date on each note before you act on it.
Feedback spread across tools
Some notes sit in Figma, others in Slack, email, a PDF or a meeting recap. Nobody sees the full pile. CoLab's survey, of engineering leaders rather than designers, found that much design review feedback is never tracked. A single list is the simplest fix.
No single decision owner
When two leads both claim the final say, each note becomes a bid. The winner is often whoever spoke last. Figma's 2026 survey found that 87% of designers say decision-making power boosts their performance. Ownership is a working condition, not a courtesy.
Vague notes that need follow-up
Words such as clean, fresh, premium or bolder describe a feeling, not a change. Two people can read the same word in opposite ways. NN/g says notes like this need follow-up questions before anyone can act on them.
Stakeholders brought in late
Late reviewers often see the work for the first time and react to all of it. They have no shared vocabulary with the team. NN/g says early involvement aligns everyone on terms, process and deliverables, which reduces vague feedback later.
How to fix it
These work with or without any app.
Set feedback guidelines before the critique
Tell reviewers what you need before they comment. Write one line at the top of the file, such as: we need feedback on goal fit, brand tone, content answers or visual details. NN/g recommends this so feedback lands on the right question. Reviewers then have one question to answer, not a whole screen to judge.
Sort every comment into three piles
After the review, put each comment into act now, negotiate or clarify. Act now is for changes that match the goal and cost little. Negotiate is for changes that clash with the goal or with each other. Clarify is for notes you cannot act on yet. Send clarify items back as one written question each.
Name one decision owner for each screen
Ask the sponsor to name one person who decides on each screen or section. Everyone else is input. Put that name in the file. When two leads disagree, the owner settles it and the reason goes into the thread. This stops the decision from moving to whoever speaks last.
Keep all feedback in one place
Pick the place where the review happens and send people there. For screens, use Figma comments and @ mentions. For copy, use one Google Doc with suggestions turned on. Gather stray notes from email and Slack into one list. Missing notes cause the next round of conflict.
Freeze each round as a record
Export the reviewed state before you change anything. In Preview, choose File > Print, then Save as PDF to flatten the annotations. Keep the editable working file separate. A frozen copy shows what each reviewer saw and ends arguments about what changed.
Reply in writing with what you kept
Send each reviewer a short note. List what you kept, what you dropped and why, and which goal the decision served. Keep it to a few lines. A written close stops the same comment returning next round, and it gives the decision owner a record.
Ask better questions before you redesign
Turn vague notes into specific questions before you change anything. Make it pop becomes which element should a user notice first. Feels off becomes which step feels wrong, the sign-up or the confirmation? NN/g says nondesigners need follow-up questions to make notes actionable. Ask them in writing so the answers stay on record.
Two reviewers look at the same screen. One wants the button bigger. The other wants it gone. Your manager wants the logo moved, and the client wants a new photo. You can answer all four requests, but not in one version without breaking the layout. That is conflicting design feedback from stakeholders in its plainest form.
What conflicting design feedback costs you
Nobody has measured the full bill for designers yet. The closest numbers come from adjacent work. CoLab surveyed full-time engineering managers and executives at large hardware companies about design reviews. Their answers point to 43% of design review feedback never being tracked or addressed. That is a warning sign for design teams, not a measure of your week.
43%
of design review feedback is never tracked or addressed. The sample was engineering managers and executives, not designers.
CoLab Software: 43% of design review feedback is never tracked or addressedOver 1/3
of feedback interventions decreased performance in Kluger and DeNisi's 1996 meta-analysis of 607 effect sizes.
Kluger and DeNisi (1996), Psychological Bulletin, Hebrew University record page91%
of designers say clear goals and expectations help them do their best work, in Figma's 2026 survey of 906 designers.
Figma Blog: State of the Designer 2026$30.27
median hourly pay for graphic designers in May 2025, from the U.S. Bureau of Labor Statistics. Graphic designers only.
Graphic Designers: Occupational Outlook Handbook, U.S. Bureau of Labor StatisticsThe clearest cost is time. Three opposite notes on one frame create work before anything ships. You reopen the file, reread the comments, ask who meant what, then change the same layout twice. The U.S. Bureau of Labor Statistics lists a median pay of $30.27 an hour for graphic designers in May 2025. That covers graphic designers only. It still gives you a rough hourly value for every hour spent untangling notes.
Where the cost shows up
- Rework on frames you already finished, sometimes twice in one week.
- Meetings that restart the argument instead of closing it.
- Unpaid revision rounds if you freelance and the scope never got written down.
- A client who learns that asking loudly wins, so the next brief gets louder.
- Slow approvals, because nobody will sign off on a screen with three owners.
- Your own focus and mood, which are harder to measure but easy to notice on a bad afternoon.
Here is a worked example. Say three reviewers comment on one Figma frame in the same afternoon. The product lead wants a shorter form. The marketing lead wants a bigger sign-up button. The founder wants the form split across two screens. Each request makes sense alone. Together they ask for three different layouts. Accept all three and you rebuild the frame. Pick one without a reason and the other two come back next round. The fix starts before you touch the frame, with the question of which goal wins.
Why reviewers give contradictory feedback
Most conflict starts with missing rules. Nielsen Norman Group says the most common reason feedback becomes subjective and impossible to act on is a lack of feedback guidelines. Without rules, reviewers fill the gap with taste. One person judges the color. Another judges the message. A third asks a question that is really about the brief.
Nondesigners add a second problem. They describe issues in general terms, such as it feels off. NN/g says that kind of note needs follow-up questions before anyone can act on it. Involving stakeholders early helps. They learn the terms, the process and the deliverables before the deadline, so their notes get more specific.
| Cause | What it looks like | First check |
|---|---|---|
| Goals never stated | Notes on color, copy and layout with no shared aim | Ask each reviewer what the screen must do first |
| Different versions | A note refers to a layout you already replaced | Check the file version and date on each comment |
| Feedback spread out | Some notes in Figma, some in Slack, some in email | Gather every note into one list before you reply |
| No decision owner | Two leads each say they have the final say | Ask the sponsor to name one person who decides |
| Vague wording | It feels off, make it pop | Ask which user action should feel different |
Feedback is not automatically helpful. In Kluger and DeNisi's 1996 meta-analysis, feedback improved performance on average. Over one-third of feedback interventions decreased performance, though. The study covers feedback in general, not design reviews, so treat it as a warning. A pile of contradictory notes can make the work worse, not just slower.
A sorting method for conflicting design feedback
NN/g recommends two habits. Set feedback guidelines at the start of each critique. Then sort the feedback into groups afterward. The method below uses both habits and adds a written record. It works the same way for a Figma file, a Slack thread or an email chain.
- Write the review goal in one sentence at the top of the file or doc.
- Copy every comment into one list, with the reviewer's name and the version it refers to.
- Mark each comment as act now, negotiate or clarify.
- Send the clarify group back to their authors with one written question each.
- Take the negotiate group to the decision owner with the two options side by side.
- Reply to every reviewer with what you kept, what you dropped and why.
What counts as act now, negotiate or clarify
Act now covers changes that match the goal and cost little. A typo, a broken link or a wrong label usually fits. Negotiate covers changes that fight the goal or each other. Two reviewers asking for opposite button sizes belong here. Clarify covers notes you cannot act on yet, such as make it more energetic. Ask the reviewer what a user should notice or do first.
Working in Figma: comments, mentions and search
Figma holds most screen notes. Press C to turn on the comment tool, then click the canvas. Figma attaches comments to top-level frames, components and groups. It does not attach them to nested layers. So a note about a button inside a card should name the button in the text. Type @ and a name to mention someone. That person gets an email and, if enabled, an in-app notification.
Figma's comment panel can search by keyword and by person. You can sort by date and mark comments unread. Figma added these in a redesign post dated November 16, 2021, so the details may have moved. The post does not mention resolving comments. Check Figma's current help pages before you rely on resolve or filter steps. Search by reviewer first, then sort by date, so each person's notes stay in order.
Text feedback in Google Docs and Preview
Copy and product text often come back as suggestions. In Google Docs, open Tools > Review suggested edits. Click Accept all or Reject all to handle every change at once. To handle one change, select its comment, then click Accept or Reject. The document owner gets an email about suggestions. Sort first, then accept only the lines the decision owner chose.
Marked-up PDFs usually open in Preview. The Markup toolbar includes Note, Text, Highlight, Shapes and Sketch. Draw needs a Force Touch trackpad. Keep your working copy editable with File > Save or File > Export. To freeze a round, choose File > Print, then Save as PDF. That flattens the annotations, so nobody can edit them later. The frozen copy becomes your record of what was reviewed.
Mistakes people make with stakeholder feedback
- Trying to satisfy every note in one version. You end up with a layout nobody asked for.
- Answering the loudest reviewer first. Volume is not a goal.
- Changing the design before asking a single clarifying question.
- Letting the decision happen in a hallway. Write it into the file or the thread.
- Treating silence as approval. Ask for a yes in writing.
- Pasting a client screen into any AI tool without checking your contract or your employer's data rules.
When the sponsor and the client disagree, stay out of the comment thread. Build a side-by-side with two options. Add one line on the trade-off for each. Send it to the person who signs off, with a date for the decision. If they cannot choose, that tells you the goal is not settled yet. Go back to the goal, not the layout.
Edge cases: when the most senior reviewer is not the right owner
A senior title does not always mean the final say on every area. A brand lead may own the logo, while a product lead owns the sign-up flow. Split the decision by area and write the split into the file. The sponsor still signs off, but each owner has a clear lane. This only works if the sponsor agrees to the split before the next round starts.
Freelancers face one more edge. If a client adds a new note after scope is agreed, treat it as a change request. Reply in writing with the note, what it changes and the extra time it needs. You do not need to sound hostile. You do need to make the change visible, or it becomes free work.
Client files, privacy and your own rules
Some work carries confidentiality duties. Client files, unreleased products and regulated data all need care. Follow your contract and your employer's rules before you share a screen with any AI tool. Lazur listens and looks at the screen only while you hold its shortcut. Audio and screenshots go to AI providers to answer and are not stored. Content is never used to train AI models. Those facts describe the app, not your contract.
Where Lazur helps, and where it does not
Lazur does not sort your feedback, decide what wins or click through Figma for you. It helps with the reading and writing around the sort. Hold ⌥ ⌘ to ask about anything on screen, and Lazur answers out loud. Ask where a comment is, and Lazur draws a circle and a label around it. Ask how to filter comments, and Lazur guides you one click at a time, waiting for each click.
- Decode a vague note by asking what it means on the screen in front of you.
- Find the comment, frame or button a reviewer means, then circle it.
- Walk through Figma's comment panel one step at a time.
- Hold fn and dictate your three piles straight into a doc or Slack message.
- Ask Lazur to draft a calm reply, then read it before you send it.
- Set an Apple Reminders alert for the day the decision is due.
Dictation is not the headline, but it helps when the list is long. Hold fn and speak. Lazur types clean, formatted text at the cursor in any app. Check the words before they reach a client, because dictation can mishear product names.
What to do on your next review round
Pick one step for the next round and do it first. If the goal is missing, write it above the first frame. If the goal is there, go straight to the sort. If comments seem to have vanished in Figma, check the fix guide before you assume they were deleted: Figma comments not showing on Mac. To roll back a file, see how to restore a previous version in Figma on Mac. For voice help with the sort, see Lazur for designers and plans and pricing.
Faster with Lazur
Where Lazur helps with contradictory feedback from several reviewers
Hold ⌥ ⌘ and say what you want. Lazur sees your Figma window. Lazur draws a circle and a label around the button or menu you need.
- 1
Hold ⌥⌘ and talk
- 2
Lazur draws a circle and a label around the button or menu you need.
- 3
You stay in Figma. Nothing to copy into a chat window.
More things to say in Figma
- “Hold ⌥ ⌘ and ask what this comment means on screen”
- “Ask where the product lead's comment is”
- “Ask how to filter Figma comments by person”
- “Hold fn and dictate your three piles”
- “Ask Lazur to draft a calm reply to the client”
- “Ask Lazur to remind you when the decision is due”
Free for 3 days, then $18/month. Download for Mac
You say“Hold Option and Command, then ask which comment came from the product lead.”
Lazur · points at itIf the name shows on screen, Lazur circles that comment and says what it asks for, out loud.
What designers say to Lazur for this
Each one is a single hold of ⌥ ⌘.
“Hold ⌥ ⌘ and ask what this comment means on screen”
Lazur sees the screen you are looking at, then answers out loud. Use it to decode vague notes before you reply.
Explains what's on screen
“Ask where the product lead's comment is”
Lazur draws a circle and a label around the comment or control on your screen.
Points at it
“Ask how to filter Figma comments by person”
Lazur walks you through it one click at a time and waits for each click.
Walks you through it
“Hold fn and dictate your three piles”
Lazur types clean, formatted text at the cursor in any app, so your sorted list goes straight into a doc.
Types what you say
“Ask Lazur to draft a calm reply to the client”
Lazur drafts the text. You read it, edit it and send it yourself.
Drafts it
“Ask Lazur to remind you when the decision is due”
Lazur sets the reminder in Apple Reminders by voice, so the deadline sits on your list.
Handles the small stuff
A plan you can start this week
- Day 1
Write the goal
Open the file and write the review goal in one sentence at the top. Ask the sponsor to confirm it in writing. If they cannot agree on the goal, stop and settle that before any design change.
- Day 2
Gather every comment
Collect Figma comments, Slack messages, email notes and PDF markups into one list. Record the reviewer and the version each note refers to. Use Figma search by person and keyword to speed this up.
- Day 3
Sort into three piles
Mark each item act now, negotiate or clarify. Send the clarify items to their authors with one written question each. Expect some answers to move items to a different pile.
- Day 4
Take conflicts to one owner
Make a side-by-side for every negotiate item. Put two options on the page with one trade-off line each. Send the pack to the decision owner with a due date, or book one short decision call.
- Day 5
Make the change and freeze it
Apply the chosen changes in the working file. Export the reviewed version to PDF with File > Print, then Save as PDF in Preview. Keep the editable file separate.
- Day 6
Reply to each reviewer
Send each reviewer a short note that lists what you kept, what you dropped and why. Thank them for the note, even when the answer was no.
Questions people ask
What is conflicting design feedback from stakeholders?
It is feedback from two or more reviewers that asks for changes that cannot all happen. One person wants a bigger button and another wants it removed. Sorting the comments, naming one decision owner and writing down the goal usually settles it.
How do I answer contradictory feedback without upsetting the client?
Reply in writing with the options and one line on the trade-off for each. Say which goal each option serves. Ask the sponsor to pick by a set date. Avoid debating taste inside the comment thread.
Should I always do what the most senior person says?
Usually the senior person has the final call. Check the goal first, though. Another reviewer may own one area of the work. When that is true, split the decision by area and write the split into the file.
Can I use Figma comments to track which feedback I acted on?
Figma comments help with location and search. The comment guide I checked does not describe tags or categories. Keep a short decision list in a doc or tracker. Check Figma's current help pages for resolve and filter steps before you rely on them.
How do I freeze a review round in Preview on Mac?
Open the marked-up PDF and choose File > Print, then Save as PDF. Print to PDF flattens the annotations, so they can no longer be edited. Keep your editable copy in a separate file.
Is it safe to show a client screen to Lazur?
Lazur listens and looks at the screen only while you hold the shortcut. Audio and screenshots go to AI providers to answer and are not stored. Still, follow your contract and your employer's rules before you share client files with any AI tool.
Does Lazur settle conflicting feedback for me?
No. Lazur can explain what is on screen, point at a comment, guide you through a menu and draft a reply. You decide which feedback wins. Lazur does not click buttons or operate Figma for you.
How do I limit revision rounds without losing the client?
Write the number of rounds into the brief or contract before work starts. Label extra rounds as change requests. Share a short list of what each round covers, so reviewers do not reopen settled decisions.
Sources
- The Effects of Feedback Interventions on Performance: A Historical Review, a Meta-Analysis, and a Preliminary Feedback Intervention Theory (record page) · Hebrew University of Jerusalem (CRIS) · checked 2026-11-08
- 43% of design review feedback is never tracked or addressed · CoLab Software · checked 2026-11-08
- Derailed Design Critiques: Tactics for Getting Back on Track · Nielsen Norman Group · checked 2026-11-08
- Add comments to files · Figma Help Center · checked 2026-11-08
- Stay in the flow with redesigned comments · Figma · checked 2026-11-08
- State of the Designer 2026: Designers Are Leaning Into the Messy Middle · Figma · checked 2026-11-08
- Suggest edits in Google Docs · Google Docs Editors Help · checked 2026-11-08
- Annotate a PDF in Preview on Mac · Apple Support · checked 2026-11-08
- Graphic Designers: Occupational Outlook Handbook · U.S. Bureau of Labor Statistics · checked 2026-11-08
Fix contradictory feedback from several reviewers with Lazur, free for 3 days
Hold a key and ask. Lazur sees your screen, points at the button and talks you through it, in any Mac app. No credit card.