Feedback is input from users or stakeholders used to refine a design. It comes in many forms. A usability test where a participant struggles with a menu. A client comment that the logo feels too corporate. A support ticket saying the checkout button is hard to find. A colleague pointing out that the contrast fails accessibility standards. Feedback is the raw material of improvement. Without it, designers work in the dark. They assume their choices are clear, their layouts intuitive, their colors appealing. Feedback tests those assumptions.

Not all feedback is equally useful. Vague feedback wastes time. "I don't like it" offers nothing to act on. Specific feedback is actionable. "The text is hard to read against that background" identifies a problem. "The navigation feels buried" suggests a fix. Designers learn to ask better questions. Instead of "What do you think?" they ask "Where does your eye go first?" or "What would you expect this button to do?" Good feedback also separates preference from performance. A stakeholder may prefer blue. A user may need larger text. Both are valid, but they are different kinds of input. The designer weighs them accordingly. Feedback is not instruction. It is information. The designer decides what to do with it.

Feedback sources

• Usability testing — observed user behavior
• Stakeholder review — client and team input
• Analytics — data on how people use the design
• Support tickets — reported problems
• Peer critique — other designers' perspectives

Feedback is a gift. It reveals what the designer cannot see from inside the work.