Design Critique Methods for Feedback

🤦🏻 “How We Run Design Critiques at Figma” (https://lnkd.in/eERQmRnY), an honest case study by Noah Levin with helpful techniques and templates to run more effective design critiques ↓ 🚫 Most critiques are an avalanche of unstructured opinions. ✅ Good critiques are inspiring, and give you a plan of action. ✅ Critiques work best with 2–6 people in the room. ✅ Explain the problem before showing any work. ✅ Reiterate previous findings, decisions and research. ✅ Explain how far you are: 30%, 60% or 90% done. ✅ Explain what kind of feedback you are looking for. ✅ No Keynote/Powerpoint: Figma link + Observation mode. ✅ Assign a note-taker to capture key points (Google Doc). ✅ Show what you want to show: feedback is shaped by that. 🚀 Critique formats: 🎡 Round-the-room: everyone voices their feedback (2min / person). 🍿 Popcorn: freeform comments for flowing conversation. 🥁 Jams: for early explorations with brainstorms, group sketching. 🫱🏻🫲🏾 Pair design: for deep collaboration on a problem (small groups). 🤫 Silent critiques: for a large volume of written, structured feedback. 📋 Paper print-out: for complex flows and reviewing more at once. 📣 FYI critiques: for sharing context and invite feedback later. Design critiques are about applying critical thinking. It’s about how well a current iteration of design does what it’s trying to do. However, designers alone often don’t have the full picture. Don’t necessarily reserve critiques to design teams only: invite developers and stakeholders and PMs for early feedback. Don’t ask what people think — ask how well the design tackles a specific problem. And probably the most important thing is to enable a flowing conversations. Invite everyone to ask, to doubt, to scrutinize, but stay on point and gather structured feedback: that’s when good critiques emerge. Useful resources: Practical Design Critique Guide, by Darrin Henein https://lnkd.in/ey_cGKuc Mastering Design Critiques, by Jonny Czar https://lnkd.in/e_BYwNwf Anti-Behavior in Design Critiques, and How To Handle Them, by Ben Crothers https://lnkd.in/e4UrpsPs --- ⛵ Figma and Miro Templates Design Critique Meetings Guide (Figma), by Overflow https://lnkd.in/dE85MUAK Design Critique Template (Figma), by Janus Tiu https://lnkd.in/dCYp2MSY Design Critique Meeting (Figma), by Rodrigo Javier Peña https://lnkd.in/dP_8pCug Design Critique Playground Template (Miro), by Miroslava Jovicic https://lnkd.in/eryJShRd #ux #design

I once dreaded design reviews. Now, I use them as a tool. All of us go through this shift. Negative feedback, constructive or not, made me defensive. It felt like an insult. I took it personally and often went through the five stages of grief: 1. Denial "They must have misunderstood my design; there's no way it's actually that bad." 2. Anger "How dare they criticize my work like that? They don't understand my vision at all!" 3. Bargaining "Maybe if I just tweak this one part, they'll see how great the overall concept is." 4. Depression "I'm clearly not cut out for this; maybe I should just give up." 5. Acceptance "Okay, okay, I will make the changes; maybe it will make the design better." Knowing how to receive and act on feedback is part of a designer's job and is also what differentiates good and bad designers. It took me a while to understand that. Here are some tips that can help you: 1. Be open-minded. Embrace new perspectives, even challenging ones. Critique aims to improve your design, not undermine your skills. 2. Ask clarifying questions if unsure. Request specific examples or detail explanations. 3. Your work isn't you. Feeling attached to designs is natural. Remember, critique isn't personal. View your design objectively. 4. Resist arguing. Listen fully and thank them for their input. If you disagree, reflect and follow up later. After you get the feedback, don't address it right away. Give yourself time to reflect on what was discussed. As I like to tell all my mentees: "Don't implement the feedback blindly. Push it through your own point of view. Use it as a guide, not as a requirement. You are the designer."

As you start working with more and more stakeholders, there is a natural tendency to try accomodate every bit of feedback received. This is something we refer to as "Design by committee". It's also a surefire way to build subpar experiences by combining multiple irrelevant ideas into a single solution, rather than thinking deeply about the problem being solved and what the right solution is. Here is what the situation usually looks like: - Stakeholder A: "This competitor app is doing it that way." - Stakeholder B: "I showed this to my partner, and they didn't like it." - Stakeholder C: "Let's rethink this as it won't be clear to users." Some of the feedback above is valid, whereas other pieces are purely opinion-based, with no particular evidence or logical argument. It's your role as a designer to cut through the noise, eliminate pure opinion, debate where needed, and ultimately arrive at a solution that addresses the original problem, both for the business and the user. I have a simple decision tree I've used throughout my career as a thought process when dealing with feedback from multiple stakeholders. It boils down to four questions: 🟢 Is it clear and specific? ↳ If not, clarify it. 🟢 Is it supported by evidence or logic? ↳ If not, debate it. 🟢 Will it help us meet the objective? ↳ If not, kindly disregard. 🟢 Is it feasible? ↳ If not, save it as a fast-follow or future idea. If all the checks above are met, it's worth actioning the feedback. It still doesn't mean you have to act on every single suggestion, but it does mean you can quickly narrow down to a much smaller pool of items to consider. -- If you found this useful, consider reposting ♻️ What else have you found helpful in dealing with feedback from multiple stakeholders? Let me know in the comments 👇 PS: I'm working on a larger content piece on managing and working with stakeholders, dropping in the next few weeks. Find the link to the newsletter in the first comment.

A mentor once gave feedback that kept me up all night. It wasn’t cruel. It wasn’t even wrong. But it hit something deep, and I couldn’t stop replaying it. That’s the thing about harsh criticism: It can hijack your mind even when it’s helpful. Here’s how I’ve learned to process it without spiraling: 1️⃣ Pause before reacting. Let your thinking brain catch up. 2️⃣ Separate tone from truth. Delivery ≠ value. 3️⃣ Drop the identity reflex. It’s about the action, not your worth. 4️⃣ Look for patterns. One comment = opinion. Several = signal. 5️⃣ Use it as a mirror, not a verdict. Reflect before you react. 6️⃣ Know who matters. Not all feedback deserves your energy. 7️⃣ Break the loop. Walk. Breathe. Write. Ground yourself. You don’t need to dissociate from criticism. You need to integrate it skillfully. ♻️ Repost if you’ve ever replayed a comment longer than it deserved. 🔔 Follow Matt Schnuck for insights on EQ, boundaries, and clear communication.

I stopped treating feedback like criticism and started treating it like free consulting. Because feedback isn’t about your worth. It’s about your blind spots. Most people waste feedback. They get defensive. They explain themselves. They ignore it. And then they wonder why nothing changes. ✅ How to treat feedback like free consulting (the real playbook): 1️⃣ Stop waiting for annual reviews. If you only hear feedback once a year, you’re already behind. Create your own feedback loop monthly, even weekly. 2️⃣ Ask sharper questions. Don’t ask “How am I doing?” Ask “What’s one thing I could do that would change the way you see me as a leader?” 3️⃣ Separate emotion from data. Feedback stings. That’s normal. But behind the sting is data. Extract it, use it, move forward. 4️⃣ Interrogate the source. Not all feedback is equal. Filter advice through one lens: Has this person achieved what I want to achieve? 5️⃣ Demand specifics. “Be more strategic” is useless. Push for examples. What did you say? What should you have said instead? Feedback without examples is noise. 6️⃣ Look for patterns, not one-offs. One person’s opinion is bias. Three people saying the same thing is truth. Patterns reveal where you need to act. 7️⃣ Stop explaining. The moment you start justifying, you close the door to honesty. Take it in, say thank you, move on. 8️⃣ Test it in real time. Don’t just collect notes. Try the new behaviour in your next meeting, pitch, or email. Feedback without testing is just theory. 9️⃣ Keep receipts. Document feedback and your response to it. When it’s time for promotion, you show the growth curve — not just claim it. 🔟 Flip the mirror. Give feedback as much as you take it. The best way to sharpen your own lens is to hold one up for someone else. We call it “feedback.” The unprepared call it “criticism.” The ambitious call it “an edge.” What’s the most valuable piece of feedback you ever received?

𝐒𝐭𝐚𝐤𝐞𝐡𝐨𝐥𝐝𝐞𝐫 𝐄𝐧𝐠𝐚𝐠𝐞𝐦𝐞𝐧𝐭: 𝐌𝐞𝐞𝐭 𝐓𝐡𝐞𝐦 𝐖𝐡𝐞𝐫𝐞 𝐓𝐡𝐞𝐲 𝐀𝐫𝐞 Enterprise Architecture abhors a vacuum—it thrives on stakeholder engagement. Often, architects jump into collaboration without first assessing one critical factor: • 𝐖𝐡𝐚𝐭 𝐝𝐨 𝐬𝐭𝐚𝐤𝐞𝐡𝐨𝐥𝐝𝐞𝐫𝐬 𝐤𝐧𝐨𝐰, 𝐚𝐧𝐝 𝐛𝐞𝐥𝐢𝐞𝐯𝐞, 𝐚𝐛𝐨𝐮𝐭 𝐄𝐀? Before strategy, frameworks, or roadmaps, 𝐮𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝 𝐭𝐡𝐞𝐢𝐫 𝐚𝐰𝐚𝐫𝐞𝐧𝐞𝐬𝐬, 𝐩𝐞𝐫𝐜𝐞𝐩𝐭𝐢𝐨𝐧𝐬 and 𝐞𝐱𝐩𝐞𝐜𝐭𝐚𝐭𝐢𝐨𝐧𝐬. This will shape how you approach, gain buy-in, and drive outcomes. Here are 𝐭𝐡𝐫𝐞𝐞 𝐞𝐬𝐬𝐞𝐧𝐭𝐢𝐚𝐥 𝐦𝐨𝐯𝐞𝐬 for aligning EA with stakeholders: 𝟏 | 𝐆𝐚𝐮𝐠𝐞 𝐄𝐀 𝐀𝐰𝐚𝐫𝐞𝐧𝐞𝐬𝐬 𝐁𝐞𝐟𝐨𝐫𝐞 𝐄𝐧𝐠𝐚𝐠𝐢𝐧𝐠 EA means different things to people, how can you align? Approach: * 𝐀𝐬𝐬𝐞𝐬𝐬 𝐞𝐱𝐢𝐬𝐭𝐢𝐧𝐠 𝐤𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞. What do leaders think EA does? What experiences shape their view? * 𝐏𝐨𝐬𝐢𝐭𝐢𝐨𝐧 𝐄𝐀 𝐢𝐧 𝐭𝐡𝐞𝐢𝐫 𝐥𝐚𝐧𝐠𝐮𝐚𝐠𝐞. If a product saw EA as 'overhead,’ shift the conversation to ‘rapid decision-making.’ * 𝐓𝐚𝐢𝐥𝐨𝐫 𝐞𝐧𝐠𝐚𝐠𝐞𝐦𝐞𝐧𝐭 𝐛𝐲 𝐚𝐮𝐝𝐢𝐞𝐧𝐜𝐞. Finance, operations, and IT leaders have different concerns. Meet them on their terms. 👉 𝐎𝐮𝐭𝐜𝐨𝐦𝐞: When you shape EA’s role based on their reality, it becomes relevant, not theoretical. 𝟐 | 𝐀𝐥𝐢𝐠𝐧 𝐄𝐀 𝐭𝐨 𝐒𝐭𝐚𝐤𝐞𝐡𝐨𝐥𝐝𝐞𝐫 𝐏𝐫𝐢𝐨𝐫𝐢𝐭𝐢𝐞𝐬 EA isn’t all architecture, it’s solving business problems. Approach: * 𝐒𝐭𝐚𝐫𝐭 𝐰𝐢𝐭𝐡 𝐊𝐏𝐈𝐬. Growth? Efficiency? Risk? Align EA contributions to what leadership interests. * 𝐂𝐨𝐧𝐧𝐞𝐜𝐭 𝐭𝐞𝐜𝐡𝐧𝐨𝐥𝐨𝐠𝐲 𝐭𝐨 𝐢𝐦𝐩𝐚𝐜𝐭. Show architecture driving go-to-market, savings, or agility—over compliance. * 𝐀𝐧𝐭𝐢𝐜𝐢𝐩𝐚𝐭𝐞/𝐫𝐞𝐦𝐨𝐯𝐞 𝐫𝐨𝐚𝐝𝐛𝐥𝐨𝐜𝐤𝐬. If EA was a bottleneck, demonstrate accelerated decision-making instead. 👉 𝐎𝐮𝐭𝐜𝐨𝐦𝐞: EA is a strategic enabler, not afterthought. 𝟑 | 𝐁𝐮𝐢𝐥𝐝 𝐄𝐀 𝐢𝐧𝐭𝐨 𝐭𝐡𝐞 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐂𝐨𝐧𝐯𝐞𝐫𝐬𝐚𝐭𝐢𝐨𝐧 EA works best in collaboration, not isolation. Approach: * 𝐄𝐦𝐛𝐞𝐝 𝐚𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐬 𝐢𝐧𝐭𝐨 𝐛𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐝𝐢𝐬𝐜𝐮𝐬𝐬𝐢𝐨𝐧𝐬. Decision-making improves when EA is a proactive presence. * 𝐒𝐡𝐢𝐟𝐭 𝐟𝐫𝐨𝐦 ‘𝐩𝐫𝐞𝐬𝐞𝐧𝐭𝐢𝐧𝐠 𝐄𝐀’ 𝐭𝐨 ‘𝐜𝐨-𝐜𝐫𝐞𝐚𝐭𝐢𝐧𝐠 𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐬.’ Stakeholders engage when architecture is a tool for their success. * 𝐂𝐨𝐧𝐭𝐢𝐧𝐮𝐨𝐮𝐬 𝐞𝐧𝐠𝐚𝐠𝐞𝐦𝐞𝐧𝐭, 𝐧𝐨𝐭 𝐨𝐧𝐞-𝐨𝐟𝐟. EA isn’t a pitch—it’s a dialog evolving with business. 👉 𝐎𝐮𝐭𝐜𝐨𝐦𝐞: EA shaping decisions early rather than reacting later. 𝐓𝐚𝐤𝐞𝐚𝐰𝐚𝐲 𝐒𝐭𝐚𝐤𝐞𝐡𝐨𝐥𝐝𝐞𝐫 𝐞𝐧𝐠𝐚𝐠𝐞𝐦𝐞𝐧𝐭 𝐬𝐭𝐚𝐫𝐭𝐬 𝐰𝐢𝐭𝐡 𝐮𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝𝐢𝐧𝐠. Before pushing frameworks or models, assess 𝐰𝐡𝐚𝐭 𝐄𝐀 𝐦𝐞𝐚𝐧𝐬 𝐭𝐨𝐝𝐚𝐲—and how to reshape that narrative to unlock its full potential. How do align EA stakeholders? Let’s discuss.👇 --- ➕ 𝐅𝐨𝐥𝐥𝐨𝐰 Kevin Donovan 🔔    👍 Like | ♻️ Repost | 💬 Comment    🚀 𝐉𝐨𝐢𝐧 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐬’ 𝐇𝐮𝐛 👉 https://lnkd.in/dgmQqfu2

What do you do when someone on your team is brave enough to criticise you? Me? I promote them as soon as possible. Why? Because in high-performing companies, innovation thrives when teams feel empowered to challenge ideas respectfully. As a leader, fostering a culture of constructive dissent can unlock your team’s full potential and fuel spectacular business growth. Here are 5 techniques I use to build openness and encourage dialogue: 1. Encourage continuous feedback Don’t wait for annual reviews or formal discussions. Make candid feedback a regular part of daily operations — through check-ins, town halls, or anonymous surveys. The more often feedback is shared, the less intimidating it becomes. 2. Model respectful dissent How do you react when your ideas are challenged? Leaders should actively invite differing viewpoints and listen with an open mind. When leaders encourage respectful dissent, it signals to everyone that diverse perspectives are truly valued. 3. Reward honest opinions Recognise those who respectfully challenge the status quo. This reinforces the idea that fresh thinking is an asset, not a liability. (Fun fact: The US State Department has an annual Constructive Dissent Award, given to those who courageously stand by their principles.) 4. Be transparent in decision-making After making a decision, explain the reasoning behind it. Even if someone’s idea isn’t chosen, knowing their input was genuinely considered strengthens future buy-in and trust. 5. Align after discussion Once a decision is made, the team must unite behind it to make it work. Remind everyone that while debate is healthy during the process, whole-hearted execution is key to success. You really can criticise your way to success. A culture of constructive dissent leads to smarter decisions and a more productive team. The key? Making sure every voice is heard and valued. Do you agree? Promise not to fire you if you don't!

Design reviews aren’t about proving your design is “right.” They’re about sparking the right conversations, surfacing blind spots, and aligning your work with both the business and the user. But here’s the thing: The quality of the questions you ask directly shapes the quality of the feedback you’ll receive. When you ask questions that seek approval, you invite surface-level reactions: “I don’t like that color.” “Can you move this button?” “It doesn’t feel right.” When you ask questions that seek perspective, you unlock insights that go much deeper: “Does this flow align with the goals we set?” “Which part of this journey feels riskiest for launch?” “What business constraints should we keep in mind?” That’s the shift: ❌ Approval → opinions ✅ Perspective → alignment, priorities, and actionable feedback Strong designers don’t just show screens. They guide the conversation by asking thoughtful, open questions that: Clarify the “why” behind feedback Dig into what truly matters for success Encourage stakeholders to connect feedback back to goals That’s how design reviews stop feeling like a defensive battle and start becoming a collaboration that moves everyone forward. Because when you stop asking “Do you like it?” and start asking “How does this support our goals?”you elevate both the conversation and the design.

How to Handle Feedback? Feedback—whether constructive or critical—is a gift that helps us grow. But let’s admit it, receiving feedback can sometimes feel overwhelming or even discouraging. How we respond in these moments defines our growth mindset and professional maturity. Here’s my approach: 1️⃣ Pause and Reflect: Instead of reacting impulsively, I take a moment to process the feedback. This helps me separate emotions from facts. 2️⃣ Seek Clarity: If the feedback isn’t clear, I ask specific questions to understand the perspective better. Clarity ensures I address the root issue. 3️⃣ Embrace It as an Opportunity: Even harsh feedback often carries a lesson. I focus on what can be learned rather than dwelling on the negative delivery (if any). 4️⃣ Acknowledge and Plan: Once I’ve understood the feedback, I acknowledge its validity and share a plan for improvement. This demonstrates accountability and a proactive approach. 5️⃣ Follow Up: After implementing changes, I reconnect with the feedback provider to ensure the issue is resolved and build trust. Feedback isn’t the end; it’s a step towards excellence. By accepting it with humility and focusing on solutions, we not only enhance our skills but also strengthen relationships with colleagues and stakeholders. 💡 How do you handle feedback? Comment #FeedbackMatters #GrowthMindset #ProfessionalDevelopment #Leadership #storiesatworkplace

A few years back, giving feedback, especially when it wasn’t all positive was tough for me (seriously). I used to worry about how my words would be received and whether I’d create resentment or anxiety. But with time I’ve learned that feedback, when approached thoughtfully, can be a powerful catalyst for growth. Here’s a simple 3-step approach that has transformed my feedback conversations (they are game changers): 📌 I start by asking team members how they think they did. This simple question helps them feel more in control and allows them to pinpoint areas for improvement. Instead of launching into my thoughts, I might ask, “How do you think your presentation went?” This sets a collaborative tone right from the start. 📌 Acknowledge what they did well. I like to start with the positives to remind my team that they have strengths, even if there are areas to improve. For example, I might say, “You really communicated the vision clearly and engaged the audience with your energy.” This kind of recognition helps ease any tension and sets a positive tone. 📌 Finally, I share my insights on how they can improve moving forward. This is about guiding them to success rather than just pointing out mistakes. For example, I might suggest, “Next time, consider preparing a bit more to ease any nerves.” This keeps the focus on solutions and growth. Feedback conversations don’t have to be intimidating. When we create a safe space for open dialogue, we empower our team members to grow and improve. Remember, it’s our responsibility to create an environment where feedback is not only welcomed but embraced. Let’s strive to make our conversations meaningful and motivating. #Teamculture #Leadership #Feedback