A screenshot in a chat can start a useful conversation. A week later, it usually leaves the same questions: which page, which screen size, and what exactly should change? Good feedback answers those questions before anyone has to ask. This guide shows what that looks like in a single note.
Start with the observation.
Name what you saw before proposing what to do. “The primary action looks the same as the secondary link” gives the designer and the developer a shared problem. “Make the button pop” gives them a guess about your taste.
Keep each note small enough to discuss and verify. If one comment holds three unrelated changes, split it into three findings. Each one can then have its own owner, priority and resolution.
- Vague
- “Make the button pop.”
- Observation
- On mobile, “Request a quote” looks the same as the “Learn more” link next to it.
- Outcome
- Visitors can tell which action comes first.
- Evidence
- Pinned to the button, 390 px wide, screenshot attached.
- Done when
- The quote button is clearly the first action at 390 px and at 1440 px.
Keep the evidence with the note.
A page URL is only a starting point. The screenshot shows the state you saw, the selected element narrows the location and the viewport explains why someone on a larger screen may not see the problem at all.
An Opmerk pin keeps that context with the note: the screenshot, the page URL, the element’s selector and text, and the viewport. Nobody has to rebuild the situation from a chain of messages.
- Pin the element itself, not the empty space next to it.
- Say what you observed and the outcome you want.
- Mention the screen size or state when it changes the issue: signed in, menu open, a form showing an error.
- Add one condition that tells everyone when the change is done.
Separate the goal from the suggested fix.
“Make the next step clearer” is a goal. “Change the label to Request a quote” is one possible fix. Both can belong in a note, but they should be easy to tell apart.
That leaves room for someone with more context to propose a better solution. It also makes the final check fairer: you test whether the goal was met, not only whether an instruction was followed.
Give the next step an owner.
A good observation still needs somewhere to go. Assign it, set a priority that fits the project and keep the discussion in the thread under the pin. When the work is bigger than one small change, link it to a task.
If the decision happens in a call, write it back into the thread in one sentence. The next person should understand why the work changed without having attended every meeting.
Resolve after checking the outcome.
A change being shipped and a finding being resolved are not the same event. Open the live page, check the screen size from the note and test the “done when” condition.
When it holds, resolve the finding. The note keeps its value afterwards: it records what was seen, what was decided and why the page looks the way it does now.
TAKE IT INTO YOUR NEXT REVIEW
A useful note has four parts: what you saw, the outcome you want, the evidence, and a condition for done.
Explore the feature