Crit Culture

So why Crit?

Why do we crit? As designers, our work is rarely a subjective response to an emotion (aka art). Our designs are (more often than not) grounded in problem-solving, system thinking, and collaboration. Crit is, therefore, a useful tool to proactively seek feedback from peers to leverage their strengths, expertise, and different points of view to make your design solution better. Crit also serves as a place to share so others can learn.

What to share

Crit shouldn’t be a formal review; what you share in a crit shouldn’t be finished work. Think of crit as a low-pressure space to share WIP designs with your peers. Some of the best crits I’ve been in (and shared in) are informal, low fidelity, and collaborative.

• Share early thoughts
• Share low fidelity work in progress
• Share the breadth of your ideas and iterations
• Share a problem you’re stuck on

How to share

How you share is just as important as what you share. It helps get to the heart of the most meaningful feedback sooner. It can be daunting at first (I’ve had my fair share of crit-fails), but I’ve learned a few tricks over the years that help make the most out of sharing work in crit.

• Set the stage (don’t jump straight into pixels)
• Frame the problem you’re trying to solve
• Share where the project is at (start, middle, end)
• State the type of feedback you’re looking for

What to ask for

It’s important to state the type of feedback you’re looking for clearly so that people share meaningful thoughts rather than subjective or off-topic comments. What to ask is often dependant on where you are in the life-cycle of a project, though. If you’re starting, you might ask for more high-level feedback such as:

• Is this the right problem to solve?
• Conceptually, which direction is most correct?
• Given the problem, what process is more ideal?

If the project is in its latter stages, then you might ask for more detailed feedback such as:

• What type of interaction pattern is best?
• Am I using the design system correctly?
• Does the visual design communicate accurately?

Additionally, you might also want to engage subject-matter-experts when it comes to Content Strategy, UX Research, Data Science, or even those in a more Senior position who can help connect the dots or unblock the project.

How to give feedback

On the flip side, when you’re a participant in a crit (someone who is giving feedback to the person sharing their design), it’s essential to learn how to give feedback. I can’t tell you how many crit’s I’ve been in where I’ve received misdirected or poorly stated feedback (both ill-intended and intentional). Giving feedback is a skill unto its own, even outside of crit, and something that takes time and practice to master.

• Critique the work, not the individual
• Ask questions to validate the designer’s intention
• Be supportive as crit can often be a vulnerable space
• Ensure others get a chance to give feedback

Who should attend crit

It’s often thought that crit is just for Designers. While that’s true for the most part, crit can also be a place for other team members to attend (especially those who are working on the same project) so they can participate in dialogue, listen to the feedback given, and understand more about how design works and the design process.

Developing a culture of critique

Developing a critique culture doesn’t have to be a vast undertaking, nor does it need to be formalized. If you’re starting out, small things like sharing WIP in a Slack channel or opening up your Figma designs to your team can go along way. In small teams, seeking feedback often regardless of the channel will develop a natural culture of critique. In larger teams where designers need to share their work with other designers for visibility and insight-gathering, having a regular slot on the calendar each week will help develop a cadence of sharing and forge a more robust critique culture.

Crit playbook

1. Set the stage (come prepared, frame the problem and the type of feedback you want)
2. Keep it in low fidelity (no need to present a Keynote)
3. Designate a crit facilitator to take notes (and take turns each week)
4. Be present (no laptops, listen)
5. Critique the work, not the person (and don’t take it personally)
6. Engage in dialogue and ask questions (refrain from subjective comments)
7. Be a hero (take feedback, be action-orientated)
8. Depressurize the space (Crit is a safe place to be vulnerable)