How to give feedback
Revisions are unlimited, but your time isn’t. Feedback that follows these five rules usually gets you what you want in one round instead of three.
React to the goal, not just the pixels. “This doesn’t feel premium enough for what we charge” beats “make the logo bigger.” We can fix a feeling ten different ways; we can only obey an instruction one way.
Say what works, too. Not for our ego: it stops us from “fixing” the parts you loved.
Batch your notes. One message, one numbered list. Drip-feeding notes through the day restarts the work each time.
Point at things. Screenshot + arrow + one sentence beats three paragraphs of description. A quick Loom counts too.
Separate “change this” from “what if…”. Directives we execute. Ideas we explore. Label which is which and both get handled right.
Grab the template
One message in this shape usually closes the round.
What works: [name it, so we don’t “fix” the parts you love] Change this (directives, we execute): 1. [point at it: screenshot, arrow, one sentence] 2. […] What if (ideas, we explore): - […]
The round-trip machines (avoid these)
“Make it pop”: pop how? Louder color, more contrast, bigger type, more air? Name the feeling that’s missing.
“I’ll know it when I see it” is a brief problem, not a design problem. Let’s find references instead.
“Small tweak: can it also…” is a new request wearing a revision costume. Drop it in the Backlog and it gets full quality.
New ideas that show up mid-revision become new cards (Claude can write them for you). That’s not us being precious: it’s what keeps your active request moving at ~48h speed.