Feedback: Defining the idea further

A lot to think about

After last week, I got the chance to sit down with Eric and two of my classmates, Abhi and Kate. I also analyzed the feedback I received from presenting the prototype in class and our guest critic, Graham Letorney. All the feedback I got from running the prototype as well as how to take the idea further has been key in informing my next steps.

Key takeaways from Eric:

  • Define the heart of the concept, the execution comes after.
  • Modes of the solution: At home, away from home, app only?
  • Placement in the house: is it a combination of being private and shared or some aspects of it are solely for the MS user?
  • On the supporters’ end: Notifications, feedback and reception of this updated information. How much is too much or too little? What does the next step for this group of users look like?

Key takeaways from Kate and Abhi:

  • The human-ness of a physical object is key.
  • There has to be remote input for days users are not home.
  • Blending in with the architecture of the house is key.
  • What happens next after the interactions have been made is important.

Key takeaways from class feedback:

Things working:

  • Simply colors, no text, to express emotion.
  • Prototype testing to establish patterns.
  • ‘Breaking the ice’ is not a must in this concept.
  • Letting user choose their own meaning to each color.

Things that need work:

  • Centering around a user and their story.
  • Support network facing solution: what does it look like for the supporters? What is the next step for them?
  • Centering the solution around people living with MS and their conditions.
  • Public and private modes of this solution.

Ideas:

  • Feedback loop outside of the communication through text.
  • Inputting cards digitally, a drag and drop word association: pulling colors to words they think of for less typing and cognitive load.
  • Comprehensive, summary screens to observe patterns together.
  • Adding folds, shapes to visualize further.
  • Outreach routes for users and ways to connect the community.
  • Built in rewards to encourage constant input.
  • AI to predict patterns in the days/everyday life.
  • App to piece together journey as next prototype?

Questions:

  • How is this specific to people living with MS and MS support networks?
  • What kind of attention do people living with MS actually need and in what form?
  • How can support system help/act once MS user flags that they need help or attention?
  • Can input only already somewhat help the person living with MS before the involvement of the support network?
  • Emergency situations/cases of sadness?
  • Key feedback and results the user with MS is looking for?

--

--