How to give feedback that gets the result you want

Feedback is where most project time is won or lost. Precise feedback is applied in one pass. Vague feedback costs a call, a guess, and often a second round.

Say where, what and why

Three pieces of information make any comment actionable:

  • Where. The page and the section. "Homepage, the three cards under the banner".
  • What. The change. "Swap the second and third cards".
  • Why. The reason, when there is one. "Support is our biggest seller so it should come first". The reason often lets us suggest something better.

Number your points

A numbered list lets us reply against each item confirming done, done differently, or needs discussion. Nothing gets lost.

Describe the problem, not only the solution

"Make the heading bigger" is one solution. "The heading does not stand out enough on my phone" is the problem, and there may be a better fix such as contrast or spacing. Give us both where you can.

Separate must from nice to have

Mark each point as must fix or optional. When time is tight this tells us where to focus without another exchange.

Screenshots help

For anything visual, a screenshot with a circle around the element removes all ambiguity, particularly for issues that appear only on your device or browser.

Feedback to avoid

  • "Make it pop." No two people mean the same thing by this.
  • "I do not like it" without saying which part.
  • Forwarding a chain of internal emails and asking us to extract the feedback.
  • Feedback sent by three people separately with no agreement between them.

Where to send it

The project discussion in the portal at crm.zylax.com.my, so it stays with the project and the whole team can see it.

If you find something hard to describe, ask for a short call on your project thread or write to [email protected] and we will work through it with you.

Did you find this article useful?