One of our design principles is ‘design in the open’. This means we choose to be collaborative, we show our early design work and invite feedback. Holding design critiques, or ‘crits’, is a useful way to do this.
Done well, they:
- improve our designs
- improve collaboration between designers and between disciplines
- offer a different perspective
- boost morale and strengthen communities of practice
- show the decisions behind the design
I recently asked on Twitter if a post on ‘how to run crits and how to get the most out of them’ would be useful. People said yes.
So here it is.
What’s the point?
The purpose of a design crit is to give a designer feedback, to evaluate an idea and identify possible changes or different approaches. It’s not to figure out a solution there and then.
Crits can focus on (but definitely aren’t limited to) things like:
- interaction of specific page elements
- a specific user flow
- the emotion a visual style portrays
- competitor services
Who to invite
Having the right people there is essential. The temptation might be to fill the room with designers but inviting people from different disciplines will make sure you hear a range of perspectives. In most cases it’s good to start with content designers and user researchers because their work is so intrinsically linked with design.
But they’re not the only ones who really understand how design works. I’d be hesitant to blanket call out other disciplines, instead I’d say it’s up to the person whose work is being critiqued to use their judgement and invite individuals they think would offer valuable input into the specific thing they’re sharing.
A golden rule is to invite the maximum number of people you’d be comfortable hosting a dinner party for – a group big enough to encourage discussion but not so big things are unmanageable.
It’s best when the crit is led by the designer who did the work so they can explain the decisions they made around their design. It also means they’re there to receive feedback first-hand rather than hear chinese whispers. However, if that designer isn’t comfortable leading the session, someone else can facilitate and steer discussions while the designer makes notes on the feedback.
When to run a crit
Run them often at the start of a project then less frequently as the project goes on. Early crits will most likely focus on top-level ideas. When you’re further along in a project, it’s useful to hold crits to look at particular issues with a view to making specific decisions.
They’re also beneficial before project milestones, for example, before it’s too late to iterate features, flows or ideas.
Actually running a crit
- Start the session by identifying the aim(s) of the discussion. For example, we want to:
- improve the registration flow
- understand if the design is easy to follow
- assess whether the design meets the project goals
- Point out any constraints, blockers and considerations. For example:
- any content that can’t be changed – this might be due to legal or policy restraints, or deadlines
- anything that’s already been built and will take more work to change
- Show the design. At this point it’s useful to:
- explain reasoning or constraints of that specific thing. For example, your navigation choice might need to be consistent with someone else’s work or all the content has been agreed and signed off
- show alternative designs if you have any
- Facilitate discussion by:
- encouraging the group to share 1 or 2 pieces of feedback. Give the option to do this on post-its for anyone not comfortable giving verbal feedback
- prompting the quieter people so that nobody dominates the discussion
- Collect feedback in a format you can share. This could be Trello.
- Share feedback and next steps to the wider group while allowing people to give more – not everyone will be comfortable in the session.
One rule: be kind
Sharing work and opening it up to criticism can be a terrifying prospect. Here are a few ways we can make it less daunting and much more productive for everyone.
When sharing your work you must remember the golden rule: you are not your design.
When critiquing work remember to:
Listen. Then speak thoughtfully.
Crits should be a safe space for everyone to share their thoughts. Listen carefully. If you want to respond, consider whether your thoughts are relevant or whether they’ll progress the discussion.
Rather than stating “X is bad” or “Y doesn’t make sense”, ask questions about the reason behind a design decision. Yes, “what’s the reason for…” is kinder than “that’s rubbish”, but it’s also more useful for the session – if you were wondering about something, chances are the rest of the group are too.
State what’s fact, opinion or assumptions
Everything you say in a crit is your point of view but it’s worth clarifying if something is your personal preference or opinion, or whether it’s backed up by research. “My assumption is that…” is just as valuable in a crit than “user research shows that…”. Both are better than “that should be green/bigger/bolder.”
How do you do it?
Designing collaboratively and in the open is important and design crits help us do that. There’s no set method but this is one that has worked for me and teams I’ve worked with.
Do you place importance on critiques and design reviews in your organisation? How do they work? All crit-related tips and tricks are welcome in the comments.
Lead interaction designer