a systematic approach to design critique
Post on 14-Jan-2017
510 Views
Preview:
TRANSCRIPT
A Systematic Approach to Design Critique
Zac Halbert@ZacHalbert
Product design lead at Tradecraft
TryMyUI@trymyui
#trymyuiEDU
1
Why critique?
Designcritique
A formal, regularly scheduled design critique process helps designers improve, and provides professional development.
It’s also an acknowledgement that designers don’t have to be perfect at all times and WIP is acceptable.
Critical to implement, especially when your design team lacks senior mentorship.
Good / BadBetter / Worse
Applies to designers, and designs
2.
Fixed mindset is lazy, and will result in high designer turnover
3.
1. Growth mindset
Good / BadBetter / Worse
Applies to designers, and designs
2.
Fixed mindset is lazy, and will result in high designer turnover
3.
1. Growth mindset
Good / BadBetter / Worse
Applies to designers, and designs
2.
Fixed mindset is lazy, and will result in high designer turnover
3.
1. Growth mindset
Builds teams
Reduces awkwardness
Builds common lingo
Prevents blindspots
Creates team-wide ownership
Regular critique makes designers better
Analyzing other people’s work improves your taste, and makes you better at spotting your own weaknesses.
It also helps designers separate ego from work.
2
The setup.
Decide on a format, then post it publicly
Discuss the process with non-design stakeholders beforehand.
2.
Do a retrospective, then tweak the format next time.
3.
1. Write an agenda and schedule
on the whiteboard at the start of every critique session.
Decide on a format, then post it publicly
Discuss the process with non-design stakeholders beforehand.
2.
Do a retrospective, then tweak the format next time.
3.
1. Write an agenda and schedule
on the whiteboard at the start of every critique session.
Decide on a format, then post it publicly
Discuss the process with non-design stakeholders beforehand.
2.
Do a retrospective, then tweak the format next time.
3.
1. Write an agenda and schedule
on the whiteboard at the start of every critique session.
Roles13
I. Designer
II. Participant
III. Facilitator
IV. Timekeeper
V. Notetaker (optional)
Other guidelines
Review rules of conduct before the meeting until everyone knows them by heart.
Limit the number of people participating. 8-10 max is a good guideline, but depends heavily on the rapport within your team and the project requirements. Some teams can have free form conversation, some need to take turns. Experiment with what works.
Establish design principles before you start your first critique session.
Design principles
Like a mission statement, these are guiding principles that you decide on outside the context of design critique. However, when differences of opinion arise, the principles can keep everyone focused on what is most important. Great way to engage non-design stakeholders.
http://www.lukew.com/ff/entry.asp?854
16DeferenceClarityDepth
AppleDesigning for iOS, Human Interface Guidelines*
* https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/
17UniversalHumanCleanConsistentUsefulFastTransparent
FacebookDesign principles, posted 7 / 1 / 09
* https://www.facebook.com/note.php?note_id=118951047792&ref=mf
Design rubric
ContentAffordancesTypographyLayoutImageryColor
18
Rules of conduct
No disclaimers, no selling work.
Keep the preamble very concise, and focused on the type of feedback you need. 60 seconds is likely sufficient.
Assume participants have good intentions.
Accept feedback graciously (say thanks). People avoid giving feedback to a defensive designer, which will limit your growth.
Presenter
Rules of conduct
Participant goals are to make the designer better long term, and to co-solve the challenges they are facing.
Speak up, but don’t monopolize the conversation.
No egos. People probably aren’t as impressed by your “eye for design” as you are. Don’t be a jerk.
Have sticky notes and pens handy, jot down things you might forget. Participate in the conversation, don’t wait for your turn to speak.
Participant
Design critique setup checklist
❏ Assign roles❏ Post agenda and schedule❏ Post design principles❏ Post design rubric❏ Post / discuss rules of
conduct
3
The critique.
23
Macro ProblemsHigh level goals, usually obvious to
everyone involved.
Micro ProblemsVisual design choices, rarely
obvious unless you ask.
What problem are you trying to solve?
Designer preamble
Discuss fidelity level, and percentage complete.
2.
What feedback don’t you want?3.
1. Frame the macro and micro
problems you’re solving.
Designer preamble
Discuss fidelity level, and percentage complete.
2.
What feedback don’t you want?3.
1. Frame the macro and micro
problems you’re solving.
Designer preamble
Discuss fidelity level, and percentage complete.
2.
What feedback don’t you want?3.
1. Frame the macro and micro
problems you’re solving.
Givingcritique
Thing in terms of solution strength, rather than good/bad.
2.
Pose questions rather than statements.
3.
1. Watch out for fundamental
attribution error.
Givingcritique
Thing in terms of solution strength, rather than good/bad.
2.
Pose questions rather than statements.
3.
1. Watch out for fundamental
attribution error.
Givingcritique
Thing in terms of solution strength, rather than good/bad.
2.
Pose questions rather than statements.
3.
1. Watch out for fundamental
attribution error.
“Posing thoughts as questions allows the designer to express their reasoning
instead of being defensive. If they hadn’t considered a particular angle, they can make a note and address it in the next
iteration.”
Judy Reeves
Receivingcritique
Hopefully, people will be respectful. Grow a thick skin for when they’re not.
If you feel terrible after critique, that’s a signal you’re identifying too closely with your work. It’s not your child, even if it feels that way sometimes.
Invite participants to co-solve with you.
We’re not as good at visualizing as we think. Be willing to try other people’s ideas. “That won’t look good” vs “I’ll try it and see.”
Designers: stop being so precious with your work. You won’t get better if you don’t ask for feedback early and often.
Mindset, notFixedMindset
GrowthSuccessful critique requires a
Thanks!
Zac Halbert@ZacHalbert
top related