Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Design Processes, Not Interfaces

7b1746f5ae99453e6a67f022ec0d73bd?s=47 Tiffany Conroy
April 30, 2012

Design Processes, Not Interfaces

Computers are tools that help people accomplish tasks by making the process easier, faster, cheaper, less error-prone, or just more fun.
But what tasks? And by what process? What parts of the process can the computer make better? How can users interact with the computer to make it do its part of the process? Only lastly can we ask: what must be presented to the user and how?

Video: http://vimeo.com/45897174/

7b1746f5ae99453e6a67f022ec0d73bd?s=128

Tiffany Conroy

April 30, 2012
Tweet

Transcript

  1. NOT INTERFACES DESIGN PROCESSES

  2. @theophani TIFFANY CONROY

  3. None
  4. None
  5. NOT INTERFACES DESIGN PROCESSES

  6. NOT FOR THE DATA DESIGN INTERFACES FOR THE PROCESS OF

    INTERACTING WITH THE DATA
  7. NOT FOR THE DATA DESIGN INTERFACES FOR THE PROCESS OF

    INTERACTING WITH THE DATA
  8. NOT FOR THE DATA DESIGN INTERFACES FOR THE PROCESS OF

    INTERACTING WITH THE DATA
  9. NOT FOR THE DATA DESIGN INTERFACES FOR THE PROCESS OF

    INTERACTING WITH THE DATA
  10. None
  11. “Tiffany will discuss the importance of process-oriented design; What parts

    of the process can the computer make better? How can users interact with a computer to make it do its part of the process?”
  12. INTERFACE DESIGN

  13. None
  14. None
  15. None
  16. None
  17. INTERFACE DESIGN: appropriate information in the appropriate place.

  18. None
  19. INTERACTION DESIGN

  20. HOW DOES THE USER …

  21. HOW DOES THE USER … affect change?

  22. HOW DOES THE USER … affect change? understand the change?

  23. HOW DOES THE USER … affect change? understand the change?

    understand what they can change?
  24. BILL VERPLANK

  25. None
  26. AFFORDANCES

  27. AFFORDANCES FEEDBACK

  28. AFFORDANCES FEEDBACK MAPS & PATHS

  29. None
  30. None
  31. None
  32. PROCESS DESIGN

  33. None
  34. JOB SHADOWING

  35. ASK LOTS OF QUESTIONS

  36. • How will you solve this problem? • What are

    the steps? • Why did you do that? • How did you know that? • How did you find out the information you needed to make that decision? • What if you didn't know that? • Are there any situations when this approach doesn't work? • What would you change? ASK LOTS OF QUESTIONS
  37. None
  38. None
  39. http://twitter.com/#!/awbjs/status/192997091440721920

  40. None
  41. None
  42. None
  43. None
  44. Text

  45. None
  46. None
  47. None
  48. What do we need humans for?

  49. What do we need humans for? Do we understand this

    process well enough to automate it?
  50. ADAPTED FROM http://old.sigchi.org/cdg/figure_1.pdf

  51. ADAPTED FROM http://old.sigchi.org/cdg/figure_1.pdf

  52. None
  53. WITHOUT KNOWING THE PROCESS, YOU CAN’T DESIGN THE INTERFACE

  54. THANKS! TIFFANY CONROY @theophani Follow me for slides and links

    www.soundcloud.com