Scale your Design up — codetalks version

Transcript

1. Emanuela Damiani Code.Talks — Hamburg — September 28, 2017 Scale Your Design Up
2. design is changing
6. design is changing
7. Matteo @MatteoMCED Senior Consultant for ThoughtWorks
8. Ideate Specifications Frame industrial mindset Design Phase
9. Distribution Production industrial mindset Ideate Specifications Frame Design Phase
10. Emanuela @brassy Working at ux designer for Firefox
11. 36.03% of market share in germany StatCounter Global Stats August 2017
12. Firefox Quantum new. fast. fierce. available in release by november 14 
 or right now in beta or in the developer edition
14. markets are hard to predict
15. today everything is software
16. 6/10 top 10 companies in the world are tech companies
17. software is easy to change
18. Recall a product is way more expensive than a bug-fix
19. flexibility & resilience
20. rethink how we create digital product and services
21. “ Alberto Brandolini Introducing Eventstorming Few people have done more harm to software development than those advocating that is like “building a house”.
22. making software as hardware
23. the water-scrum-fall
24. Marketing & Sales the water-scrum-fall
25. Marketing & Sales Stakeholde rs the water-scrum-fall
26. Marketing & Sales Stakeholde rs Project Manager the water-scrum-fall
27. Marketing & Sales Stakeholde rs Project Manager Design Team the water-scrum-fall
28. Marketing & Sales Stakeholde rs Project Manager Design Team User Research Team the water-scrum-fall
29. Marketing & Sales Stakeholde rs Project Manager Design Team User Research Team the water-scrum-fall Specs!
30. Marketing & Sales Stakeholde rs Project Manager Design Team Dev Team User Research Team the water-scrum-fall Specs!
31. Marketing & Sales Stakeholde rs Project Manager Design Team Dev Team User Research Team Final Product the water-scrum-fall Specs!
32. Marketing & Sales Stakeholde rs Project Manager Design Team Dev Team User Research Team Final Product Users the water-scrum-fall Specs!
33. Marketing & Sales Stakeholde rs Project Manager Design Team Dev Team User Research Team Final Product Users the water-scrum-fall Specs!
34. Marketing & Sales Stakeholde rs Project Manager Design Team Dev Team User Research Team Final Product Users the water-scrum-fall Specs!
35. design as planning for the future
36. designers focus is before the launch
37. What about user research?
38. “ Brian Nosek Estimating the reproducibility of psychological science Over half of psychology studies fail reproducibility test.
39. Subject selection bias Poor experimental control Inconsistent measurement Demand characteristics Inadequate consideration of statistical power Partial reporting Post-hoc cherry picking of significant results Why research fails
40. people don’t know what they want until they’re using it
41. capture learnings and react rapidly
42. decisions are less important if it’s easy to adjust our course
43. baby steps
44. Think Make Check
45. Think Make Check Sketch Decide the “5 days” approach
46. running one experiment is easy… Matteo Cavucci “
47. running experiments at scale is hard! Matteo Cavucci “
48. devOps
49. devOps is not developer operations
50. “ Jez Humble Notes around the devOps manifesto Delivery teams run software products - not projects - that run from inception to retirement
51. you build it, you run it DevOps Mantra
52. observing the product
53. devOps is all about feedback
54. design as a continuous conversation designOps
55. a two-way conversation
56. building shippable software is expensive, but effective
57. minimise efforts, maximise feedback
58. A.I. and machine learning
59. experiments require automation and organisational structure
60. Design System, 
 a product servings other products
61. does your company have a pattern library or a style guide?
62. make the right choice the easiest choice
63. tweet…
64. design system is a shared language
65. faster generation of experiments, easier to create multiple variants
66. enable other to design
70. design infrastructure
78. unique source-of-truth
79. design tokens, design decisions make it easy to implement
80. design
 decision
81. token data (.JSON) design
 decision
82. iOS Web token data (.JSON) design
 decision token data (.xml) Android token as variables (.css) token as variables (.sass)
83. iOS Web token data (.JSON) design
 decision token data (.xml) Android token as variables (.css) design system website npm module sketch color palette keynote color palette addons website token as variables (.sass)
84. iOS Web token data (.JSON) design
 decision token data (.xml) Android token as variables (.css) design system website npm module sketch color palette keynote color palette the next hot thing! addons website token as variables (.sass)
86. start with but don’t stall with just color & type.
87. focus on what really matter
88. making your design more accessible
89. making your design more future-friendly
90. making your design more performant
91. making your design more resilient
92. define micro-interactions 
 and animations
93. build a conversation with the users
94. you run it, you design it
95. design the feedback
98. me!
99. delight the user
100. everything is automate! 
 so, what now?
101. organisational structures
102. Cross functional the product team
103. Cross functional End-to-end value creation the product team
104. Cross functional End-to-end value creation Domain experts the product team
105. Cross functional End-to-end value creation Domain experts May (or may not!) 
 include a designer the product team
106. user-driven iterations Product Team co-creation of value driven by experiments feedback! Users Production Environment
107. dynamic strategy Product Team co-creation of value driven by experiments purpose feedback! feedback! Users Strategy Production Environment
108. design as a service Product Team Users Strategy co-creation of value driven by experiments Production Environment purpose feedback! pull, not push! feedback! feedback! DesignOps
109. Includes designers, developers, data analysts designOps team
110. Includes designers, developers, data analysts Provides the design infrastructure designOps team
111. Includes designers, developers, data analysts Provides the design infrastructure Manage the design system life designOps team
112. Includes designers, developers, data analysts Provides the design infrastructure Manage the design system life Observes org design needs designOps team
113. Includes designers, developers, data analysts Provides the design infrastructure Manage the design system life Observes org design needs Ideates org-wide solutions designOps team
114. Includes designers, developers, data analysts Provides the design infrastructure Manage the design system life Observes org design needs Ideates org-wide solutions Scales up local optimised solutions designOps team
115. Includes designers, developers, data analysts Provides the design infrastructure Manage the design system life Observes org design needs Ideates org-wide solutions Scales up local optimised solutions […] designOps team
116. governance
117. no magic spell
118. design for learning
 experimenting is part of the design process
119. everyone in your organisation should be able to produce high quality design artefacts
120. launching a new feature is just the beginning of a continuous design process
121. Emanuela Damiani Thank you Scale Your Design Up Code.Talks — Hamburg — September 28, 2017