Projects
See All My Projects
Admin

Apply Feedback


Introduction

After each round of testing, your team will have amassed a wealth of information that must be digested. You will need to synthesize new information to define next steps that improve your solutions. As you synthesize your feedback, consider both necessity and ease of any changes that need to be made.

  • Necessity: The necessity of a change is determined by the degree to which a user would be positively affected by the change, as well as the number of users who would benefit from the change. A high necessity change might be removing or redesigning a feature that confused all of the users your team tested with. Be mindful, however, that some individuals or prototypes might be outliers and therefore not represent the majority of cases.

  • Ease: The ease of a change corresponds to the amount of time and effort it would take to make the change. Here, the focus is on making changes that require the least investment of your team resources but still improve the quality of a design. Pick the low-hanging fruit first!

Effective ways to do this include:

  1. Gather all your notes and documentation from your testing session
  2. Ask the following questions:
    • What quotes and stories from users and experts stood out to you during testing?
    • What kinds of insights on how your users think or feel did your tests uncover? 
    • Are there any ideas or directions that you should consider based on feedback?
    • Are there any ideas or directions that you shouldn't consider based on feedback?
    • What changes do those quotes, stories, or insights make you consider?
    • How essential is the change?
    • How hard is the change?
    • What next steps do you need to do to address user feedback?
      • This typically includes going into ideate to generate new ways to think about the insights you uncovered, going to immerse to understand a bit more about your challenge, or build to quickly re-make your prototypes to test again.
  3. Decide on 3-4 next steps to complete in the next 2 weeks
    • Find a quote or story to quickly explain why your team is taking that step based on testing.
  4. Assign people to complete each step

Network Best Practices

Iterate after getting feedback like DFA Yale

DFA Yale’s Illumilloon team focused on improving communication among community members and aid first responders in after natural disasters. After testing with users, the Illumiloon team iterated their release mechanism based on feedback. The new release mechanism had detailed step-by-step instructions on how to apply colored bands for different needs, how to mount the balloon, and how to release the balloon. Check out how the team iterated by looking at their two videos below.

1st Prototype - October 2014


2nd Prototype - May 2015