Comma, Not a Bow

Comma, Not a Bow

Why this matters

Safety gets the work in the room early. The takeaways question makes sure the feedback leaves with somewhere to go.

TITLE
Comma, Not a Bow
AUTHOR
Leonardo De La Rocha
PUBLISHED
May 29, 2026
CATEGORY
State of the Craft
READ TIME
3 min read
ISSUE
08
LISTEN
[▶ PLAY]
******************************************************************************************

Two small moves that decide whether crit feedback actually changes the work.

I‘ve changed how we close design crits. Instead of letting the discussion wind down and wrapping up, I ask the presenter a question at the end: what are your takeaways, and what are you going to do with this feedback? The job of summarizing shifts to the person who has to act on it, out loud, in front of the room.

One of my designers watched a colleague close her own crit this way, saying she was going to go act on what she’d heard. Her read on it was the phrase I keep coming back to: that doesn’t put a bow at the end of the crit, it puts a comma. The conversation isn’t sealed shut. It’s continuing. The feedback was heard, it’s going somewhere, and it mattered.

The reason it works is accountability. Feedback that the recipient never restates tends to go in one ear and out the other. The act of summarizing it, even when they won’t take every note, shows the room their input was taken seriously. That single beat can make or break the relationship between the person giving feedback and the person getting it.

The other half is safety

Around the same time, one of my leads got specific praise for making it comfortable to be wrong in crits, especially for mid-level designers. He sets the conditions where someone will bring unfinished work into the room instead of polishing it in private until it feels bulletproof. That matters, because the common failure mode is perfectionism: people wait to share until the work can’t be criticized, which is exactly the point at which feedback is least useful.

The two moves are a pair. Comfort with being wrong gets the work into the room early, while it’s still cheap to change. The takeaways question makes sure the feedback leaves the room with somewhere to go. Safety on the front end, accountability on the back end. Miss either one and the crit turns into theater: either nobody brings real work, or everyone nods and nothing changes.

The teachable part

Both moves are free. No tooling, no process document. One is a question you ask at the end. The other is how you respond when someone is wrong in front of the group, which is the moment that quietly sets the price of being wrong for everyone watching. A crit isn’t a verdict you hand down. It’s the setup for the next revision, and your job is to make sure that revision actually happens.

Filed under SC State of the Craft — Monthly synthesis.