DESIGN CRITIQUE GUIDE
When solving complex problems, setting the stage for the problem can be time-consuming.
It can be challenging for people working on completely different parts of the product to dive into another meeting once per week and provide useful feedback.
Keeping crits focused, useful, and on time. As the teams get bigger, the rooms fill up. In growing teams critique meetings have become too large and a bit unmanageable especially if ran on Zoom.
Confusions around expectations in critiques vs reviews meetings. There was the perception that critique is for review and approval. "You attend a critique session to get approval on your designs."
Yet this became really stressful for some people because many of them were unsure if they'll do good. As a result the barrier was high to entry and critiques became intimidating, for people to speak up.
Feedback can be subjective and not specific enough. Constraints were getting lost in translation when communicating remotely.
It is very helpful to set the boundaries for the feedback you're looking for. Keeping critiques focused within scope so that you get the right feedback you are looking for.
Si Min shares her thought process and the critique format that they use at Zendesk to keep the sessions focused.
What is the problem you are solving? What are the challenges you are facing?
What specific types of feedback are you looking for? e.g. "I'm only looking for feedback around the flow and approach taken." (Or it can be regarding the interaction or visual design)
What feedback are you NOT looking for? This helps the feedback stay focused within scope and brings people back if the conversation goes off-topic. e.g. "Let’s document this feedback for reference later. The focus for today is not on the visual design."
Do you want feedback during or after the presentation? Do you want written feedback? e.g. "I would like feedback after my presentation. If you have any questions along the way, please jot them down in this board."
The framework used by design teams at Zendesk to set expectations in a critique session
When solving complex problems, setting the stage for that problem can be time-consuming. It can be challenging for people working on completely different parts of the product to dive into another meeting once per week and provide useful feedback.
To frame the problems clearly we use starter statements like the following to introduce the problem.
I am solving this problem for...
I am at a stage at...
These are the steps that I took...
I am looking for feedback in...
At LinkedIn we use a sign up based system to understand who is presenting what.
As designers go through the critique, they make sure they mention what stage is the design currently. We use the Discover-Design framework based on the double diamond design process.
Critiques bring early stage work, even napkin sketches to get feedback on work in progress as early as possible.
Crits are usually more informal, no prior preparation is required. It’s less of a presentation and a more focused on discussion.
Unblocking challenges
Work at any stage can be presented
Informal, no prior preparation
Happens as early and often as possible
Critiques are usually done with the design team.
Reviews tend to be more formal, scheduled in advance with a larger cross-functional team, and be proposals in a presentation format.
In most companies, reviews tend to happen later in the design process when designs are more fleshed out. However, if sign off on high-level direction is needed from leadership reviews can (and should) happen earlier in the process.
Getting sign off / approvals
More fleshed out designs can be presented
High-level direction, presentation format
Happens later in the design process
Reviews involve cross-functional stakeholders and the leadership team/ decision makers.
There are four main questions to ask to help in the decision process:
Does the design proposed solve our user problem?
Is the design missing a step in the workflow?
Are the steps in the workflow too complex?
Did you make correct assumptions about what the user needs to see?
Acknowledging there is a debate and that the room is split or most folks are leaning in one direction.
Create space for the designer to reflect on the input outside the meeting.
Acknowledging the difference between subjective and objective feedback.
Capture the feedback as an action item. The members with conflicting feedback could meet async to discuss.
Sometimes you may need to bring up scope limitations to close a loop on a conversation.
Hearing both sides of the argument and trying to understand how does that contribute to user goals.
Reiterate “what type of feedback are you looking for” or “is this more like a share-out."
Clarify with the designer "what you're asking for is..."
"A great design critique is a meeting in which the designer who presented got the help they needed to move their work forward."
"One aspect of a great design critique is getting to the problem as soon as possible. You have a room full of experts at your disposal. Get their brains working for you as soon as you can. Also inviting people who have context on the problem but haven’t been thinking about the problem all day helps provide a fresh perspective."
"Designers feel safe to challenge, question and filter through the feedback received. Also, everyone in the room feels empowered to bring any level of design ideas/concepts to the critique."
"A great design critique it’s fun. It’s energizing. It’s full of spirited debate with diverse perspectives. It’s about creating a level of comfort between everyone on the team. Its about candid conversations. It’s about feedback that comes from a place of care and investment in the work we do as a team."
"Openness, the person being critiqued feeling comfortable and not threatened/intimidated, direct constructive feedback, not holding any punches but giving feedback with tact."
"Honest, straight-forward critique in a setting where the designers feel trust and supported by their fellow designers. The designer who presented feels unblocked and feels the feedback was helpful and actionable."
"A good set up, participation, and covering all aspects of design: how the proposed design solves the problem, design patterns and compliance with design system and accessibility."
"Provide context before sharing - share clarity on the problem you're trying to solve, any previous solutions that didn't work, set the stage for specific feedback. Don't ever ask "What do you think?" It's too broad."
GRATITUDE
Deepest thanks to the following people who graciously offered feedback and support while working on the Design Critique Guide. Additionally many thanks to the 200+ people who shared their learnings and filled out our survey.
