large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

From Design System to ‘NFT Design System’: Creating TinyFaces

Neurodiversity and Inclusion: Choosing Kinder Design

medium_652ccf22c8853584bde5553986a4eed0.png

small_652ccf22c8853584bde5553986a4eed0.png

thumbnail_652ccf22c8853584bde5553986a4eed0.png

Web5 is here. Goodbye Web3? TBD.

<p><a href="https://uxdesign.cc/the-why-and-how-of-effective-design-critiques-944313947fe4">medium bookmark / Raindrop.io</a> |  </p>
<div>
<div>
<div>
<div>
<div>
<p>Trying to be thoughtful. Design Lead at YouTube. Chrome, Expa, Lookout before that.</p>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<div>
<div><img src="https://cdn-images-1.medium.com/max/2000/1*sbP8WSVXkRiQnXnsEIx0rQ.jpeg" alt="1*sbP8WSVXkRiQnXnsEIx0rQ.jpeg"></div>
</div>
<p>Photo by  on </p></div>
<div>
<p>Critiques are a time-proven way of pushing design ideas forward. Art and design schools have used them as key teaching venues for decades. And while common in corporate teams, I suspect they’re often underutilized.</p>
<p>To start, it’s worth pointing that critiques (&#8220;crits&#8221;):</p>
<ul>
<li>Are not <strong>generative sessions</strong> (divergent, idea generation meetings). These tend to involve different project stakeholders and happen early in the design process.</li>
<li>Are not <strong>evaluative sessions (</strong>convergent, approval-oriented meetings). These focus on making a decision, and by definition happen later in the process.</li>
</ul>
<p>Critiques are <strong>iterative sessions,</strong> where the design team comes together to comment on work in progress. It’s an opportunity to enrich solutions between the divergent/generative beginning and the convergent/decisive end of a design cycle.</p>
<h3>Why Critiques</h3>
<p>Some of the advantages of having critiques sessions are obvious.</p>
<blockquote><p>“Feedback is the breakfast of champions.”<br /><em>&#8211; Ken Blanchard</em></p></blockquote>
<p>First of all, <strong>you get better results</strong>. The more capable, dedicated people look a problem, better the chances of finding an elegant solution.</p>
<p>Critiques also <strong>increase the chance of cross-pollination</strong>. When designers from different sub-teams or who are tackling different problems meet, they create opportunities to spot patterns in their problems and solutions and to rethink their approaches based on the big picture. Along the same lines, critiques <strong>allow organic consistency to emerge</strong>: if your product lacks a comprehensive style guide, they help ensure consistent patterns are used.</p>
<p>But what excites me the most about crits are how they can help a design team grow, both as a group and as individuals.</p>
<p>By having to quickly articulate a problem, its constraints and proposed solutions, designers <strong>exercise their presentation skills. By doing so</strong> regularly and in a safe space, they get better at it. And since crits are about gathering feedback, designers must be able to <strong>effectively articulate what feedback is valuable and handle it well.</strong></p>
<p>Designers often feel frustrated by seemingly off-topic or untimely feedback when presenting to other functions (product, engineering, marketing, etc). What they often don’t realize is that it’s their own fault. <em>It’s a designers responsibility to set up the conversation so the scope of feedback is valuable to them at a given point in time.</em><em> </em>Critiques force designers to do so, but in a safer space than an evaluative presentation.</p>
<p>It can also be hard to handle criticism in cross-functional presentations, especially after spending tons of energy. Critiques can help designers foresee objections, strengthening their designs, and develop the ability to handle them with grace.</p>
<h3>How to Run a Critique session</h3>
<p>It would be silly to say there’s one best way of running critiques. The art school model tends to be pretty brutal, and promote growth through negative reinforcement. Some teams love rules, some teams less so. But I’ve observed over time that successful critiques share a few attribute, which I recommend here.</p>
<h3>People</h3>
<ul>
<li><strong>Design-team only.</strong> Critiques should be a safe space where people can be themselves, present incomplete work and discuss minutiae which could be deemed irrelevant by other functions. That’s why I believe attendance should be limited to members of the design team (which in my definition would include UX Researchers, writers, etc).</li>
<li>In terms of numbers, <strong>4 people seem to be the critical mass</strong> for a session to flow. Large groups (15+) can derail the conversation — or just not fit in the allotted time. You can work around that issue by breaking sessions into multiple meetings on different days.</li>
<li>It’s also important to <strong>appoint a facilitator</strong>, whose role is to balance the more and less vocal people and ensure the session’s fluidity. They don’t have to be a team lead, and the role can be on a rotation. And while the facilitator should be encouraged to also provide feedback, their thoughts don’t count any more or less than the other participants’.</li>
</ul>
<h3>Logistics</h3>
<ul>
<li>Make sure your critiques are <strong>regular and frequent</strong>. They should be part of the team’s routine. One hour once a week seems to be a favorite. Many teams also formalize a number of slots (say 3 slots, 20 minutes each) which can be booked ahead, so sessions is fully scheduled ahead of time.</li>
<li>If they’re not, the facilitator should <strong>prepare an agenda</strong> beforehand, calling for presenters. You may want to have a fixed presenter rotation, but ideally your critiquess are so valuable (and fun!) that presenters volunteer by themselves.</li>
<li>Presenters should <strong>make it clear if they’d rather hear feedback or questions during their presentation or afterward</strong>. It’s up to personal preference, but I see much better results when it comes at the end: many questions are organically answered during the presentation and it allows the presenter to control the timing.</li>
<li><strong>Present unfinished work</strong>. The rougher the better — there’s more room for new ideas to make it in. That’s why it’s so important to create a safe space: designers should be comfortable sharing incomplete ideas and low fidelity mocks with no fear of judgement.</li>
<li>While a presenter is speaking, participants should <strong>write their thoughts on sticky notes, and read from them later</strong>. This avoids interruptions, forgotten comments and saves on note-taking: presenters can just take all sticky notes back to their desk to process after the meeting. It also forces participants to articulate their ideas in writing or, better yet, sketches.</li>
<li>It might seem random, but I’ve noticed that <strong>when everyone stands up</strong> during the course of the meeting, <strong>feedback flows best</strong>. The passive, evaluative posture of leaning back on conference room chairs seems to lead to less participation.</li>
</ul>
<h3>A Note on distributed teams</h3>
<p>Critiques surely work best when the entire team is in the same room, standing up, looking at the same screen or print-out. It’s hard to recreate that same dynamic for distributed teams, especially across time zones.</p>
<p>One definite requirement is a great video-conferencing system and screens large enough for people’s expressions to be captured. Good cameras where sticky notes can be shown are also important. And facilitators must pay extra attention to ensure everyone participates especially if there’s a significant difference in number of people between HQ and other locations.</p>
<h3>Conclusion</h3>
<p>To summarize, my recommendations are to:</p>
<ul>
<li>Make crits regular and frequent</li>
<li>Make them exclusive to the design-team</li>
<li>Appoint a facilitator</li>
<li>Collect an agenda beforehand</li>
<li>Present unfinished work</li>
<li>Ensure presenters are clear about what feedback is valuable</li>
<li>Write feedback on sticky notes</li>
<li>Stand up if you can</li>
</ul>
<p>And treat critiques like any design project: <em>ideate, test, iterate</em>. Don’t settle for this model, and don’t give up if things don’t flow right away. Find the model which works for your team, and you’ll be harvesting benefits for a long time.</p>
</div>
</div>
</div>
<div>
<hr>
<div>
<div>
<p><em>You should consider </em><a href="http://twitter.com/bbergher"><em>following me on Twitter</em></a><em>.</em></p>
</div>
<div>
<div></div>
</div>
</div>
</div>
</div>
<div><a href="https://uxdesign.cc/the-why-and-how-of-effective-design-critiques-944313947fe4">https://uxdesign.cc/the-why-and-how-of-effective-design-critiques-944313947fe4</a></div>


The why and how of effective design critiques Elevate your product, elevate your team

The why and how of effective design critiques Elevate your product, elevate your team

Top Stories