Closing the Loop: What to Do After a Design Critique Ends - NN/G

Skip to content

September Exclusive | Buy 2, Get 3rd Free on Live Online Courses

Enroll Today

Closing the Loop: What to Do After a Design Critique Ends

Rachel Krause

Rachel Krause

May 22, 2026

2026-05-22

Share

Email article

Share on LinkedIn

Share on Twitter

Summary:<br>Most designers invest in running critiques but skip the followup. That missing step is often why feedback culture breaks down.

Design critiques generate feedback. But feedback is valuable only if someone closes the loop on it: telling people what changed because of what they said, what didn’t change, and why. This article covers two concrete followup tactics, when to use them, and what you’re quietly risking every time you skip them.

In This Article:

Design Critiques Don’t End After the Session

How to Close the Loop

When to Follow Up

What Happens When You Skip Followups

Conclusion

Design Critiques Don’t End After the Session

A design critique is a workshop focused on analyzing a design and giving feedback on whether it meets its objectives. Its ultimate goal is to improve the design. Most teams spend their time and energy focused on planning and facilitating a design critique — choosing the right attendees, structuring the agenda, and facilitating the conversation. Then the session ends, and the feedback gets filed away in a document that nobody touches again.

This is one of the most common reasons critique culture quietly breaks down. Critique followups make feedback feel worth giving rather than a nice-to-have or a courtesy. When people contribute thoughtfully to a critique and never hear what happened to their input, they learn to stop contributing and show up unprepared to further sessions because they clearly don’t matter.

If your critiques feel pointless, the problem may not be your facilitation. It may be that your stakeholders don’t know what happened with their feedback.

Your design critique is over, but what about everything that came before?

Improve every step of the process with our self-paced course, Design Critiques.

What You'll Learn

How to Close the Loop

There are two types of followup communication:

Immediate post-session recap: Captures what was heard and what will happen next

Deeper followup after a design has evolved: Connects the changes that people see now to the conversation that helped shape them

The immediate recap doesn’t need to be long. A Slack or Teams message works well: “Here’s what we’re moving forward with, what we’re still investigating, and what we’ve decided not to pursue.” Be concerned about specificity rather than length.

The deeper followup is where trust actually gets built. It is usually a longer document or message and takes more effort, but it also showcases the value of design critiques and stakeholder feedback directly because they see the changes in real time.

Tactic: Show the Before and After

“Here’s the new version” shares the output. “This changed because you said that” closes the loop. When you share only the update, the people who gave feedback are left guessing: Did my comment land? Did it influence anything? Did the designer even remember it? Over time, that uncertainty erodes engagement. People stop showing up with careful observations because the feedback doesn’t seem to connect to anything.

Consider the scenario of a designer updating a dashboard design after a critique:

Poor followup: “Here’s the updated dashboard. We made some changes to the navigation and hierarchy.”

Strong followup: “We simplified the navigation after the group flagged that users couldn’t find their primary action. We also gave savings progress more visual weight, which came from our discussion about information hierarchy.”

The content of both updates is nearly identical, but the strong followup includes attribution. It connects the specific change to the specific feedback from the session. That’s what makes participants feel like contributors rather than an audience.

If you’re including a before-and-after visual, add an annotation with context. Don’t assume the comparison is self-explanatory. A sentence or two pointing to what changed and why gives people the context to engage with the image rather than scroll past it.

The two changes called out in the strong followup are both annotated in the image: a condensed navigation that surfaces the primary action, and a savings progress section with enough visual weight to get noticed by users.

Tactic: Acknowledge What You Didn’t Act On

Most designers default to reporting the wins: what changed, what improved, and what feedback they incorporated. This is understandable (we love winning!), but it creates a selective highlight reel that can quietly erode trust over time.

Stakeholders notice when their feedback wasn’t addressed. If no one explains why, they fill in the gaps themselves — usually with something like “they didn’t care” or “critiques are just a formality.”...