Stop Brainstorming During Design Critiques: A Facilitator's Guide

The Trap of the Accidental Brainstorm

Imagine watching a brilliant design concept get ripped apart, not because it is fundamentally flawed, but because six different stakeholders suddenly decided it was time to brainstorm. This happens every day in product teams. A session is billed as a "design critique," but within ten minutes, it morphs into an unguided ideation workshop.

When design teams or cross-functional groups gather to review work, they rarely have an organized way to analyze it. Without structure, human nature takes over. Instead of evaluating the work against its goals, people start throwing out new ideas and alternative solutions.

This is how you end up with watered-down, design-by-committee products. As Aarron Walter from the Design Better podcast points out, feedback is the lifeblood of a healthy team. Yet, in most tech companies, it is practiced poorly or not at all.

A critique culture doesn't just produce better designs; it produces better designers.

To build that culture, you need to step into your role as a facilitator and change the rules of engagement.

The Golden Rule: Separate Critique from Ideation

The single most effective change you can make to your critique sessions is drawing a hard line between giving feedback and generating ideas. Ideation has no place in a design critique.

When participants start brainstorming, they divert attention from the actual design under consideration. The focus shifts from "Does this solve the user's problem?" to "What if we tried this completely different approach?" This robs the designer of the opportunity to understand the impact of their specific decisions.

Critique should be focused purely on structured analysis. Your job as a facilitator is to guide the room in describing what parts work, what parts do not, and why. If a new idea pops up, park it in a "parking lot" document and gently steer the group back to the analysis at hand.

Setting the Stage with Context

A critique cannot succeed if the room does not understand what they are evaluating. You cannot judge a solution if you do not know the problem.

Before any feedback is given, the presenter must set the foundation. This means explicitly defining the goals, the underlying design principles, the target personas, and the specific scenarios the user is facing. This context acts as the measuring stick for all feedback.

If a piece of feedback does not relate back to these established goals or personas, it is simply a personal preference. As a facilitator, you can use this context to filter out unhelpful subjective opinions.

Tactics for the Room: Rules and Rhythms

Running a smooth critique requires strong ground rules. Without them, the loudest voice in the room will dominate the session, and quieter experts will keep their insights to themselves.

The "No Piling On" Rule

Andrew Bosworth's famous "P-rules" offer a fantastic guideline for critiques: No piling on. Feedback in a design critique does not have weight based on how many people say it. If one person points out a flaw in the navigation, the next three people do not need to repeat it.

Prioritization is ultimately left to the designer. Repeating the same feedback wastes time and can make the designer feel attacked rather than supported.

The Round-Robin Method

To ensure everyone has a voice, borrow a technique championed by design leader Sarah Gibbons: the round-robin. After the designer presents their work, enforce a few minutes of silent reflection. Then, go around the room systematically.

Each person shares their single most important piece of feedback. This prevents extroverts from hijacking the meeting and ensures you get a diverse range of perspectives.

Borrowing from Figma's Playbook

You do not have to run every critique the exact same way. In fact, relying solely on the standard "everyone in a room looking at a screen" format can lead to fatigue.

Look at how Noah Levin structured design critiques at Figma. He realized that different stages of design require different types of feedback. His team utilizes a variety of formats to keep things fresh and effective.

They use "silent critiques" where the team leaves comments on a file without speaking, "pair design" for rapid feedback between two people, and asynchronous "FYI" reviews for minor updates. Matching the format to the specific need of the design dramatically increases the quality of the feedback.

Structuring Your Next Session

Changing your team's critique culture won't happen overnight, but it starts with how you design your next meeting agenda. You need distinct blocks for context-setting, silent reflection, and structured sharing.

If you need a reliable way to build these structured agendas without starting from scratch, metodic.io helps you map out the exact flow of your sessions. By deliberately designing the meeting structure, you ensure that you never accidentally mix an ideation exercise into a feedback block again.

Actionable Takeaways for Your Next Critique

• Ban brainstorming: State clearly at the beginning of the meeting that the goal is analysis, not ideation.
• Demand context: Never start a review without the presenter defining the user persona, the scenario, and the business goal.
• Enforce silent reflection: Give participants 3-5 minutes to write down their thoughts before anyone speaks. This prevents groupthink.
• Stop the pile-on: If someone repeats a point already made, acknowledge it quickly and ask for net-new feedback.

By taking control of the structure, you stop being a passive meeting host and become a true facilitator. You will protect the designer's time, elevate the team's shared understanding of quality, and ultimately build better products.