Redesign design — Re:Publica 17

Transcript

1. Redesign Design re:publica 17 - berlin, May 8
2. 2 Let’s talk about food!
4. 4 step 1 step 2 step 3 step 4 step 5 step 6 step 7 step 8 expectation
5. and that’s the result 5
6. 6 Recipe doesn’t guarantee success.
8. Emanuela Damiani @brassy
9. 9 What I Do
10. 10 What I Do
11. Design is changing
12. Design as a plan.
13. Industrial mindset.
14. Ideation stops.
15. Production and distribution start.
16. Today markets are unpredictable.
17. Everything is software.
18. Software is not
 a house.
19. We still have an industrial mindset.
20. Organizations are changing.
21. Adapt to uncertainty.
22. Teams run software products that run from inception to retirement. Jez Humble
23. You build it, you run it.
24. You build it, you run it. DevOps Mantra
25. Responding to change over following a plan Agile Manifesto
26. How can we make design resilient?
27. You run it, you design it.
28. DesignOps
29. Enable others to design.
30. High-quality design artefacts.
31. Increase coherency in the product.
32. Give teams more autonomy.
33. Providing design infrastructures.
34. Tools and resources.
35. AirBnb
36. Design System.
43. A system’s value is realized when products ship features using a system’s parts. Nathan Curtis
44. Design System isn’t a style guide.
45. Design System isn’t a pattern library.
46. Design System is
 a shared languange.
47. It combines theory
 and resources.
48. It helps build cohesive experiences.
49. It helps focus on what really matters.
50. Learning is what really matters.
51. Minimise the effort, maximise feedbacks.
52. DesignOps support design decision at team level.
53. Product teams design and operate the software.
54. Product teams conduct experiments.
55. Product teams validate assumptions.
56. Faster feedback loops.
57. Product teams constantly learn.
58. From Design as a plan to Design a service
59. Use people feedback as input to design.
60. Constantly seeking for empathy.
61. Thank you. > Emanuela Damiani @brassy > Redesign Design — May 8, 2017