Hi, I’m Mushon



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




                          @Mushon....
-
-
-
-
e happe ns here
Ope n Sourc




}
            -
1. Motivation
1. Motivation



• Code - low costs for collaboration
1. Motivation



• Code - low costs for collaboration
• Chicken & Egg - Designers don’t use OSS
2. Process
2. Process

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

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

• Allows for varie...
2. Process

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

• Allows for varie...
2. Process

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

• Allows for varie...
2. Process

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

• Allows for varie...
2. Process

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

• Allows for varie...
3. Language

A                 B
A
            A


        A



A   A
Encoding
Encoding



• Defining a language (code) is key
Encoding



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



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


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


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

• Inconsistency in design fr...
Decoding


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

• Inconsistency in design fr...
So is it simply undoable?
(would I be wasting your time if I thought so?)
Fixing it: 1. Motivation
Fixing it: 1. Motivation



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



• We can’t force the use of bad tools
• Some success mainly code-based
  (webdesign / Wordpres...
Fixing it: 2. Process
Fixing it: 2. Process



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



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



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

Collaborative Encoding:
Fixing it:
  3. Language

  Collaborative Encoding:

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

  Collaborative Encoding:

• 1st step:
  Conduct a networked research

• 2nd step:
  Define an ex...
Fixing it:
  3. Language

  Collaborative Encoding:

• 1st step:
  Conduct a networked research

• 2nd step:
  Define an ex...
Fixing it:
3. Language
Fixing it:
3. Language
Collaborative Decoding:
Fixing it:
  3. Language
  Collaborative Decoding:

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

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

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

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

• Some design decisions are rational:
   • UX research
   • Technical ...
Leadership   or   Openness
A nuanced analysis of OS:
Leadership + Openness




    -
We can’t just sprinkle design
with the magic pixie dust of
       “Open Source”
Collaboration is hard!
Let’s make it easier.
    Suggestions?
@Mushon.com Nov 09
Open Source Design at Ignite lightning talk
Open Source Design at Ignite lightning talk
Open Source Design at Ignite lightning talk
Open Source Design at Ignite lightning talk
Open Source Design at Ignite lightning talk
Open Source Design at Ignite lightning talk
Open Source Design at Ignite lightning talk
Open Source Design at Ignite lightning talk
Open Source Design at Ignite lightning talk
Open Source Design at Ignite lightning talk
Open Source Design at Ignite lightning talk
Open Source Design at Ignite lightning talk
Open Source Design at Ignite lightning talk
Upcoming SlideShare
Loading in …5
×

Open Source Design at Ignite lightning talk

1,556 views
1,495 views

Published on

A narrated ignite (lightning-talk) version of the more extended talk I gave at Wordcamp NYC 2009 (available here: http://www.slideshare.net/mushon/beyond-sharing-open-source-design)

Published in: Design, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,556
On SlideShare
0
From Embeds
0
Number of Embeds
302
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Open Source Design at Ignite lightning talk

    1. 1. Hi, I’m Mushon @Mushon.com Nov 09
    2. 2. www.shual.com
    3. 3. Beyond Sharing: “Open Source Design” Wordcamp NYC 2009 (short version) @Mushon.com Nov 09
    4. 4. -
    5. 5. -
    6. 6. -
    7. 7. -
    8. 8. e happe ns here Ope n Sourc } -
    9. 9. 1. Motivation
    10. 10. 1. Motivation • Code - low costs for collaboration
    11. 11. 1. Motivation • Code - low costs for collaboration • Chicken & Egg - Designers don’t use OSS
    12. 12. 2. Process
    13. 13. 2. Process • In coding (software) and writing (wikis): G-R-A-N-U-L-A-R building block - a character
    14. 14. 2. Process • In coding (software) and writing (wikis): G-R-A-N-U-L-A-R building block - a character • Allows for varied contribution:
    15. 15. 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
    16. 16. 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
    17. 17. 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
    18. 18. 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
    19. 19. 3. Language A B
    20. 20. A A A A A
    21. 21. Encoding
    22. 22. Encoding • Defining a language (code) is key
    23. 23. Encoding • Defining a language (code) is key • Try Coding without choosing a language
    24. 24. Encoding • Defining a language (code) is key • Try Coding without choosing a language • Standardization VS. Innovation
    25. 25. Decoding
    26. 26. Decoding • Code either executes or it doesn’t, but a message interpretation isn’t binary
    27. 27. 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)
    28. 28. 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
    29. 29. So is it simply undoable? (would I be wasting your time if I thought so?)
    30. 30. Fixing it: 1. Motivation
    31. 31. Fixing it: 1. Motivation • We can’t force the use of bad tools
    32. 32. Fixing it: 1. Motivation • We can’t force the use of bad tools • Some success mainly code-based (webdesign / Wordpress)
    33. 33. Fixing it: 2. Process
    34. 34. Fixing it: 2. Process • Put all master files online
    35. 35. Fixing it: 2. Process • Put all master files online • Explore versioning tools for design
    36. 36. Fixing it: 2. Process • Put all master files online • Explore versioning tools for design • Use Code (when possible)
    37. 37. Fixing it: 3. Language
    38. 38. Fixing it: 3. Language Collaborative Encoding:
    39. 39. Fixing it: 3. Language Collaborative Encoding: • 1st step: Conduct a networked research
    40. 40. Fixing it: 3. Language Collaborative Encoding: • 1st step: Conduct a networked research • 2nd step: Define an extensible language (like in CSS)
    41. 41. 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
    42. 42. Fixing it: 3. Language
    43. 43. Fixing it: 3. Language Collaborative Decoding:
    44. 44. Fixing it: 3. Language Collaborative Decoding: • Some design decisions are rational:
    45. 45. Fixing it: 3. Language Collaborative Decoding: • Some design decisions are rational: • UX research
    46. 46. Fixing it: 3. Language Collaborative Decoding: • Some design decisions are rational: • UX research • Technical aspects of design
    47. 47. 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...)
    48. 48. 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
    49. 49. Leadership or Openness
    50. 50. A nuanced analysis of OS: Leadership + Openness -
    51. 51. We can’t just sprinkle design with the magic pixie dust of “Open Source”
    52. 52. Collaboration is hard! Let’s make it easier. Suggestions?
    53. 53. @Mushon.com Nov 09

    ×