Point to the exact part of the page
Avoid notes such as “the middle feels off.” Instead, place a pin on the section you mean and name the element: “The testimonial heading is easy to miss.” A screenshot annotation makes that precision effortless.
When a comment applies to a broader area, say so. “This whole section feels crowded” gives a designer permission to consider spacing, hierarchy, and structure instead of changing one isolated detail.
Explain the outcome you need
A proposed solution can be helpful, but the reason behind it is more valuable. Rather than only saying “Make the button bigger,” try “I want new visitors to notice how to book a demo sooner.” The team can then choose the best solution for the page.
Similarly, state whether a note is a must-fix, a question, or an idea for later. This helps everyone prioritise without guessing.
Keep one note to one issue
Bundled feedback is difficult to track: “Change this image, rewrite the headline, and make the page feel friendlier.” Split it into separate annotations. Each item can then be discussed, completed, or deferred on its own.
Before sending feedback, read your notes once as if you had not seen the design before. If a colleague could not tell what to change, add a little context.
Review the revised version against the goal
The final review is not just a check for whether every requested edit appeared. Ask whether the page now makes the intended message clear and supports the action you want visitors to take.
With comments pinned directly to the screenshot, that final pass is calmer and faster: the conversation stays next to the work, not scattered across inboxes and meeting notes.