Slides from our workshop at Booster 2016. "Everyone" is talking about the importance of doing design critiques, because it promises to improve the solutions we create. But as former "UX teams of one" we have rarely seen this done systematically. In this workshop you will get tips on how to conduct a design critique; some ground rules for giving and receiving feedback; and some suggestions on how to introduce design critiques in your organization. Then we will get our hands dirty and actually do some rounds of critiquing.

1. HOW TO CONDUCT A
DESIGN CRITIQUE
Ram Yoga and Tor Anders Dybing
BOOSTER 2016

2. RECIPE RULES PRACTICE
2

3. Improve the solution
3
Purpose

4. Improve the solution
4
Purpose
Improve as designers

5. 5
Who to invite?
3-6 people
useful feedback

6. 25–75 %
6
How complete should the design be?

7. facilitator
critics
presenter

8. RECIPE FOR DESIGN CRITIQUE-MEETING
1. Establish the facilitator
8

9. RECIPE FOR DESIGN CRITIQUE-MEETING
1. Establish the facilitator
2. Identify the designer
9

10. RECIPE FOR DESIGN CRITIQUE-MEETING
1. Establish the facilitator
2. Identify the designer
3. Explain what type of feedback you need
10

11. RECIPE FOR DESIGN CRITIQUE-MEETING
1. Establish the facilitator
2. Identify the designer
3. Explain what type of feedback you need
4. Repeat the design goals
11

12. RECIPE FOR DESIGN CRITIQUE-MEETING
1. Establish the facilitator
2. Identify the designer
3. Explain what type of feedback you need
4. Repeat the design goals
5. Show the design
12

13. RECIPE FOR DESIGN CRITIQUE-MEETING
1. Establish the facilitator
2. Identify the designer
3. Explain what type of feedback you need
4. Repeat the design goals
5. Show the design
6. Write down the feedback (5-10 min)
13 flickr.com/danielfoster/14813000931/

14. RECIPE FOR DESIGN CRITIQUE-MEETING
1. Establish the facilitator
2. Identify the designer
3. Explain what type of feedback you need
4. Repeat the design goals
5. Show the design
6. Write down the feedback (5-10 min)
7. Don’t design in the meeting
14
flickr.com/un_photo/4080558655/

15. RECIPE FOR DESIGN CRITIQUE-MEETING
1. Establish the facilitator
2. Identify the designer
3. Explain what type of feedback you need
4. Repeat the design goals
5. Show the design
6. Write down the feedback (5-10 min)
7. Don’t design in the meeting
8. Finish with a task list
15

16. RECIPE RULES PRACTICE
16

17. flickr.com/photos/cenz/26416145

18. HOW TO GIVE GOOD FEEDBACK
• Listen before you speak
18

19. HOW TO GIVE GOOD FEEDBACK
• Listen before you speak
• Know the goals
19

20. HOW TO GIVE GOOD FEEDBACK
• Listen before you speak
• Know the goals
• Most important feedback first
20

21. HOW TO GIVE GOOD FEEDBACK
• Listen before you speak
• Know the goals
• Most importantfeedback first
• Ask questions, don’t assume
21

22. HOW TO GIVE GOOD FEEDBACK
• Listen before you speak
• Know the goals
• Most importantfeedback first
• Ask questions, don’t assume
• Don´t forget what works
22

23. HOW TO GIVE GOOD FEEDBACK
• Listen before you speak
• Know the goals
• Most importantfeedback first
• Ask questions, don’t assume
• Don´t forget what works
• Point to specific elements
23

24. HOW TO GIVE GOOD FEEDBACK
• Listen before you speak
• Know the goals
• Most importantfeedback first
• Ask questions, don’t assume
• Don´t forget what works
• Point to specific elements
• Distinguish between opinion
and data
24

25. HOW TO RECEIVE FEEDBACK
• Shut up, and make notes
25

26. • Shut up and make notes
• Use active listening
26
HOW TO RECEIVE FEEDBACK

27. • Shut up, and make notes
• Use active listening
• Refer back to the goals
27
HOW TO RECEIVE FEEDBACK

28. • Shut up, and make notes
• Use active listening
• Refer back to the goals
• Don’t be defensive
28
HOW TO RECEIVE FEEDBACK

29. • Shut up, and make notes
• Use active listening
• Refer back to the goals
• Don’t be defensive
• Say thanks
29
HOW TO RECEIVE FEEDBACK

30. RECIPE RULES PRACTICE
30

31. TIPS
31

32. Catalyst
32
Tips on how to implement #1

33. Use rituals
33
Tips on how to implement #2

34. Critique
≠
must or should be fixed
34
Tips on how to implement #3

35. Thanks!
@ramyo
ry@computas.com
@toranders
tad@computas.com