As Frontline Education’s design team grew to 12 designers, our existing critique rituals struggled to scale. Most designers were embedded as the sole designer on individual product teams, often working in unfamiliar domains from one another. As a result, critique sessions required heavy context-setting, participation was uneven, and feedback quality varied — directly impacting our ability to validate design decisions and maintain quality standards across products.
I partnered with a UX Researcher who joined the team around the same time I did to rethink how critique could better support collaboration, learning, and design quality as the team scaled. As newer hires, we were encouraged by our manager to bring a fresh perspective to a long-standing team ritual.
The Problem
The existing critique format wasn’t consistently serving designers or improving design outcomes. Presenters hesitated to share early work, leading to late-stage feedback when changes were costly. Critics lacked sufficient domain context to give useful, actionable feedback. The large group size limited participation depth and individual contribution. Sessions often drifted into problem-solving or unfocused discussion rather than structured critique.
These dynamics made critique feel high-stakes with unpredictable outcomes. They prevented critique from serving its core purpose: improving design quality through collaborative review.
Applying Design Thinking to Team Process
I approached this challenge using the same user-centered methodology I apply to product design.
Empathize. I surveyed all 12 designers to understand critique pain points, fears, and needs. I conducted follow-up conversations to dig deeper into specific challenges around context-setting, psychological safety, and feedback quality.
Define. The core problem wasn’t the format itself, but creating conditions for useful feedback when context was limited and stakes felt high. Critique needed to scale alongside team growth while supporting designers working in isolated domains.
Ideate. I researched critique best practices from design leaders and organizations and drew from prior experiences on different design teams. I explored multiple formats including smaller breakout groups, asynchronous critique, and structured facilitation models.
Prototype. I designed a new critique structure with defined roles, ground rules, prep templates, and smaller group sizes. I piloted the approach by facilitating one group while my research partner facilitated the other in parallel — which let us test consistency, compare notes, share learnings, and support each other through challenges.
Test. After 12 weeks, we conducted a follow-up survey and iterated on prep templates, facilitation techniques, and ground rules based on what was working and what needed refinement.
Key Design Decisions
Smaller groups, parallel sessions. Splitting the 12-person team into two groups of 6 increased individual participation, reduced context-switching fatigue, and created space for deeper discussion. Critics could engage more meaningfully when they weren’t competing for airtime with 10 other people.
Defined roles and responsibilities. Establishing clear roles — facilitator, presenter, critics — with explicit responsibilities reduced ambiguity about what was expected and helped less experienced designers participate more confidently. Facilitators actively managed time, kept discussion focused, and intervened when feedback drifted off-topic.
Structured prep template. A lightweight template asked presenters to frame the problem, goals, constraints, and specific questions for critics. This shifted cognitive load from the critique session itself to async preparation, allowing presenters to be more intentional about what feedback they needed and giving critics essential context upfront.
Ground rules for constructive feedback. Codifying shared expectations — feedback should be objective, user-focused, specific, and aligned to the presenter’s stated goals — gave both presenters and critics a shared vocabulary. It reduced anxiety around receiving critique by making expectations explicit.
Support for earlier sharing. Explicitly encouraging informal, early-stage critiques outside the formal session structure normalized sharing unpolished work and reduced the pressure for “ta-da” presentations that were too far along to meaningfully change.
Outcomes
- Over half of the design team reported improved feedback quality in the post-implementation survey
- A marked increase in early-stage work sharing during critique sessions over six months
- Increased participation across experience levels, with junior designers contributing more actively
- Clearer takeaways and next steps after each session, improving follow-through on feedback
- Dramatic reduction in cancellations and overall more engagement during critiques
Qualitatively, designers reported feeling more comfortable sharing work earlier in the design process and more confident both giving and receiving feedback across unfamiliar domains.
Tradeoffs
Not every improvement was immediate or universal. Designers varied in how consistently they used the prep template, especially under time pressure — we optimized for flexibility over strict enforcement to avoid turning critique into overhead. Context still mattered: even with stronger framing, some domain-heavy work required deeper background than critique time allowed. And the quality of critique remained highly dependent on active and engaged facilitators, which required rotating the facilitation role to avoid burnout.
Shifting critique habits — especially around sharing earlier work and structuring feedback around goals rather than preferences — required repetition and reinforcement beyond a single rollout. We maintained momentum through consistent facilitation, celebrating examples of effective critique, and favoring natural conversations over textbook perfection.
Why This Matters
This work improved design quality not by adding process, but by designing better collaboration systems. It helped the team scale critique alongside team growth without losing effectiveness, support designers working in siloed or specialized domains, and make critique a reliable tool for decision-making rather than a box-checking exercise.
For me, as the team’s newest designer, I saw an opportunity to revitalize Frontline’s design critique practice by introducing principles I’d learned at Center Centre and during my residency at Abstract. My goal was to make critique feel less like a test and more like design hygiene — a routine practice that improves your work and feels good to do.