How to prepare feedback for a website redesign
Clear feedback helps the team make better decisions and turns general preferences into concrete changes.

Feedback is more useful when it explains the problem you noticed and the effect you want to achieve. Phrases such as “I do not like it” can start a conversation, but they do not provide enough information for a design decision.
Before sending observations, identify which website goal each proposed change supports.
Separate preferences from real problems
A personal preference can matter, but it should be separated from issues that affect usability, clarity or the page outcome.
- what a visitor does not understand
- where information is difficult to find
- which element does not work on mobile
- which part does not support the page goal
Describe the situation and impact
Instead of requesting only a colour or block change, explain where the problem appears and what happens because of it. A concrete example helps choose the right solution.
Mention the page, device and steps that revealed the problem when they are relevant.
Prioritise observations
Not every change has the same importance. Group feedback into blockers, important improvements and preferences that can be reviewed later.
Start with problems affecting navigation, understanding the offer, forms or access on mobile.
Use examples and references
A screenshot, section link or comparison with a desired behaviour can clarify the observation. The reference should explain the goal, not require copying another page.
If you share several examples, note which element matters in each one.
Review feedback against goals
After writing the observations, ask whether each suggestion supports an important action, piece of information or stage in the visitor journey.
A redesign can look more modern while missing the original problem if feedback is not connected to goals.
Keep one clear decision for each point
Close each observation with a decision: change it, test it or leave it unchanged for now. This makes feedback easy to track and review after implementation.
Connect the project to relevant articles and services for context, then review important pages on mobile before launch.
This article was prepared with the assistance of AI tools and editorially reviewed before publication.


