Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Why Developers Should Learn Design - ViewSource 2016

394 views

Published on

I turned the first part of the talk into a blog post:
https://medium.com/@iamtenko/stop-looking-for-designers-become-one-291993a4f195#.40uli95c1

There has been a huge buzz in the last 1-2 years around the topic that "Everyone should learn how to code" and more specifically that "Designers should learn how to code". Why is this not happening the other way around? Can brainstorming, user research, personas and design thinking change the way we write software? Can we adopt the same army-knives used by design agencies and freelancers to speed up the development of Software or to better prioritise some features over others?


This talk has been given at ViewSource Conference 2016.
Berlin, 14th of September 2016

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Why Developers Should Learn Design - ViewSource 2016

  1. 1. STOP LOOKING FOR DESIGNERS. BECOME ONE! On why developers need to learn design.
  2. 2. DESIGNERS SHOULD LEARN HOW TO CODE. Kids too. And grandparents. And your dog.
  3. 3. WHAT ABOUT DEVELOPERS?
  4. 4. DEVELOPERS vs. DESIGNERS
  5. 5. AWS IS A PLATFORM TO HELP DEVELOPERS RUN THINGS IN THE CLOUD™
  6. 6. USABILITY Yes. Developers need usable tools too.
  7. 7. "HEY, WE JUST FINISHED IMPLEMENTING THIS. LET'S CALL THE DESIGNERS AND MAKE IT LOOK NICE!" cit. "Unknown developer", all the times.
  8. 8. NO!
  9. 9. USER EXPERIENCE DESIGN
 (UX) Human-Machine interaction
  10. 10. DESIGN AS A SERVICE™
  11. 11. BUSINESS NEED
  12. 12. BUSINESS NEED DESIGN AGENCY
  13. 13. BUSINESS NEED DESIGN AGENCY DEVS IMPLEMENTATION
  14. 14. BUSINESS NEED DESIGN AGENCY DEVS IMPLEMENTATION ??? PROFIT
  15. 15. TODAY IS DIFFERENT Agile methodologies, design thinking.
  16. 16. BRAINSTORM PROTOTYPE SHIP TESTING ITERATE ON PROTOTYPE
  17. 17. WE ARE NOT "JUST" SOLVING A PROBLEM. WE DELIVER AN EXPERIENCE
  18. 18. TASK DRIVEN TEAMS VS USER DRIVEN TEAMS
  19. 19. TASK DRIVEN TEAMS They find a solution to a specific business or technological problem
  20. 20. USER DRIVEN TEAMS They solve a user problem
  21. 21. FROM TASK SOLVERS TO EXPERIENCE CREATORS
  22. 22. USER CENTERED DESIGN Design based on the needs of the user.
  23. 23. "[..] simplifying the structure of tasks, making things visible, getting the mapping right, exploiting the powers of constraint, designing for error, explaining affordances and seven stages of action. [..]" https://en.wikipedia.org/wiki/Don_Norman#User-centered_design
  24. 24. PERSONA SCENARIO
 USE CASE
  25. 25. PERSONA: "[..] is fictional character created to represent the different user types that might use a site, brand, or product in a similar way. [..]" https://uxthink.wordpress.com/2010/11/30/using_scenarios/
  26. 26. SCENARIO: "[..] is a fictional story about the "daily life of" or a sequence of events with the primary stakeholder group as the main character. Typically, a persona that was created earlier is used as the main character of this story. [..]" https://en.wikipedia.org/wiki/User-centered_design#Analysis_tools
  27. 27. USE CASE: "[..] describes the interaction between an individual and the rest of the world. [..] may consist of intricate details and interactions between the actor and the world. [..]" https://en.wikipedia.org/wiki/User-centered_design#Analysis_tools
  28. 28. CULTURAL CLASH
  29. 29. ILLUSTRATOR USER RESEARCH WIREFRAME You designers are better. That's fine, it's your job.
  30. 30. IT'S ABOUT UNDERSTANDING THE IMPLICATION OF WHAT WE ARE IMPLEMENTING
  31. 31. IT'S ABOUT TESTING AND KILLING OVER-ENGINEERING
  32. 32. IT'S ABOUT SPEAKING THE SAME LANGUAGE
  33. 33. IT'S ABOUT CREATING AN EXPERIENCE.
  34. 34. NOW: RELEASE YOUR FRUSTRATION!!
  35. 35. DEVS FAULTS: We are used to talk to machines
  36. 36. DEVS FAULTS: We are used to talk to machines We have a superiority complex
  37. 37. DEVS FAULTS: We are used to talk to machines We have a superiority complex Our users are stupid
  38. 38. DEVS FAULTS: We are used to talk to machines We have a superiority complex All users are stupid
  39. 39. HOW DO WE FIX THIS?
  40. 40. WORK NEXT TO EACH OTHERS
  41. 41. PRINT YOUR PERSONAS
  42. 42. MAKE THE DEVS PARTICIPATE TO USER TESTING
  43. 43. MAKE THEM DESIGN
  44. 44. COMMUNICATE. AS PEERS
  45. 45. SUGGESTIONS?
 EXPERIENCES?
  46. 46. THANK YOU. @iamtenko hi@tenko.it www.tenko.it

×