Critique Facilitator

A critique facilitator is the referee who keeps design critiques from devolving into performance art or senior designer dominance hour. This person enforces whichever framework the team selected for that session. For early direction they run I Like I Wish What If. For mid fidelity they use Goal Rationale Feedback. For pre ship they deploy the Decision Stack. They start by having the designer declare the exact goal and the scope of desired feedback. From there they ride herd on the three layer feedback model. Every comment must begin with observation. The CTA sits below the fold on mobile. Only then does interpretation follow. That placement means users never see it. Only then comes suggestion. Move it up or make it sticky. They shut down vague statements force specificity and park anything off scope for a later session. They own the clock. They own the focus. They own the capture. No side conversations. No prescriptions without observations. Notes get taken in real time by someone other than the designer and shared immediately after in tools like Notion or Coda. The facilitator makes sure the meeting ends with a stated outcome that everyone agrees on before moving to the next piece of work. They rotate this role every sprint so the skill spreads across the team including to junior designers who gain more from running the meeting than from simply receiving feedback.

This is not the job of the most senior person in the room. Seniors often make the worst facilitators because they cannot resist jumping in with their hot takes on every screen. It is not a passive note taking position although capture matters. The real work is active redirection when the conversation drifts to taste or when someone offers a fix before stating what they observed. The facilitator is not there to critique the work while the meeting runs. They hold their opinions until the structure finishes if they offer any at all. It is not a permanent title or a power move. Teams that assign it to the design lead forever create a bottleneck and rob everyone else of growth. It is not optional theater. Skip it and your frameworks die within two meetings turning them back into the exhausting sessions nobody learns from.

Concrete proof comes from several teams that installed this role in the last few years. At Stripe in early 2023 critiques felt like theater. Work shipped with the same flaws week after week because no one captured decisions and feedback stayed too high level. They introduced a rotating facilitator drawn from the full team of 12 designers. During one session focused on the payments dashboard a junior facilitator named Priya managed a review of an AI generated layout option created with Midjourney the night before. The presenting designer had used it to explore options in minutes. A product manager started firing suggestions without context. Priya reminded everyone of the no prescriptions without observation rule from the three layer model. The PM stated the observation that the generated cards had inconsistent spacing that broke the visual hierarchy. That led to an interpretation about trust signals in financial interfaces where consistency builds confidence. The team landed on a specific test plan for the next iteration. Priya cut the session at 20 minutes sharp and the notes appeared in their shared Coda page before lunch with clear action items assigned. The updated version tested 18 percent better with users two weeks later. Another example comes from Webflow in 2024. Their cross functional critiques included engineers who often derailed discussions with implementation concerns too early in the process. A rotating facilitator kept those conversations in sequence using the Decision Stack framework. One facilitator caught a senior visual designer giving feedback dressed as principle when it was really personal taste on typography choices. She asked him to reframe it as observation first. The team avoided 40 minutes of circular debate and focused on the actual goal the designer had stated. Before these changes both teams reported dreading critique meetings and skipping them when possible. After rotation became standard the meetings became the most valuable 60 minutes of the week and the overall quality of shipped interfaces improved noticeably. The opposite happened at a fintech called Ramp in 2021 where the head of design hoarded the facilitator role. Critiques became his personal platform for opinions. No notes were taken. Designers learned to bring only polished work to avoid embarrassment. Innovation died and projects took 30 percent longer. Installing the role and rotating it fixed the pattern in one quarter.

Use the critique facilitator in every formal review that follows a framework especially when the group mixes disciplines or includes senior voices that tend to dominate. That includes the three required critique points per project from direction where you test if you are solving the right problem all the way to pre ship where you pressure test recommendations against risks. It becomes essential with AI generated work in 2025 and beyond because those outputs require extra human accountability to avoid shipping generic or broken designs. Remote teams need facilitators even more to synthesize async comments in Figma Loom videos or shared documents before they become a mess of unconnected threads that no one acts on. Do not bother with the role during casual peer feedback or exploratory brainstorms where the goal is generation not refinement. Avoid it if your team is smaller than four people and already shares a tight vocabulary from years of working together. Never let someone facilitate if they play favorites or cannot stay neutral because they will break trust and the whole system collapses. The role fails when the facilitator starts protecting certain designers or pushing their own agenda instead of protecting the process.

The critique facilitator turns chaotic design reviews into reliable engines of improvement that make the whole team better.