Design Team Retrospective

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. Recognizing 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, such as 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 the design work and how consistent it is across the team: visual polish, interaction details, accessibility and use of the design system. Ask the team to reflect on standards, how critique works and where the craft could improve. This keeps attention on 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 prioritize 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 in the design process and what didn't.
• After a big launch, to capture lessons about craft, handoffs and collaboration.
• On a regular cadence, to keep critique healthy and keep raising design quality.
• When friction with engineering or product is hurting design outcomes.
• When you're onboarding new designers or changing your design system and need agreement 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?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

• Critique the work, not the person. Specific, kind feedback keeps the creative culture healthy.
• Use anonymous input so quieter designers can raise criticism without worrying about stepping on toes.
• Invite engineers and PMs now and then to deal with handoff friction directly.
• Timebox each topic and vote, so the discussion goes to the biggest themes instead of every comment.
• Close with clear actions that someone owns, and review them at the start of the next retro.
• Give design wins as much time as problems so the session doesn't feel like a list of complaints.

Frequently asked questions