How to give feedback that gets results

Giving feedback is a skill — and it's one of the most important things you can do to get a great final product. Good feedback gets you what you actually want. Vague feedback leads to guesswork and revision rounds that don't move things forward.

The difference between good and vague feedback

The four parts of good feedback

1. What specifically are you reacting to?

Point to the exact element. Not "the page feels off" — but "the button color on the hero section."

2. What is the problem or concern?

Describe what the issue is, not just that there is one. "It blends in with the background and I'm worried visitors won't notice it."

3. What outcome do you want?

Tell us the goal, not just the change. "I want the button to stand out more so visitors know to click it."

4. Why does it matter?

Context helps us make the right decision. "Our main call to action is to book a call, so this button is critical."

With these four elements, we can make a confident, informed change — and often a better one than you might have specified directly.

Useful things to include in feedback

• Screenshots — circle or annotate the specific area you're commenting on
• Examples — a link to a website, image, or ad that shows what you mean
• Your audience's perspective — "My customers are mostly over 60 — I'm worried the font is too small"
• The business reason — "We're launching a campaign next month and this page is the landing page"

Common feedback mistakes to avoid

Sending feedback in multiple waves

Gather all your feedback before sending. Multiple rounds of "one more thing" emails slow the project significantly and can create conflicts between changes. Read everything once, sit with it, then compile your notes.

Giving prescriptive solutions instead of describing the problem

It's natural to say "make the font bigger" — but what you usually mean is "I'm worried visitors won't read this." Tell us the concern, and we'll find the best solution. We may know a better fix than the one you suggested.

Mixing personal preference with genuine concerns

It's worth distinguishing between "I personally don't love this color" and "I think this color will confuse our customers." We'll always try to serve your customers first. Personal preference is valid input — just label it as such.

Approving something without really reviewing it

A quick "looks great!" without genuinely reviewing can mean you discover problems after development has begun. Set aside real time to review carefully before signing off.

How to submit your feedback

Leave all feedback as a comment in the relevant ClickUp task. If you're reviewing designs shared as a link (e.g. a Figma file), you can often leave comments directly in the tool — ask your project lead whether to use the design tool or ClickUp.

Email support@chykalophia.com if you don't have ClickUp access yet.

Related guides

• How approvals & sign-off work
• What happens in the design phase
• How we communicate (ClickUp, email, calls)