How to give design feedback that doesn’t get lost

Design feedback has a translation problem. You write “the spacing feels off near the header” and the designer reads it three times trying to picture which header, which spacing, and how off. Half of design feedback is just establishing what you’re both looking at.

A screen recording removes the translation step entirely: you point at the exact pixel and say what you mean. Here’s how to give feedback designers can act on.

Point, don’t describe

Open the design, start recording, and move your cursor to the thing you’re talking about as you talk. “This button” plus a cursor hovering the button beats a paragraph trying to name it. Ambiguity is what makes feedback rounds drag.

Say why, not just what

“Make it bigger” is a command; “this is the primary action, so it should pull more weight” is feedback. Narrating the reason lets the designer solve the actual problem — maybe the fix isn’t size at all.

Batch it into one pass

Walk the whole screen top to bottom in one recording instead of firing off ten separate comments. The designer gets your full thinking in order, and you avoid the death-by-a-thousand-threads that kills momentum.

Keep the link with the file

Because it’s a link, it lives next to the design forever — anyone joining later can watch the rationale instead of asking. Install ClipCast, record your screen, and turn vague notes into pointed, watchable feedback.