Why Feedback Is the Secret Ingredient Every Designer Needs

• Concept: A signal that tells users the system has recognized their action and is operating normally.
• Core: A system that gives no response—such as an elevator or traffic-light button with no light or sound—creates anxiety and uncertainty.

• Promotes growth: It acts as a mirror that reveals user discomfort and design blind spots you may not recognize yourself.
• Keeps the product grounded in reality: It helps teams design around real human behavior instead of subjective assumptions.
• Reduces cost and risk: Finding problems before launch prevents significant losses of time and money later.

• Timing: A delayed response can be as harmful as no response. Even a slight delay can make users uneasy, so feedback should be immediate and clear.
• Goldilocks Principle (Not Too Little, Not Too Much)
  • Too little feedback creates confusion, while too much becomes noise and is ignored. For example, a dishwasher loudly announcing that it quietly finished cleaning in the middle of the night.
  • Minor issues should be handled quietly, while important signals should be emphasized and delivered according to priority.

• Collection stages: Feedback should be gathered throughout the design process, including stakeholder alignment during the concept stage, real-user testing during prototyping, and final testing.
• Collection methods: Use user testing, focus groups, surveys, and team critiques.
• Application mindset: Listen without becoming defensive, prioritize rather than panicking over every opinion, and maintain an open mind.

Feedback is a key element in building user trust in a product. Designers should always ask, *“When users interact with this product, can they immediately tell whether it is working properly?”*