
At the SxSW conference, I enjoyed hearing Jason Santa Maria and Rob Weychert share
best practices for design critiques. Here are some key takeaways:
1) Introduce your varied concepts without interruption
2) Introduce the team discussion by asking "What works? What doesn't?"
> Keep the conversation moving, as the team may get hung up on details. At this early stage however, it's best to capture overall feelings instead of tiny details.
> Make sure each design is discussed adequately. Sometimes the team will say "that's the one!" and not chat about the other designs, but much can be learned from what is/isn't working in the other designs to help the refinement stage.
> Stay "problem-focused" as the team will likely share solutions instead since it's easier for them to articulate those. A typical "solution" is to take one thing from the first concept, another from the second and yet another from the third. Recognize that if you say "yeah, we can do/change that" during the review, it may screw up the design when you actually try it out. Say that a potential solution is something you'd like to explore, but you'll keep the actual problem in the forefront and will solve that in the refinement stage.
Click "read more" for more tips.