In this presentation we’ll discuss the importance of critique and a language for discussing design. It can be easy to complain about the way things are and theorize on the way things should be. Progress comes from understanding why something is the way it is and then examining how it meets or does not meet it’s desired goals. This is critique. Critique is not about describing how bad something is, or proposing the ultimate solution. Critique is a dialogue, a conversation that takes place to better understand how we got to where we are, how close we are to getting where we want to go and what we have left to do to get there.
The contents of this presentation will focus on:
understanding critique
best practices for incorporating critiques into a design practice
identifying common challenges to critique and ways to improve our ability to deliver, collect and receive critique
8. Tips for giving critique...
• Use a lter. Gather initial thoughts and
reactions. Revisit them in the right context.
9. Tips for giving critique...
• Use a lter. Gather initial thoughts and
reactions. Revisit them in the right context.
• Don’t assume. Find out the reason behind
thinking, constraints or other variables.
10. Tips for giving critique...
• Use a lter. Gather initial thoughts and
reactions. Revisit them in the right context.
• Don’t assume. Find out the reason behind
thinking, constraints or other variables.
• Don’t invite yourself. Get in touch and ask to
chat about the design.
11. Tips for giving critique...
• Use a lter. Gather initial thoughts and
reactions. Revisit them in the right context.
• Don’t assume. Find out the reason behind
thinking, constraints or other variables.
• Don’t invite yourself. Get in touch and ask to
chat about the design.
• Lead with questions. Show interest in their
process.
14. Tips for receiving critique...
• Remember the purpose: improvement, not
judgement.
15. Tips for receiving critique...
• Remember the purpose: improvement, not
judgement.
• Listen. Do you understand what the critics
are saying?
16. Tips for receiving critique...
• Remember the purpose: improvement, not
judgement.
• Listen. Do you understand what the critics
are saying?
• Think before you talk back.
17. Tips for receiving critique...
• Remember the purpose: improvement, not
judgement.
• Listen. Do you understand what the critics
are saying?
• Think before you talk back.
• Refer to the goals.
18. Tips for receiving critique...
• Remember the purpose: improvement, not
judgement.
• Listen. Do you understand what the critics
are saying?
• Think before you talk back.
• Refer to the goals.
• Participate just like any other critic.
22. A few things to keep in mind...
• Critique is a skill. You only
get better with practice
23. A few things to keep in mind...
• Critique is a skill. You only
get better with practice
• Start small (internal only)
24. A few things to keep in mind...
• Critique is a skill. You only
get better with practice
• Start small (internal only)
• Think before you speak
25. A few things to keep in mind...
• Critique is a skill. You only
get better with practice
• Start small (internal only)
• Think before you speak
• Choose who you
critique with carefully
28. The Rules of Critique
• Everyone is a critic.
• Everyone is equal.
29. The Rules of Critique
• Everyone is a critic.
• Everyone is equal.
• The designer decides
what to act upon.
30. The Rules of Critique
• Everyone is a critic.
• Everyone is equal.
• The designer decides
what to act upon.
• Avoid problem
solving and design
decisions.
36. When and what should you be critiquing?
In the beginning of a project...
What You’re Working On
• Setting high level user & business goals
• User research, competitive analysis
• Initial concepts & vision
Example Goals
• Get feedback about a set of different concepts / approaches
• Explore the designs of competing products
What You Might Look At
• Competing products
• Conceptual models/sketches/ ows
37. When and what should you be critiquing?
In the middle of a project...
What You’re Working On
• Detailed interactions & product behaviors
• Identifying variations in ows
• Solving for constraints
Example Goals
• Compare the design of system components
• Identify potential usability issues
• Get cross-functional team feedback
What You Might Look At
• Screen- ow diagrams
• Wireframes / Prototypes
38. When and what should you be critiquing?
At the end of a project...
What You’re Working On
• Finalizing detailed design
• Solidify answers or solutions to issues
• Solving for constraints
Example Goals
• Analyze design details and the product’s full impact
• Discuss usability issues
• Get cross-functional team feedback
What You Might Look At
• High Fidelity Prototypes
• Beta/Pilot Systems
49. Help with handling difficult people...
• Set expectations at the beginning
50. Help with handling difficult people...
• Set expectations at the beginning
• Make sure everyone understands critique
51. Help with handling difficult people...
• Set expectations at the beginning
• Make sure everyone understands critique
• Ask quiet people for feedback directly
52. Help with handling difficult people...
• Set expectations at the beginning
• Make sure everyone understands critique
• Ask quiet people for feedback directly
• Use personas and goals to keep focused
53. Help with handling difficult people...
• Set expectations at the beginning
• Make sure everyone understands critique
• Ask quiet people for feedback directly
• Use personas and goals to keep focused
• Laddering / The 5 Whys
56. In Summary
• Critique is a life skill, not a design skill
57. In Summary
• Critique is a life skill, not a design skill
• Critique focuses on what works, what doesn’t
and why. It’s analysis.
58. In Summary
• Critique is a life skill, not a design skill
• Critique focuses on what works, what doesn’t
and why. It’s analysis.
• Intent is critical to the success of a critique, both
in giving and receiving.
60. In Summary
• Learning to critique improves our ability to
communicate with teams, clients and others
and only improves with practice.
61. In Summary
• Learning to critique improves our ability to
communicate with teams, clients and others
and only improves with practice.
• Critique can be done both internally and with
clients. Use 3-6 people for about 1 hour.
62. In Summary
• Learning to critique improves our ability to
communicate with teams, clients and others
and only improves with practice.
• Critique can be done both internally and with
clients. Use 3-6 people for about 1 hour.
• Be sure to clearly communicate the goals of a
critique session as well as ground rules to all
participants.
63. Additional Resources
• The Art of the Design Critique (Aarron Walter - Think Vitamin)
http://thinkvitamin.com/design/the-art-of-the-design-critique/
• Dealing with Design Critiques (Jacob Gube - Design Instruct)
http://designinstruct.com/articles/project-management/dealing-with-design-critiques/
• Design Criticism and the Creative Process (Cassie McDaniel - A List Apart)
http://www.alistapart.com/articles/design-criticism-creative-process/
• Everything I’ve Ever Learned About Giving Design Critiques I Learned from Tim
Gunn (Dan Saffer - Kicker Studio)
http://www.kickerstudio.com/blog/2010/11/everything-ive-ever-learned-about-giving-
design-critiques-i-learned-from-tim-gunn/
• What Goes into a Well-Done Critique (Jared Spool - UIE)
http://www.uie.com/articles/critique/
64. How’d we do???
Aaron Irizarry (Aaron I for short)
User Experience Designer
http://thisisaaronslife.com
aaron@thisisaaronslife.com
@aaroni268
Adam Connor (no catchy nickname)
Experience Design Director
http://adamconnor.com
adam@adamconnor.com
@adamconnor
Notas del editor
Intro\nTell story\n
Aaron\nWe talk about critique in the context of giving feedback\nOften it’s equated with giving feedback, but it’s more specific than that. It’s a deliberate, active process\nFeedback is nothing more than how we react to something.\nCritique identifies where/how a design meets or doesn’t meet specific goals.\nIt’s a form of analysis.\nIs delivered in a form in which the person receiving it understands and can act upon it.\n
Adam\nActually it’s kind of the reverse of critical thinking\nWhere critical thinking is about problem solving, critique is about trying to understand what problems the designer is trying to solve, and how\nWhy is it important to talk about critique:\nIts something a lot of us talk about doing, but often have challenges with. Particularly with clients.\nHelps establish a common framework for discussing designs and ideas.\nCreates opportunities for more team interaction, building collaboration and trust\nLearning to critique makes us better communicators.\n
Aaron\nIntent is the initiator of critique.\nIt defines the purpose of the critique process.\nThe success of critique hinges on intent. Critique only works when the intent is right on both sides.\n\n
Aaron\nIt is focused on personal goals at the expense of the team or other individuals.\nSelfish Critique:\n140 characters of one sided, open ended critique every time an app/site is launched or updated.\nProviding unwelcome or un-timely feedback, without context, or consideration (in a team environment or otherwise).\n
Adam\nThe right intent is wanting to improve the product\nIt is focused on helping facilitate conversation and critical thinking that leads to improvement.\nThe best critiques are a discussion.\n
Adam\n
Adam\n
Adam\n
Adam\n
Aaron\nRequesting feedback for personal validation. If you need a hug just ask :)\nAsking for feedback with no intent of listening.\nDon’t just hear... Listen.\nDon’t take it personal... even if someone else seems to be going there.\nEven if you know that someone else is wrong, or in the wrong, take their insights into consideration. \n
Aaron\nRecognize that there is no such thing as a perfect solution, there is always room for improvement.\nThink before you talk back. Are you being defensive? Protective?\nRemember that you are (supposed to be) in control. It's up to you to decide what feedback to act on and what not to.\n
Aaron\nRecognize that there is no such thing as a perfect solution, there is always room for improvement.\nThink before you talk back. Are you being defensive? Protective?\nRemember that you are (supposed to be) in control. It's up to you to decide what feedback to act on and what not to.\n
Aaron\nRecognize that there is no such thing as a perfect solution, there is always room for improvement.\nThink before you talk back. Are you being defensive? Protective?\nRemember that you are (supposed to be) in control. It's up to you to decide what feedback to act on and what not to.\n
Aaron\nRecognize that there is no such thing as a perfect solution, there is always room for improvement.\nThink before you talk back. Are you being defensive? Protective?\nRemember that you are (supposed to be) in control. It's up to you to decide what feedback to act on and what not to.\n
Aaron\nRecognize that there is no such thing as a perfect solution, there is always room for improvement.\nThink before you talk back. Are you being defensive? Protective?\nRemember that you are (supposed to be) in control. It's up to you to decide what feedback to act on and what not to.\n
Adam\n
Aaron\nAn introduction to participants unfamiliar with giving structured feedback.\nA safe(er) place to practice giving and receiving feedback.\nCritique vs. Review meetings\n
Aaron\n
Aaron\n
Aaron\n
Aaron\n
Adam\nThe “I like/don’t like” situation.\nAlways make sure to review these (and any other) ground rules with clients to gauge how comfortable they are with them before planning a critique.\nAlso, post the ground rules in the room where the critique will be held.\n\n
Adam\nThe “I like/don’t like” situation.\nAlways make sure to review these (and any other) ground rules with clients to gauge how comfortable they are with them before planning a critique.\nAlso, post the ground rules in the room where the critique will be held.\n\n
Adam\nThe “I like/don’t like” situation.\nAlways make sure to review these (and any other) ground rules with clients to gauge how comfortable they are with them before planning a critique.\nAlso, post the ground rules in the room where the critique will be held.\n\n
Adam\nThe “I like/don’t like” situation.\nAlways make sure to review these (and any other) ground rules with clients to gauge how comfortable they are with them before planning a critique.\nAlso, post the ground rules in the room where the critique will be held.\n\n
Aaron \n3 - 6 people\nChoose attendees based on the goal(s) of your session.\nConsider personality, not just roles.\nDon’t use the same people every time.\nPeople to invite:\nExecutives/Business Sponsors/Stakeholders\nSubject Matter Experts\nMarketers\nDevelopers\nBiz Analysts\nOther Designers\n
Aaron\n
Aaron\n
Aaron\n
Aaron\n
Adam\n
Adam\n
Adam\n
Aaron\nSend out materials ahead of time.\nClearly describe the goals of the product but not how it’s intended to achieve them. (flesh this out further)\nPresent quickly.\nBe careful when talking about constraints.\n
Aaron\n
Aaron\n
Aaron\n
Aaron\n
Aaron\n
Aaron\n
Adam\n
Adam\n
Adam\n
Adam\n
Adam\n
Adam\n
Aaron\nTake note of how people participated\nDocument any observations and open questions and post/share them.\nFollow up with individuals to for more feedback or to explore an idea.\nCommunicate next steps: what activities will occur prior to the next critique.\n