<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Carolann Merchant on Medium]]></title>
        <description><![CDATA[Stories by Carolann Merchant on Medium]]></description>
        <link>https://medium.com/@carolanncan?source=rss-350754aef755------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2BnHnmTrT9qLCQs5aa3ojQ.jpeg</url>
            <title>Stories by Carolann Merchant on Medium</title>
            <link>https://medium.com/@carolanncan?source=rss-350754aef755------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:23:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@carolanncan/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Crit Playbook]]></title>
            <link>https://medium.com/bleacher-report-design/the-crit-playbook-e9fbb957bc07?source=rss-350754aef755------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9fbb957bc07</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[critique]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Carolann Merchant]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 17:40:53 GMT</pubDate>
            <atom:updated>2023-07-17T15:53:34.326Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9S2vG81KQCPIoNzWIypYUA.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h4>A Four Part Series</h4><p>Welcome to the Crit Playbook! Feedback on your work is important for every designer. We’ve written about some of the ways our team makes our Design Critiques the most effective. Each part of this series offers guidance and best practices on the different aspects of a design critique meeting.</p><ul><li><a href="https://medium.com/bleacher-report-design/part-1-introduction-2282140ddf0b">Part 1: Introduction</a></li><li><a href="https://medium.com/bleacher-report-design/part-2-presenting-your-work-42527be7cfb4">Part 2: Presenting Your Work</a></li><li><a href="https://medium.com/bleacher-report-design/part-3-feedback-c7eac60d878d">Part 3: Feedback</a></li><li><a href="https://medium.com/bleacher-report-design/part-4-the-role-of-design-critique-in-decision-making-33170d9599a1">Part 4: The Role of Design Critique In Decision-making</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9fbb957bc07" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/the-crit-playbook-e9fbb957bc07">The Crit Playbook</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 4: The Role of Design Critique In Decision-making]]></title>
            <link>https://medium.com/bleacher-report-design/part-4-the-role-of-design-critique-in-decision-making-33170d9599a1?source=rss-350754aef755------2</link>
            <guid isPermaLink="false">https://medium.com/p/33170d9599a1</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[critique]]></category>
            <dc:creator><![CDATA[Carolann Merchant]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 17:37:10 GMT</pubDate>
            <atom:updated>2019-09-24T17:37:10.804Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sUxsKPccU3HW8DRanFdf_g.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h4>The Crit Playbook</h4><p>The final part of this series will talk about the attitude and approach to take toward design critique within the larger context of your team and the impact it has on your day-to-day decision making.</p><h3>Attitudes Toward Critique</h3><p>As a designer, your team is trusting and relying on you to be a decision-maker for your project. You should not lean on Crit as a place where you get direction. Your team can’t make your decisions for you!</p><p>Conversely, a team should not expect the feedback from Crit to dictate the final solution. Even if the director of product is in attendance and providing input, in Crit everything is take-it-or-leave it feedback.</p><h3>Crit Is Not An Approval Process</h3><p>Crit shouldn’t feel like a committee of art directors reviewing and approving work. It’s meant to provide healthy discussion and outside points of view. Crit should not be where decisions are made, debated, or approved. Crit is a place for open-minded discussion.</p><p>Following a style guide or brand standards is likely a constraint of your work. Some teams may need an approval process to make sure designs comply with pre-set guidelines. These evaluations and approvals should happen in a dedicated meeting. The outcome of an approval meeting is similar to a pass or fail test while the outcome of Critique is take it or leave it feedback.</p><h3>Crit Is Not For Strategy Pivots</h3><p>The process of setting a strategy for an area of work involves many layers of decisions, multiple people, meetings, and discussions. Designers should be actively involved in helping shape the strategy for their area of work.</p><p>In Crit, it can be helpful to include details on how the work you’re presenting connects to the roadmap for your team or broader product vision. But the strategy has likely been through rounds of feedback before you began producing work. This makes it difficult to discuss changes in strategy without the right stakeholders in the room. But it’s possible for input on strategy to come up in Crit that needs consideration. In that situation, you could choose to:</p><ul><li>Take down a note about the feedback and ask to follow up in a separate meeting. This ensures the feedback is heard, provides a dedicated time for discussion with the right set of people, and keeps the rest of Crit on track.</li><li>Timebox the conversation during Crit. Offer to take the next 5–10 minutes to discuss the feedback so the entire group is included in the conversation. Remember, you still need to use the rest of your time to get the feedback you specified. If the discussion goes beyond the timebox, the conversation probably merits a separate meeting.</li></ul><h3>Crit Is Not Show and Tell</h3><p>Part of your responsibility as a designer is to keep your design team aware of your progress, and it’s tempting to use Crit as a way to socialize work. The whole design team is conveniently in the room, you can show your progress and let everyone know that you have<em> in fact</em> been busy working. It can feel easier than documenting your progress. However, this isn’t the best use of everyone’s time.</p><p>The purpose of Crit is to receive input. If you aren’t looking for input and just want to share, it’s best to publish your work to message boards or share your progress during meetings meant for status updates.</p><h3>Keep Your PM In the Loop</h3><p>It doesn’t happen often, but it’s possible that in a <em>single </em>Crit, the team has helped you realize you’ve been going about your solution all wrong. Maybe you’ve done too much! Or too little… or drifted from the original problem. You might be thinking, “My PM is gonna freak out if we change direction.” or “I’ve invested so much time in my current solution… I’ll slow down the team if I pivot now.”</p><p>PMs are great thought partners! If you feel you need to explore a new direction, discuss the points raised in Crit with your PM. Help them understand why you think making a significant change is important to the user experience and the goals your team has set. Ask for their input, and their help in figuring out how to execute on the ideal solution while managing the team’s timeline. Even if they’re not in Crit, they still need to be part of the conversation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35jzQwqwCn0uu34RLLMCGw.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h3>Get Feedback Outside of Crit</h3><p>Most teams have a weekly Crit. Waiting until the next meeting to get feedback can slow down progress on your work. It’s helpful to have tools to get input throughout your process.</p><h4>Asynchronous Feedback</h4><p>Exploring button styles? Typography? Or specific visual design choices? Decisions that are more tactical or small in scope don’t require a meeting. Tools that enable asynchronous design feedback can help you get input from your team as they have time throughout their day.</p><h4>In-person Meetings</h4><p>Maybe you could use a second pair of eyes on a problem that’s a bit larger in scope or hard to explain if you’re not doing it in person. Set up one-on-one time with a teammate or ask if you can stop by their desk for their input. Ask another designer, a PM, an engineer, or anyone who you think might have a helpful point of view!</p><h3>In Conclusion</h3><p>Overall, design critique is meant to be a place where designers can come together and offer helpful input on each other’s work. Maybe more than other roles and professions, designers recognize that good design can’t be made in solitude. You’ll never get it exactly right on your own. The best work comes from creativity, open-mindedness, and scrutiny.</p><h3>See Full Series: The Crit Playbook</h3><p><strong>Want to be part of our product design team? We’re hiring! Reach out to learn more. carolann.merchant@bleacherreport.com</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33170d9599a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/part-4-the-role-of-design-critique-in-decision-making-33170d9599a1">Part 4: The Role of Design Critique In Decision-making</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 3: Feedback]]></title>
            <link>https://medium.com/bleacher-report-design/part-3-feedback-c7eac60d878d?source=rss-350754aef755------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7eac60d878d</guid>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[critique]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Carolann Merchant]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 17:36:49 GMT</pubDate>
            <atom:updated>2019-09-24T17:39:29.587Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qzuN-mFRk1wT70ICp0fuAQ.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h4>The Crit Playbook</h4><p>So far in our series we’ve focused on being prepared, individually, for Crit. Part 3 will dive into the conversations during the meeting and offer guidance on how to make sure we’re supporting each other while also being honest and direct with our feedback.</p><h3>How To Approach Feedback</h3><p>During design critique, all input should be taken with a grain of salt. Feedback in Crit should never be considered mandatory changes. As the designer, you’re the owner of the decisions you make. Critiques on the work aren’t a reflection on you or your abilities. It’s only about the current status of the design.</p><h3>When You Are The One Receiving Feedback</h3><h4>Assume Good Intentions</h4><p>Some people struggle to phrase feedback well while others can be great at it. Assume that your teammates are doing their best to be honest and helpful, regardless of how the wording comes out. If something doesn’t feel quite right, use your best judgement in the meeting and lean on your manager to help you and your teammates to make sure everyone feels respected.</p><h4>Appreciate The Feedback</h4><p>Non-verbal communication is the most effective way to let someone know you’re listening and encourage them to express their thoughts. When your teammates are talking, make eye contact! Show appreciation by saying things like, “I hadn’t thought of that thank you!” or “I hadn’t noticed until you said it, I’ll think about that.”</p><p>If you get feedback you don’t agree with, ask clarifying questions to make sure you understand the intent behind the feedback. Be careful not to debate their suggestions or their point of view. Take note of all the input and keep the conversation moving. What you do with their feedback after the meeting is up to you.</p><h4>Make A Decision</h4><p>Think about how you are going to use (or not use) the feedback to move your project forward. Making a decision can be the most difficult part of being a designer. No matter how experienced you are, you never know for sure how people will interact with a design until you get something out there. The key to getting better as a designer is seeing how people respond to a design and learning from your own mistakes. It’s better to be wrong and learn how to improve the design, than to be indecisive and delay progress.</p><blockquote>I’ve missed more than 9,000 shots in my career. I’ve lost almost 300 games. 26 times I’ve been trusted to take the game winning shot and missed. I’ve failed over and over and over again in my life. And that is why I succeed.</blockquote><blockquote>- Michael Jordan</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ifdgYbWk6K-EVli3noQDAw.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h3>When You Are The One Giving Feedback</h3><p>As much as we want to be direct and focus on the work, Critique is still a vulnerable place. Always focus feedback on the work, and not on the designer. Remember that people receive communication differently. A little warmth and patience goes a long way.</p><h4>Positive Feedback</h4><p>As designers, we have to be self-critical of our choices in order to create good work. Crit isn’t just about pointing out what needs improvement. It’s just as important to know what’s working. Even if the presenter doesn’t directly ask for it, calling out what is good or just <em>cool</em> about a design can go a long way toward helping each other create good work.</p><h4>Show Confidence In Each Other</h4><p>When suggesting a new idea or approach, you can show confidence in the presenter by starting with a phrase like, “You may have already thought of this…” This shows respect by acknowledging that an idea you <em>just</em> came up with may be something they already considered, since they’ve been thinking about the problem longer than you.</p><h4>Don’t Ask Leading Questions</h4><p>It’s natural to want to deliver critical feedback in a diplomatic way. It’s common to hear feedback in phrases like, “Do you think the design is a little noisy with that graphic?” or “Do you think it would be better if the text was bigger?” These are leading questions. A leading question is when you ask a question and secretly insert the answer you want. This phrasing reveals that the person <em>asking</em> the question holds an opinion, but maybe doesn’t want to come off too strong when expressing it. However, this puts the person receiving the feedback in a position of having to answer a leading question without knowing the motivation behind it. Even if the intentions are good, it can feel manipulative and inadvertently lead to arguments.</p><p>There are much better ways to express feedback directly without masking the opinion in a question. A few phrases you could use:</p><ul><li>I think that….</li><li>In my opinion…</li><li>If you ask me…</li></ul><p>So instead of “Do you think it would be better if the text was bigger?” you could say “In my opinion, the text is a bit hard to read. Making the text bigger could improve the legibility.”</p><h4>Be Specific</h4><p>Always explain why you’re giving the feedback so that the presenter understands what they can improve in the design.</p><p>For example, simply asking:</p><blockquote>Have you thought about moving that button to the bottom of the screen?</blockquote><p>This is just a yes or no question (and a leading question). It doesn’t convey a point of view or an opportunity to improve the design. If you really just want to know if they’ve thought about moving the button, the answer is probably yes! So what?</p><p>Asking a general question:</p><blockquote>What if you move the button to the bottom of the screen?</blockquote><p>This is a suggestion for a different approach, however, you haven’t conveyed why this approach improves the design. Let’s say we move the button to the bottom of the screen. So what?</p><p>If you were to say:</p><blockquote>I feel like the button on top throws off the visual hierarchy. As a user, it might make it hard to know what I should do. What if the button was at the bottom of the screen?</blockquote><p>Aha! This is great! You’ve specified what might be causing the design to struggle. You’ve helped identify a possible solution. These are the types of things that sometimes take multiple points of view to uncover. This is why we have Crit!</p><h4>Feedback That’s Out of Scope</h4><p>If you want to give feedback outside of what the presenter asked for, ask yourself how your feedback might impact the process of their work.</p><p>Notice a few small things that might be worth flagging in this meeting? Write it down. Mention it at the end of the presenter’s time allotment or mention it to them separately after the meeting.</p><p>Have concerns at the strategy level and feel the work might need to course-correct? Wait until the presenter has specified what feedback they’re looking for (presenter: be concise!). Let the presenter know you have a question that is outside of the scope and need clarity before the conversation moves forward. From here, the group should be able to discern if it merits pivoting the conversation to a different scope or if it is best to set a follow-up meeting.</p><h3>What If I Don’t Know How To Give Feedback?</h3><p>If you’re just getting started in your design career or you’re not a designer, it can be hard to know what details to look for in order to offer critique. If you’re feeling a little lost or unsure of how to contribute in Crit, start by asking yourself:</p><ul><li>Is there anything about the work being presented that is confusing to me?</li><li>Could the work being presented be simplified? Are there any elements or screens that could be removed or taken away?</li><li>How does the work being presented impact the way the user experiences the product as a whole?</li></ul><p>If these questions trigger thoughts or feedback in your mind, share that out loud with the group. There’s no right or wrong answer!</p><h3>Coming Up Next</h3><p>Part 4 of this will dive in to the actual conversations in design critique, how to give feedback and how to receive it.</p><p><a href="https://medium.com/bleacher-report-design/part-4-the-role-of-design-critique-in-decision-making-33170d9599a1">Part 4: The Role of Design Critique In Decision-making</a></p><p><strong>Want to be part of our product design team? We’re hiring! Reach out to learn more. carolann.merchant@bleacherreport.com</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7eac60d878d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/part-3-feedback-c7eac60d878d">Part 3: Feedback</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 2: Presenting Your Work]]></title>
            <link>https://medium.com/bleacher-report-design/part-2-presenting-your-work-42527be7cfb4?source=rss-350754aef755------2</link>
            <guid isPermaLink="false">https://medium.com/p/42527be7cfb4</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[critique]]></category>
            <dc:creator><![CDATA[Carolann Merchant]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 17:36:33 GMT</pubDate>
            <atom:updated>2019-09-24T17:38:38.347Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nkvb4tv1_Xp2sRSAB-0gSw.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h4>The Crit Playbook</h4><p><a href="https://medium.com/bleacher-report-design/part-1-introduction-2282140ddf0b">Part 1 of this series</a> covered why critique is important and how to decide when you’re ready for feedback. Part 2 offers guidance on how to present your work once you’ve decided you’re ready for feedback from a group.</p><h3>Presenting</h3><p>Even in Crit, people can suffer from information overload or get easily distracted. When you’re presenting, you can do a lot to make your work easy to follow. This will help everyone be able to participate and makes sure you get the most benefit out of everyone’s time.</p><h3>Set Context</h3><p>When you’re presenting, always start by giving a little background on your work. This should only take 2–3 minutes. To being concise when you’re setting context, it helps to know what <strong>type feedback you need</strong>. Then ask yourself, what is the minimum context necessary to enable others to provide feedback? Try presenting only that context. Leaving more time for others to talk means you’ll get more feedback or more specific questions on what type of context they might find helpful.</p><p>If you think it will take longer than 2–3 minutes to set the context, you might be sharing too much at once. The full context of your work is not needed in order to get input. Focusing on a specific portion of your work will help you get actionable feedback.</p><p>Here are some details that are usually helpful to include for any project:</p><ul><li>The problem you’re trying to solve</li><li>The outcome you’re hoping to achieve for the user</li><li>Constraints you’re designing within (such as timelines, scope, resources, technical limitations, etc.)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PWRa3JcanCUk2NNI7oexBA.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h3>Show. Don’t Tell!</h3><p>Our brains process images faster than text. Less effort is required of an audience when pictures <em>support</em> a message. A good rule of thumb for any presentation is to ask the audience to read OR listen, but not both. Use visuals (like sketches, wireframes, mockups, screenshots, etc.) to illustrate your points while you talk.</p><h4>Things you can say without showing it:</h4><ul><li>The problem you’re solving</li><li>The type of feedback you need</li><li>Constraints (e.g. deadlines, resources)</li><li>Goals, hopeful outcomes, metrics for success</li></ul><h4>Things you can show through visuals:</h4><ul><li>Complex details that help illustrate context</li><li>What the current solution looks like (assuming you’re improving an existing feature)</li><li>Ideas you previously tried that you already ruled out</li><li>The specific part of the design that needs feedback</li></ul><p>It’s important for your visuals to be easy to digest. Avoid putting a bunch of words on the screen. People will naturally try to read and listen at the same time, which distracts from actually processing the information.</p><p>Avoid small labels or arrows through flows that can’t be quickly understood. A better approach for feedback on flows is to show a before and after visual. This makes it more clear how your work is different from what currently exists, and where you need feedback.</p><p>People see and interpret almost everything through contrast and comparison. The contrast between before and after helps separate your work from what currently exists, and highlights the differences where you need input.</p><h3>Facilitate The Conversation</h3><p>As the presenter, it is your job to facilitate the conversation you want to have. To do that, you need to be solid on two things:</p><ul><li>The goals of your project</li><li>The type of feedback you need</li></ul><p>It is your responsibility to keep the conversation focused on the feedback you need. If someone is giving feedback that is off topic or out of scope for the conversation you want to have, it’s your job to point this out. It can be as simple as letting them know, “I see what you’re saying. Right now, I could use more feedback on [reiterate what you need feedback on] first before we have that conversation.”</p><p>It only takes one person to break the seal for off-topic feedback to change the conversation for the whole group. It’s important to keep the conversation on track. In the end, you’re responsible for making sure you get the feedback you need.</p><h4>Talk Less And Listen More</h4><p>Remember, you came to Crit to hear from others! If you find yourself doing most of the talking during your time allotment, you should switch gears and offer the floor to the group.</p><h3>Coming Up Next</h3><p>Part 3 of this series will dive in to the conversations during design critique; how to give feedback and how to receive it.</p><p><a href="https://medium.com/bleacher-report-design/part-3-feedback-c7eac60d878d">Part 3: Feedback</a></p><p><strong>Want to be part of our product design team? We’re hiring! Reach out to learn more. carolann.merchant@bleacherreport.com</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42527be7cfb4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/part-2-presenting-your-work-42527be7cfb4">Part 2: Presenting Your Work</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 1: Introduction]]></title>
            <link>https://medium.com/bleacher-report-design/part-1-introduction-2282140ddf0b?source=rss-350754aef755------2</link>
            <guid isPermaLink="false">https://medium.com/p/2282140ddf0b</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[critique]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Carolann Merchant]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 17:36:09 GMT</pubDate>
            <atom:updated>2019-09-24T17:37:23.893Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vnwe4bpiRmOSNI_vON9m5w.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h4>The Crit Playbook</h4><h3>What is Design Crit?</h3><p>There are many different ways to get feedback on design work: one-to-one conversations, formal reviews, user research, data analysis, the list goes on. This series will focus on how designers can best get feedback during a design critique.</p><p>Most design teams have a weekly critique meeting to make sure designers get the feedback and support they need. This meeting is where designers share unfinished work. We ask to be challenged and to have the successes and flaws in our work pointed out. At times, these conversations can be challenging and sometimes uncomfortable, but the more you open up in Crit the better designer you’ll be.</p><h3>Always Come With A Point Of View</h3><p>The number one rule of Design Critique is to always come with a point of view. Even if it’s a loosely held point of view or an opinion you’re not confident in, you have to come with one. To make products, you have to make decisions. To make informed decisions, you have to form an opinion. As a designer, this is what you’re getting paid for!</p><p>Crit should be a casual environment. But no matter how casual the conversation or the meeting, everyone’s time is important. Coming prepared shows respect for your teammates.</p><h3>Know What Type of Feedback You Need</h3><p>Always communicate what type of feedback you need to the group. This helps everyone focus their input on the details that are most relevant. It also ensures that you get the input you need, rather than input that might be out of scope or jumping ahead of where you are in the process.</p><p>A good place to start is letting people know which aspect of design you’d like input on:</p><ul><li>Visual design</li><li>Interaction design</li><li>User experience</li></ul><h4>Prepare Ahead of Time</h4><p>Spend a few minutes before Crit to prepare. A good practice is to create a separate space or page in your design tool just for that day’s Crit. Only copy/paste in the visuals you need feedback on and the visuals you might need to include for context. This prevents scrolling around in big design files (jarring for everyone) and forces you to narrow down <em>only</em> the information needed for feedback and how best to present it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UiPM8dVuPO1Wx86bcUc3EQ.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h3>When To Show, When Not To Show</h3><p>It can be hard to know when is the right time for outside input on your work. At times it’s helpful. Other times it can introduce confusion. There are a few ways you can decide whether you should present your work in Crit.</p><h4>You should present in Crit when:</h4><ul><li>You’re blocked; you’ve explored all the possible or reasonable options but could use some extra brain power to make sure you’re not missing an opportunity.</li><li>You need input on something specific to refine your current solution. Maybe an extra pair of eyes could help identify improvements you hadn’t thought of yet.</li><li>You feel like you’ve landed on the right design, but want a gut check. You want your thinking challenged to make sure you’ve come to the best solution.</li></ul><h4>You should NOT present in Crit when:</h4><ul><li>You haven’t developed your own point of view on the problem you’re solving. You haven’t had a chance to fully understand the goals of your project yet.</li><li>You haven’t had a chance to explore different approaches on your own. There’s still a lot of low-hanging fruit or obvious ideas to try out first before getting feedback.</li><li>Your mockups are a mess and you don’t have any digestible visual assets prepared. You won’t be able to facilitate a productive conversation.</li><li>You have new work you’ve completed but you don’t really need feedback.</li></ul><h3>Tips For Organizing the Meeting</h3><h4>Have An Agenda</h4><p>All meetings should have an agenda. It helps the meeting stay on track and ensures everyone gets the amount of time they need to present. Keep an eye on the time during the meeting and provide reminders when it’s time to switch presenters. The goal is to keep conversations focused and helpful.</p><h4>Laptops Down</h4><p>At the beginning of the meeting, remind everyone to close their laptops and phones when they’re not presenting. It’s better to skip Crit if you need to focus on other work or conversations than to try to multitask during the meeting.</p><h3>Keep An Open Mind</h3><p>No one has all the answers. We need outside points of view to make our best work. Crit is one of the places where that happens. Being in situations where you have to explain the reasoning behind your decisions ensures good design. Others can learn from your decision-making and you learn by having your decision-making challenged!</p><p>It’s always okay to say “I don’t know” or “I’ve tried everything and I <em>still</em> haven’t found a good solution. I need help!” It doesn’t make you seem inexperienced or like you don’t know what you’re doing. It happens to all good designers.</p><h3>Coming Up Next</h3><p>In Part 2 of this series, we’ll cover best practices for how to present your work in crit and how to facilitate the conversation to get the feedback that you need.</p><p><a href="https://medium.com/bleacher-report-design/part-2-presenting-your-work-42527be7cfb4">Part 2: Presenting Your Work</a></p><p><strong>Want to be part of our product design team? We’re hiring! Reach out to learn more. carolann.merchant@bleacherreport.com</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2282140ddf0b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/part-1-introduction-2282140ddf0b">Part 1: Introduction</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>