Design Team Retrospective

Reflect, refine, and elevate your design team's craft.

Use this template in TeamRetro

Design Wins

Which design decisions or outcomes are we proud of?

The new onboarding flow tested really well—users completed signup 40% faster.
Loved how quickly we aligned on the design system tokens this sprint.
Our research readout actually changed the product direction—huge win for UX.
Friction Points

Where did our design process or collaboration slow down?

Feedback came too late in the cycle, forcing last-minute rework.
Requirements kept shifting after we'd already locked the designs.
Our review meetings ran long and rarely ended with clear decisions.
Craft & Quality

How can we raise the bar on our design craft?

We should run regular design critiques to keep quality high.
Accessibility needs to be part of our definition of done, not an afterthought.
Our design system is drifting—components need an audit and cleanup.
Ideas & Experiments

What should we try to improve how we work?

Try a weekly async design review using shared prototypes.
Introduce a shared component library checklist before handoff.
Run a monthly portfolio-style share to celebrate and learn from work.

What is the Design Team Retrospective

Great design isn't just about pixels and prototypes—it's about how a team collaborates, critiques, and continuously improves the way they create. The Design Team Retrospective gives designers, researchers, and design leads a dedicated space to step back from the daily flow of work and reflect on what's shaping their craft, their process, and their working relationships. Rather than focusing purely on delivery metrics, this format invites the team to consider the quality of design outcomes, the health of their feedback culture, and the systems that support (or hinder) creative work. Running this retrospective in TeamRetro is simple and inclusive. Each team member contributes their reflections across focused themes—celebrating strong design decisions, surfacing friction in handoffs and reviews, and uncovering opportunities to refine the design system and tooling. Grouping, voting, and discussion features make it easy to move from scattered observations to shared insights, and from insights to clear, ownable actions. Anonymous input ensures even quieter voices and constructive critiques are heard. The goal is continuous improvement of both the design product and the design practice. Whether you're a product design team inside an agile squad, a brand studio, or a UX research group, this retrospective helps you align on craft standards, smooth cross-functional collaboration with engineering and product, and build a healthier creative environment. Use it at the end of a design sprint, after a major launch, or on a regular cadence to keep your design team learning and growing together.

Design Team Retrospective format

Design Wins

Which design decisions or outcomes are we proud of?

This topic celebrates strong design work and effective collaboration. Encourage the team to call out specific design decisions, polished interactions, research insights, or moments where craft really shone. Recognising wins reinforces good practices and builds creative confidence—prompt people to name what made the win possible so it can be repeated.

Friction Points

Where did our design process or collaboration slow down?

Use this space to surface blockers, bottlenecks, and frustrations in the design workflow—unclear requirements, late feedback, tooling pain, or rushed reviews. Keep the tone constructive and focused on the process rather than individuals. Group related themes to identify systemic issues worth addressing.

Craft & Quality

How can we raise the bar on our design craft?

Focus this topic on the quality of design outcomes and consistency across the team—visual polish, interaction details, accessibility, and adherence to the design system. Encourage reflection on standards, critique culture, and where craft could be elevated. This keeps the team aspirational about the work itself, not just the process.

Ideas & Experiments

What should we try to improve how we work?

This forward-looking topic invites the team to propose new ways of working, tools to trial, rituals to adopt, or collaboration improvements. Encourage concrete, testable ideas the team can commit to as actions. Use voting to prioritise the experiments with the most potential impact.

When to use this retrospective

  • At the end of a design sprint or major project to review what worked and what didn't in the design process.
  • After a significant product launch or release to capture lessons about craft, collaboration, and handoffs.
  • On a regular cadence to maintain a healthy critique culture and keep raising design quality.
  • When cross-functional friction with engineering or product is affecting design outcomes.
  • When onboarding new designers or evolving your design system and want shared alignment on standards.

Suggested icebreaker questions

  • If your design style were a font, which one would it be and why?
  • What's one piece of design—an app, poster, or product—that's caught your eye recently?

Ideas and tips for your retrospective meeting

  • Frame critique around the work, not the person—keep feedback specific, kind, and actionable to protect a healthy creative culture.
  • Use anonymous input so quieter designers and constructive criticisms surface without fear of stepping on toes.
  • Invite cross-functional partners like engineers and PMs occasionally to address handoff and collaboration friction directly.
  • Timebox each topic and use voting to focus discussion on the highest-impact themes rather than every comment.
  • Always close with clear, owned action items and revisit them at the start of the next retro to build accountability.
  • Balance celebrating design wins with surfacing problems so the session feels motivating, not just critical.

Frequently asked questions

What is a Design Team Retrospective?
It's a structured reflection where designers review their recent work, process, and collaboration to celebrate wins, surface friction, and agree on improvements. It focuses on both design craft and how the team works together.
When should we run a Design Team Retrospective?
Run it at the end of a design sprint, after a major launch, or on a regular cadence such as every two to four weeks. It's also valuable when cross-functional friction or quality concerns start affecting your work.
How long does a Design Team Retrospective take?
Most sessions run 45 to 60 minutes for a typical design team. Larger groups or particularly eventful sprints may need up to 90 minutes to discuss and prioritise actions.
How is it different from a sprint retrospective?
A sprint retrospective focuses broadly on agile delivery, while a Design Team Retrospective centers on design craft, critique culture, design systems, and creative collaboration. It's tailored to the unique needs of designers and UX practitioners.
Who should take part in a Design Team Retrospective?
All members of the design team—product designers, UX researchers, content designers, and design leads—should join. Occasionally inviting engineering or product partners can help resolve handoff and collaboration issues.
How do we make sure actions actually happen?
Capture clear, owned action items at the end of each session and assign them to specific people. Review progress at the start of the next retrospective to build accountability and momentum.

New to retrospectives? Read our guide on how to run a retrospective →

Related templates

Working, Not Working Retrospective

A clear-cut way to identify successes and improvement areas

Quarterly Retrospective

Reflect, realign, and recharge your team every quarter.

SCOR Futurespective

Strategic planning framework to analyze future scenarios and prepare for what's ahead

Marketing Team Retrospective

Reflect, refine, and amplify your marketing campaigns together.