Developers are Experience Designers

The people who use the products we build will never differentiate between design and the technology. As team members we tend to look at our projects through only one lens, and in turn lose sight of the bigger picture. Lets talk about breaking down these silos and what each role plays in creating products that deliver the experience users deserve.

Transcript

1. DEVELOPERS ARE EXPERIENCE DESIGNERS (AND DON’T EVEN KNOW IT)
2. Hi! I’m Ryan Nicholson AestheticRain.com - @RyanDNicholson
3. DISCLAIMER I’M NOT A STRONG DEVELOPER
4. I’M A DESIGNER, WE’RE WEIRD
5. BUSINESS REPS ARE ANNOYING
6. ANGRY DEVELOPER DEVELOPERS ARE SCARY
7. MOST PRODUCTS SUCK
8. EXCEPT YOURS... YOURS ARE AWESOME DON’T HURT ME
9. IF WE’RE SUCH EXPERTS WHY DO THEY SUCK?
10. WE’RE DISCONNECTED
11. WEB DESIGNER USERS
12. PROJECT MANAGERS STRATEGISTS DESIGNERS DEVELOPERS ETC. ETC. ETC. USERS
13. “A beef filet cooked for 15 hours by 30 different cooks doesn’t necessarily taste better than a cheeseburger” OLIVER REICHENSTEIN
14. THIS IS NOT A PRODUCT
15. NEITHER IS THIS
16. NOT EVEN CLOSE
17. PEOPLE DON’T KNOW OR CARE
18. IT’S WHAT PEOPLE EXPERIENCE
19. WE HAVE DIFFERENT ROLES AND TEND TO WEAR BLINDERS
20. WE DO OUR JOB AND PASS IT ON
21. THIS CREATES SILOS OF SKILL SETS WHICH CAUSE GAPS IN PRODUCTION
22. Maker Thinker Creative Analytical
23. A LOSS OF VALUE IN WHAT OTHERS DO ANGRY DEVELOPER
24. GAPS IN PRODUCTION = GAPS IN EXPERIENCES
25. WE DO THE TASKS WE’RE GIVEN BY THOSE WE REPORT TO
26. “THE CODE WORKS, GOOD JOB” ENGINEERING
27. “THE CODE WORKS, BUT THE WORKFLOW SUCKS HOW CAN WE FIX IT?” UX TEAM
28. THE EASY WAY IS NEVER THE RIGHT WAY
29. EVERYONE MUST OWN THE EXPERIENCE
30. DESIGNERS HAVE A OFFENSIVE ROLE
31. DEVELOPERS ARE ON THE FRONT LINES
32. FIRST TO USE THE ACTUAL PRODUCT
33. FIRST TO DISCOVER ERRORS
34. FIRST TO RECOGNIZE DESIGN GAPS
35. FIRST TO FIND PERFORMANCE ISSUES
36. FIRST TO LOCATE SECURITY RISKS
37. DEVELOPERS PLAY A HUGE ROLE IN THE FINAL EXPERIENCE AND SHOULD PLAY A BIGGER PART IN THE DESIGN PROCESS
38. DESIGNERS NEED A FUNCTIONAL UNDERSTANDING OF DEVELOPMENT (WE COULD ARGUE THIS TOPIC FOR DAYS)
39. HOWEVER, EVERYONE NEEDS A FUNDAMENTAL UNDERSTANDING OF DESIGN
40. “Form follows function - that has been misunderstood. Form and function should be one, joined in a spiritual union” FRANK LLOYD WRIGHT
41. SO NOW I’M AN EXPERIENCE DESIGNER? CRAP NOW WHAT?
43. DESIRABILITY USABILITY USEFULNESS
44. USABILITY USEFULNESS &
45. GET OUT OF THE OFFICE EVALUATE AND BE INSPIRED USABILITY USEFULNESS
46. TALK TO PEOPLE UNDERSTAND YOUR USERS USABILITY USEFULNESS
47. RECOGNIZE QUALITY DESIGN MAKE NOTE OF GREAT THINGS USABILITY USEFULNESS
48. DO WHAT THEY DO PUT YOURSELF IN THEIR SHOES USABILITY USEFULNESS
49. BECOME T SHAPED
50. “Having a principal skill that describes the vertical - but can branch into other skills and do them well” TIM BROWN
52. LOGIC ENGINEERING FUNCTIONALITY TECHNOLOGY DRIVEN
53. LOGIC ENGINEERING FUNCTIONALITY TECHNOLOGY DRIVEN DEVELOPMENT USABILITY USEFULNESS EXPERIENCE DRIVEN
54. LOGIC ENGINEERING FUNCTIONALITY DEVELOPMENT USABILITY USEFULNESS EXPERIENCE DRIVEN
55. WE ALL HAVE A DIFFERENT “T” USE THEM TO FILL GAPS IN PRODUCTION
56. EVERYONE PROTOTYPES THINK IN THE CONTEXT OF THE FINAL PRODUCT
57. BREAK DOWN SILOS FRAME TASKS AROUND THE USER’S EXPERIENCE
58. CREATE A COMMON LANGUAGE ENCOURAGE MORE COLLABORATION
59. CREATE SKILL OVERLAP AMONG TEAMS
60. Maker Thinker Creative Analytical
61. Maker Thinker Creative Analytical
62. THIS ISN’T EASY
63. THIS EXPECTS MORE OUT OF PEOPLE AND PUSHES THEM OUT OF THEIR COMFORT ZONES
64. TALK WITH OTHER TEAM MEMBERS LEARN THEIR SKILLS AND SHARE YOUR KNOWLEDGE
65. BE ABLE TO DESIGN SOMETHING ALMOST AS WELL AS YOU CAN BUILD IT
66. IT’S NO LONGER OK TO “NOT KNOW” EVEN WORSE TO NOT CARE
67. ULTIMATELY WE’RE BUILDING FOR PEOPLE LETS START THINKING THAT WAY
68. TIME TO KICK SOME A** Ryan Nicholson - AestheticRain.com - @RyanDNicholson