Mushon discusses open source design and how to make collaboration on design easier. Some key challenges are that designers don't commonly use open source like developers do and that inconsistent design fragments the message. Mushon proposes putting all master files online, exploring versioning tools for design, using code when possible, conducting research to define an extensible design language, documenting the language, sharing resources through blogs, and recognizing that both leadership and openness are needed for open source to work for design. The goal is to make collaborative design easier through establishing common processes and standards.

1. Hi, I’m Mushon
@Mushon.com Nov 09

2. www.shual.com

7. Beyond Sharing:
“Open Source Design”
Wordcamp NYC 2009
(short version)
@Mushon.com Nov 09

10. -

11. -

12. -

15. -

16. e happe ns here
Ope n Sourc
}
-

17. 1. Motivation

18. 1. Motivation
• Code - low costs for collaboration

19. 1. Motivation
• Code - low costs for collaboration
• Chicken & Egg - Designers don’t use OSS

20. 2. Process

21. 2. Process
• In coding (software) and writing (wikis):
G-R-A-N-U-L-A-R building block - a character

22. 2. Process
• In coding (software) and writing (wikis):
G-R-A-N-U-L-A-R building block - a character
• Allows for varied contribution:

23. 2. Process
• In coding (software) and writing (wikis):
G-R-A-N-U-L-A-R building block - a character
• Allows for varied contribution:
• Accessible ladder of contribution

24. 2. Process
• In coding (software) and writing (wikis):
G-R-A-N-U-L-A-R building block - a character
• Allows for varied contribution:
• Accessible ladder of contribution
• History

25. 2. Process
• In coding (software) and writing (wikis):
G-R-A-N-U-L-A-R building block - a character
• Allows for varied contribution:
• Accessible ladder of contribution
• History
• Moderation

26. 2. Process
• In coding (software) and writing (wikis):
G-R-A-N-U-L-A-R building block - a character
• Allows for varied contribution:
• Accessible ladder of contribution
• History
• Moderation
• Transparency

27. 3. Language
A B

28. A
A
A
A A

29. Encoding

30. Encoding
• Defining a language (code) is key

31. Encoding
• Defining a language (code) is key
• Try Coding without choosing a language

32. Encoding
• Defining a language (code) is key
• Try Coding without choosing a language
• Standardization VS. Innovation

33. Decoding

34. Decoding
• Code either executes or it doesn’t,
but a message interpretation isn’t binary

35. Decoding
• Code either executes or it doesn’t,
but a message interpretation isn’t binary
• Inconsistency in design fragments the
message (our brains can’t really multitask)

36. Decoding
• Code either executes or it doesn’t,
but a message interpretation isn’t binary
• Inconsistency in design fragments the
message (our brains can’t really multitask)
• Wikipedia’s has a largely rational guidelines

37. So is it simply undoable?
(would I be wasting your time if I thought so?)

43. Fixing it: 1. Motivation

44. Fixing it: 1. Motivation
• We can’t force the use of bad tools

45. Fixing it: 1. Motivation
• We can’t force the use of bad tools
• Some success mainly code-based
(webdesign / Wordpress)

46. Fixing it: 2. Process

47. Fixing it: 2. Process
• Put all master files online

48. Fixing it: 2. Process
• Put all master files online
• Explore versioning tools for design

49. Fixing it: 2. Process
• Put all master files online
• Explore versioning tools for design
• Use Code (when possible)

50. Fixing it:
3. Language

51. Fixing it:
3. Language
Collaborative Encoding:

52. Fixing it:
3. Language
Collaborative Encoding:
• 1st step:
Conduct a networked research

53. Fixing it:
3. Language
Collaborative Encoding:
• 1st step:
Conduct a networked research
• 2nd step:
Define an extensible language (like in CSS)

54. Fixing it:
3. Language
Collaborative Encoding:
• 1st step:
Conduct a networked research
• 2nd step:
Define an extensible language (like in CSS)
• 3rd step:
Document the language

55. Fixing it:
3. Language

56. Fixing it:
3. Language
Collaborative Decoding:

57. Fixing it:
3. Language
Collaborative Decoding:
• Some design decisions are rational:

58. Fixing it:
3. Language
Collaborative Decoding:
• Some design decisions are rational:
• UX research

59. Fixing it:
3. Language
Collaborative Decoding:
• Some design decisions are rational:
• UX research
• Technical aspects of design

60. Fixing it:
3. Language
Collaborative Decoding:
• Some design decisions are rational:
• UX research
• Technical aspects of design
• Design best practices (in typography, use
of icons, interaction paradigms...)

61. Fixing it:
3. Language
Collaborative Decoding:
• Some design decisions are rational:
• UX research
• Technical aspects of design
• Design best practices (in typography, use
of icons, interaction paradigms...)
• Blogs share resources and documentation

62. Leadership or Openness

63. A nuanced analysis of OS:
Leadership + Openness
-

64. We can’t just sprinkle design
with the magic pixie dust of
“Open Source”

65. Collaboration is hard!
Let’s make it easier.
Suggestions?

66. @Mushon.com Nov 09