# 08A Turning an Observation into a Clear Request

Useful feedback connects an observation to a requested change, so that the person doing the work knows what to improve.
Instead of saying that the page feels wrong, I explain which part is difficult to read, understand, or use.
I might say that the header is too large on mobile and ask for a smaller title with slightly less padding.
If I want an existing pattern preserved, I include that request rather than assume that the other person will notice it.
For example, I can ask them to replace the icon while keeping its size and alignment consistent with the navigation.
I separate necessary changes from optional ideas, because a long list can make every small suggestion appear equally urgent.
When the task is clear, the next preview should show a specific improvement that we can compare with the previous version.
I review that result using the same content and screen size so that unrelated differences do not confuse the comparison.
If the problem remains, I describe what is still visible and ask for another focused adjustment instead of restarting the entire design.
This approach makes feedback easier to act on and helps the conversation move from personal impressions to concrete decisions.