Is seeking feedback recommended in the design process?

• A. Yes. Test it, tweak it, send it.
• B. No, you should design in isolation.
• C. Only after finalizing.
• D. Feedback is unnecessary.

Answer: (A)

Seeking feedback during the design process is recommended because design benefits from real input and iteration. Testing ideas with users and stakeholders early and often helps you verify assumptions, uncover usability issues, and ensure the design actually meets needs and constraints. By observing how people interact with a prototype, you can identify what works, what doesn’t, and why, then make focused refinements. This approach—test it, tweak it, send it—reduces the risk of building something that misses the mark and can save time and resources in the long run.

Designing in isolation misses important perspectives and can lead to gaps that become costly to fix later. Waiting until everything is final to gather feedback increases the chance of major rework. Feedback isn’t unnecessary; it is a critical driver of a design that functions well in the real world.