ADDC 2017 - Anastasiia Voitova, Anna Iurchenko: Solve it. Don't just build it.

ADDC 2017 - Anastasiia Voitova, Anna Iurchenko: Solve it. Don't just build it.

This is a story from a designer and a developer who worked together and built a product for people who really need it. It is a first-hand story about behind-the-scenes processes, results, and reflections about the design & development of a medical app which actually saves people’s lives.

We will walk you through our design process from ideation and brainstorming, research and user study to first prototype and iterations. We will talk about why and how engineers should be a part of this journey, how to create shared understanding about users, and how to create a product that makes someone's life better together.

Is it all about pixels, colors, lines of code, or is it about users?

More about the talk, authors & slides: https://addconf.com/talks/18/
Read about the conference: https://addconf.com

Transcript

  1. #addconf SOLVE #addconf

  2. @vixentael Lead Developer at Stanfy @anatinge Lead Designer at Stanfy

  3. None
  4. super-simple app that helps my patients take drugs on time

  5. forget about their pills! 50 % = medical non-adherence

  6. 15% transplant patients who forget pills loose their transplant and

    die
  7. None
  8. None
  9. None
  10. Non- collaborative process Why it doesn’t work PLAN for today

  11. Non- collaborative process Why it doesn’t work Collaborative design process

    Why & how do it together PLAN for today
  12. Non- collaborative process Why it doesn’t work Collaborative design process

    Why & how do it together Take aways Next steps for your team PLAN for today
  13. Non- collaborative process

  14. Non-collaborative process

  15. Non-collaborative process

  16. Non-collaborative process

  17. Non-collaborative process

  18. PROS of this approach

  19. Everyone do the part they are the best in 1.

  20. Everyone do the part they are the best in 1.

    2. Start faster, move faster
  21. CONS of this approach

  22. Designers’ ideas difficult to implement 1.

  23. Designers’ ideas difficult to implement 1. 2. Designers unaware of

    technical possibilities that make solution better
  24. Designers’ ideas difficult to implement 1. 2. Designers unaware of

    technical possibilities that make solution better 3. Developers feels disengaged
  25. None
  26. Collaborative design process

  27. None
  28. Research helps to understand people, their needs, motivations, context

  29. Research enable us to design the right experience for Real

    people who will use your product
  30. Goal and questions

  31. Identify main reasons why transplant patients forget to take their

    medications?
  32. How patients lives are changed after the surgery? 1. 2.

    What are the main challenges they face with after? 3. What is the context?
  33. Goal and questions Plan and prepare

  34. None
  35. Goal and questions Plan and prepare Collect the data

  36. None
  37. Topics we discussed how life changed after surgery life before

    the surgery 1. 2. habits around taking medications 3. computer and mobile habits 4. …
  38. sell your product ask about future behavior ask leading questions

    ask YES/NO questions limit their imagination
  39. smile take notes ask open-ended questions get their story shut

    up and listen
  40. 90% listening 10% TALKING

  41. Invite your developers!

  42. KEEP ENGINEERS ENGAGED!

  43. What I heard What I saw What stood out TEN

    minutes One idea per sticker
  44. Collaborative design

  45. DEEP DIVE INSIDE DOMAIN AREA because sometimes interviews are not

    enough!
  46. None
  47. Collaborative design

  48. None
  49. start in group

  50. None
  51. None
  52. None
  53. show process with usability tests Sketch UI concepts Together

  54. Collaborative design

  55. Share ownership of the product!

  56. SOLUTION

  57. Transplant Hero is ABOUT transplant patients ONLY

  58. None
  59. Transplant Hero is your smart guide to the anti- rejection

    medicine.
  60. None
  61. Transplant Hero is the bright part of your post- transplant

    life.
  62. None
  63. HeRoes patients (because words are important)

  64. Be ethical

  65. Be a friend, not a doctor.

  66. How might we?

  67. Let’s play!

  68. None
  69. None
  70. - Do people understand our product? - Do they care?

    - Can they figure out how to use it? - Which messages are most effective at explaining it? Validating prototype with users
  71. avoid building unnecessary stuff

  72. None
  73. None
  74. None
  75. None
  76. Take aways

  77. Collaborative design

  78. process Be visual!

  79. Move into one ROOm

  80. create design+dev channel

  81. Track every idea in a backlog

  82. Make DEMOs TOGETHER!

  83. Have fun at retro!

  84. Encourage team to draw!

  85. mixed media :)

  86. Remote retro

  87. Plasticine retro!

  88. None
  89. None
  90. EAT YOUR OWN DOG FOOD

  91. Work together! Share knowledge (one room / chat room, explore

    OSS components) 2. Make demos together and have fun retrospectives 3. Track every idea in backlog 4. Use your own product 5. 1. Conduct user studies together (research + analysis + development)
  92. Share with the team user’s feedback! Thank you for Transplant

    Hero. It has enabled my son to learn, at a young age, his meds and dose by sight and name, and how to adhere to his medication schedule. He is confidently on the path to a happy and normal childhood and life. Thank you!
  93. @vixentael @anatinge QUESTIONS? #ADDconf