Over the years I've tried many approaches to design critiques with the teams I've managed. Without fail these 4 simple principles impact the effectiveness of design critiques greater than anything else when established as ground rules. For presenters: ✦ Describe the problem you're solving ✦ State the target audience* ✦ Specify the feedback you're seeking All of the above can be done in less than a minute, either verbally or in written format. For participants: ✦ Ask questions before comments "I think you should go with blue instead of red" is less effective than first asking "Why did you choose red for this?" The additional context that comes from asking questions will lead to more effective feedback. Design critiques are the easiest and most important thing design teams can do to improve design quality. Alone they are not a silver bullet. But they are the foundation for all other improvements to design quality. If you're not holding regular design critiques (usually weekly), this is step 1 for improving design quality. If you're already holding regular design critiques but not doing the 4 principles above well, this is step 1 for improving your design critiques. Better critiques. Better quality. * "Everyone" is rarely acceptable as the target audience. Even if the feature being presented is intended for everyone, 99% of the time there's a specific segment or archetype you're aiming for. #design #critiques #quality
This might be a relevant tool for this discussion I call it design proofreading https://www.designandculture.net/blog/design-proofreading?rq=Proof
This is totally true. I used to work with a company that really understands design. Then I moved to a new company and presented my design for feedback, thinking they understood design. But to my surprise, I got loads of critiques. I had to spend the next week creating a document that explained the basis of my design decisions. It was totally my fault because I didn’t understand the audience I was preparing for. Next time, I planned my design feedback session with clear guidelines and specific areas for feedback. Even though I still received many comments, the number of bogus ones was reduced. 🙂↕️
I 100% agree with this. I’ve been documenting best crit practices for years; they’re all included with the CritKit I’ve been building.
These are great Cam! “Specify the feedback you’re looking for” is such a small addition that brings huge value to a critique! Otherwise, teams can spend a lot of time talking about the work without helping move the project forward
I love this. I might add that if the group has established design or project phases (ex: discovery, concept or detailed design phase), it’s usually helpful to add that information, maybe as a subpoint of the type of feedback the designer is looking for.
Simple and elegant approach to crits. It’s easy to over complicate these sessions and that can put people off doing them. Cameron Moll has nailed it with this approach. Think purpose, business, customer and be specific about exactly what you want from your peers. Thanks for sharing.
Will implement see how it goes.
Love this, Cameron! As one giving feedback, I especially need to remember "ask questions before comments" - great reminder, thank you!!
Solid advice Cameron Moll! Thanks for sharing.
CMO, Co-founder at Torus
3wI've learned the only way to give design critique is one on one. It provides a safe space for both people, provides a chance to go deep, it's collaborative instead of one sided, and prevents any embarrassment for younger designers.