WSWhat Scene?

Learn · Process & management

How do you give useful feedback on design and development work?

Focus on the problem, not the prescription: say what feels off and why, rather than dictating the exact fix, so the expert can solve it well. Tie feedback to goals and users ("this makes the main action hard to find") instead of personal taste, and gather it into clear, consolidated rounds.

The least useful feedback is vague ("make it pop") or purely subjective without reasoning. The most useful explains the underlying concern, which lets the designer or developer address the real issue, often better than your suggested fix would.

Consolidate feedback rather than sending a stream of one-off notes, and separate must-fix issues from preferences. Timely, specific, goal-oriented feedback keeps work moving and produces a better result than either silence or a flood of contradictory comments.

Updated July 2026

Related

Want this built, not just explained?