Redesign design — Re:Publica 17

Transcript

1. Redesign
   Design
   re:publica 17 - berlin, May 8
   

   View Slide

2. 2
   Let’s talk
   about food!
   

   View Slide

3. View Slide

4. 4
   step 1 step 2 step 3
   step 4 step 5 step 6
   step 7 step 8 expectation
   

   View Slide

5. and that’s the
   result
   5
   

   View Slide

6. 6
   Recipe doesn’t
   guarantee success.
   

   View Slide

7. View Slide

8. Emanuela
   Damiani
   @brassy
   

   View Slide

9. 9
   What I Do
   

   View Slide

10. 10
    What I Do
    

    View Slide

11. Design is
    changing
    

    View Slide

12. Design as a plan.
    

    View Slide

13. Industrial mindset.
    

    View Slide

14. Ideation stops.
    

    View Slide

15. Production and
    distribution start.
    

    View Slide

16. Today markets are
    unpredictable.
    

    View Slide

17. Everything is
    software.
    

    View Slide

18. Software is not

    a house.
    

    View Slide

19. We still have an
    industrial mindset.
    

    View Slide

20. Organizations are
    changing.
    

    View Slide

21. Adapt to
    uncertainty.
    

    View Slide

22. Teams run software products
    that run from inception
    to retirement.
    Jez Humble
    

    View Slide

23. You build it,
    you run it.
    

    View Slide

24. You build it,
    you run it.
    DevOps Mantra
    

    View Slide

25. Responding to change over
    following a plan
    Agile Manifesto
    

    View Slide

26. How can we make
    design resilient?
    

    View Slide

27. You run it,
    you design it.
    

    View Slide

28. DesignOps
    

    View Slide

29. Enable others to
    design.
    

    View Slide

30. High-quality design
    artefacts.
    

    View Slide

31. Increase coherency
    in the product.
    

    View Slide

32. Give teams more
    autonomy.
    

    View Slide

33. Providing design
    infrastructures.
    

    View Slide

34. Tools and resources.
    

    View Slide

35. AirBnb
    

    View Slide

36. Design System.
    

    View Slide

37. View Slide

38. View Slide

39. View Slide

40. View Slide

41. View Slide

42. View Slide

43. A system’s value is
    realized when products ship
    features using a system’s
    parts.
    Nathan Curtis
    

    View Slide

44. Design System isn’t a
    style guide.
    

    View Slide

45. Design System isn’t a
    pattern library.
    

    View Slide

46. Design System is

    a shared languange.
    

    View Slide

47. It combines theory

    and resources.
    

    View Slide

48. It helps build
    cohesive experiences.
    

    View Slide

49. It helps focus on
    what really matters.
    

    View Slide

50. Learning is what
    really matters.
    

    View Slide

51. Minimise the effort,
    maximise feedbacks.
    

    View Slide

52. DesignOps support
    design decision at
    team level.
    

    View Slide

53. Product teams
    design and operate
    the software.
    

    View Slide

54. Product teams
    conduct
    experiments.
    

    View Slide

55. Product teams
    validate
    assumptions.
    

    View Slide

56. Faster feedback
    loops.
    

    View Slide

57. Product teams
    constantly learn.
    

    View Slide

58. From Design as a
    plan to Design a
    service
    

    View Slide

59. Use people feedback
    as input to design.
    

    View Slide

60. Constantly seeking
    for empathy.
    

    View Slide

61. Thank you.
    > Emanuela Damiani @brassy
    > Redesign Design — May 8, 2017
    

    View Slide