Loading…
Loading…
Leading structured critique sessions where teams evaluate and improve design work.
stellae.design
Facilitating Design Reviews is the practice of running structured sessions where designs are presented, discussed, and refined through peer and stakeholder feedback. Effective design reviews improve quality, catch issues early, share knowledge across the team, and build alignment. They require clear structure: context setting (what problem does this solve?), presentation (design walkthrough), feedback (structured critique), and action items (what changes and who owns them). The facilitator manages the conversation to keep it productive and prevent it from devolving into subjective opinion battles.
Design reviews are the critical checkpoint where individual design decisions are evaluated against user needs, business goals, and technical feasibility — and the quality of the facilitation determines whether the session produces actionable improvements or devolves into subjective opinion battles. A well-facilitated review creates psychological safety that encourages honest critique, surfaces blind spots the designer could not see alone, and aligns the team on a shared understanding of what good looks like for the specific problem being solved. Poorly run reviews waste everyone's time, demoralize designers who feel attacked rather than supported, and allow fundamental usability issues to ship because no one felt comfortable raising them.
Spotify's design teams use a structured critique framework where the presenter states the problem, the constraints, and the specific feedback type requested (directional, detail, or stress-test), and reviewers organize their comments into those categories. This structure prevents the session from wandering into tangential discussions and ensures that the most impactful feedback — whether the design solves the stated problem — always gets addressed first. The framework is lightweight enough to use in fifteen-minute sessions, making reviews frequent and low-stakes rather than rare and high-pressure.
Google Ventures popularized a feedback framework where reviewers structure comments as 'I like' (what is working), 'I wish' (what could improve), and 'What if' (generative suggestions), ensuring that every critique session balances validation with constructive challenge. The format forces reviewers to acknowledge strengths before identifying weaknesses, which maintains the presenter's confidence and keeps the tone collaborative. It also surfaces creative alternatives through the 'What if' prompt that pure critique formats tend to miss.
A team holds a design review with no agenda, no stated objectives, and no facilitation, allowing the most senior stakeholder to dominate the conversation with subjective preferences about visual style that have nothing to do with the design's effectiveness for users. Junior designers stay silent because the social dynamic discourages dissent, and a critical usability issue in the checkout flow goes unmentioned. The design ships with the executive's preferred color scheme but a broken user journey, and the team learns to treat reviews as approval ceremonies rather than genuine quality checkpoints.
• The most damaging mistake is allowing design reviews to become approval gates controlled by stakeholder preference rather than collaborative sessions focused on user outcomes and design principles. Teams also commonly skip the framing step — jumping straight into showing screens without establishing what problem the design solves or what kind of feedback is most useful — which invites unfocused commentary on surface aesthetics. Another frequent failure is not designating a facilitator, which allows dominant personalities to steer the conversation, silences introverted team members who often have the most thoughtful observations, and lets the session run over time without reaching actionable conclusions.
Was this article helpful?