A design review is only as good as its facilitation. Without structure, reviews devolve into rambling discussions where the loudest voice wins. With thoughtful facilitation, they become one of the most productive hours on your team's calendar. This lesson covers the practical mechanics of running reviews that consistently produce useful outcomes.
Setting an Agenda
Every design review should have a written agenda shared in advance. The agenda sets expectations and allows participants to prepare.
Agenda template for a 60-minute design review:
- Welcome and ground rules (3 minutes) — Briefly remind the group of critique norms, especially if the team is new to structured reviews.
- Presenter 1: Context and goals (5 minutes) — The designer explains the problem, constraints, and what specific feedback they need.
- Presenter 1: Walkthrough (5 minutes) — The designer shows their work without interruption.
- Presenter 1: Discussion (10 minutes) — The group provides critique following the structured format.
- Presenter 2 (repeat format) — If multiple projects are being reviewed.
- Wrap-up and action items (5 minutes) — Summarize key takeaways and next steps.
Practical tip: Share the agenda with all participants at least 24 hours before the review. If possible, include screenshots or prototype links so people can preview the work. Cold reviews — where people see work for the first time in the meeting — produce lower-quality feedback because participants need time to process.
Timeboxing
Timeboxing is the single most important facilitation technique for design reviews. Without it, the first project takes 80% of the time and everything else is rushed.
How to timebox effectively:
- Assign a specific duration to each project before the meeting
- Use a visible timer — a phone timer on the table or a shared screen timer for remote reviews
- Give a 2-minute warning before each section ends
- When time expires, capture remaining thoughts as written notes to be shared asynchronously
Practical tip: It is better to end a discussion early with clear next steps than to extend it and sacrifice time for other presenters. The note-taker can capture unresolved questions for follow-up.
Roles in a Design Review
Assigning explicit roles prevents the common failure modes of design reviews: one person dominating, no one taking notes, and the conversation going off track.
Essential roles:
- Facilitator — Manages time, enforces ground rules, ensures everyone participates, and redirects off-topic discussions. The facilitator should not also be presenting their own work in the same session.
- Presenter — Shares their work, states goals, and asks for specific feedback. During the discussion phase, they mostly listen and ask clarifying questions rather than defending decisions.
- Critics — The rest of the group. Their job is to provide structured feedback connected to the stated goals. Everyone in this role should contribute — the facilitator can directly invite quiet participants.
- Note-taker — Records key feedback points, decisions, and action items. Without notes, valuable insights are lost within hours. Rotate this role so the same person is not always stuck typing.
Practical tip: For teams new to critique, the facilitator should model good feedback by going first. This sets the tone and demonstrates what kind of comments are expected.
Managing Common Problems
Even well-structured reviews encounter challenges. Here is how to handle the most common ones:
The dominator — One person talks too much. The facilitator should say "Thank you, Alex — let's hear from someone who hasn't spoken yet." Alternatively, use a round-robin format where each person gives one piece of feedback in turn.
The tangent — Discussion drifts to unrelated topics like technical implementation or business strategy. The facilitator should note the topic on a "parking lot" list and redirect: "That's an important point — let's capture it for a separate discussion and stay focused on the design."
The solution jump — Someone immediately proposes a specific solution instead of first identifying the problem. Redirect by asking "What problem does that solve?" to bring the conversation back to diagnosis before prescription.
The silent room — No one wants to go first. The facilitator can break the ice by starting with a specific question: "Looking at the onboarding flow, does the sequence of steps feel intuitive?" Specific prompts are easier to respond to than "Any thoughts?"
Remote Design Review Tips
Remote reviews require extra intentionality to work well:
- Use screen sharing with annotation tools — Figma's observation mode lets everyone follow along. Use cursor-based pointing or comment pins to reference specific elements.
- Use a structured format strictly — Remote conversations have more interruption and crosstalk. The round-robin approach works especially well.
- Keep cameras on — Non-verbal cues are important for gauging reactions and maintaining engagement.
- Use chat for quick reactions — Encourage participants to drop observations in chat while someone else is speaking, then the facilitator can pull from chat during discussion.
- Record the session — For distributed teams across time zones, recording allows absent members to watch and add async feedback.
Practical tip: For remote reviews, have the presenter walk through the design in Figma rather than sharing a static slide deck. Figma allows the audience to zoom in, inspect details, and look around on their own.
Key Takeaways
- Always share an agenda and preview materials before the review
- Timebox every section and enforce it — use a visible timer
- Assign roles: facilitator, presenter, critics, and note-taker
- Address dominant voices, tangents, and silence with specific facilitation techniques
- Remote reviews need extra structure — use round-robin, annotations, and chat