Community Based Design - reload

A design process can be extraordinarily structured, or entirely missing. Either way, it often requires a remarkable number of conversations with all the stakeholders involves, including people from different departments and the users. But, what does happen when we add the unpredictable power of a community? In this talk, I’ll share my thoughts, fears, and views on working for an open-source product.

Transcript

1. Community based Design EMANUELA DAMIANI ~ FLOWCON ~ NOVEMBER 27, 2018
2. Take something and make it your own
3. 2 years ago…
4. I got the job!
5. Yep, I looked up on the Internet.
6. “ ghacks article July 29, 2013 So this is your idea of a great user interface, Mozilla?
7. “ A random guy on reddit 5 years ago Is it just me or has Firefox become a piece of sh*t?
9. ROUNDED CORNERS — TABS ON TOP
10. TABS
11. TOOLBAR TOOLBAR TOOLBAR TOOLBAR TOOLBAR
13. Those people have been nasty because they were in pain.
14. Emanuela @brassy Working at UX designer for
15. 17% of market share in France StatCounter Global Stats Desktop Browser Market Share in France - October 2018
16. How many of you are using Firefox?
18. There is a problem when we talk about design
19. What process apply? Who does take the decision?
20. It seems easier with code
21. Peer programming 
 and code review culture
22. On/Off Paradox
24. “ Not to diminish the great work by @elioqoshi but is there anyone else whom has graphical talents and want to do a proposal for a logo?
25. “ I still would love to get a real designer to make sure it (type) is near perfect.
27. Working in the open requires work
29. Resources Tools Platforms
30. Resources Tools Platforms
31. Resourcers
 to re-use what is here already
32. Design System, 
 a product servings other products
33. Does your company have a pattern library or a style guide?
34. Make the right choice the easiest choice
35. tweet…
36. Design System is a shared language
37. Increase collaboration
40. Resources Tools Platforms
41. Tools
 to create new things
42. design tokens, design decisions make it easy to implement
43. Design Decision
44. Design Decision token data (.JSON)
45. iOS Web token data (.JSON) token data (.xml) Android token as variables (.sass) Design Decision token as variables (.css)
46. iOS Web token data (.JSON) 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) Design Decision
47. 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)
49. Not just code
52. Resources Tools Platforms
53. Platforms
 where communicate
54. Blogs Bug trackers Social Networks
55. Reddit
56. GitHub
57. Bugzilla
58. Bugzilla
59. Bugzilla
60. Communication is the key
61. Listen to the user. Sure, but how?
62. Co-participatory design
63. “ Nick Fury UX Practitioner, Former director of S.H.I.E.L.D. The idea was to bring together a group of remarkable people, see if they could become something more. Photo by Daria Nepriakhina on Unsplash
64. Resources Tools Platforms
66. UX team Product Community
67. More than empathy
69. Identify where opportunities are
71. Explore solutions together
73. Getting uncomfortable
75. Document everything!
77. Build your product
80. Build your community
81. FIND ME ON TWITTER: @BRASSY Merci! Questions?