Hiking, Superstitious Mountains, Arizona 2016

Iterative Book Production Manifesto

Something I wrote in 2012 for FLOSS Manuals and updated recently to:
https://github.com/greyscalepress/manifestos

We value:

  1. Contributors and facilitators over ‘editors’ and ‘authors’
  2. Collaboration over individualised production
  3. Here and now production over sometime soon production
  4. Meaningful credit for all contributors over single author attribution

Earlier iterations:
http://lists.flossmanuals.net/pipermail/discuss-flossmanuals.net/2012-June/007446.html
http://lists.flossmanuals.net/pipermail/discuss-flossmanuals.net/2012-June/007465.html
http://blog.booki.cc/2012/06/iterative-book-development-manifesto/
https://web.archive.org/web/20131225055321/http://blog.booki.cc/2012/06/iterative-book-development-manifesto/

book-development-manifesto

CPD – Collaborative Product Development

Scratch pad initial thoughts for CPD methodology

Guiding Rule

Diversity of Stakeholders + Collaboration = 
1. a better product
2. accelerated adoption

Requirements

  • product flexability
  • facilitator

Origin Steps

  1. develop a Solution Proposition
  2. start initial design and development any way you can
  3. diversify the product development team as soon as possible to include designers, UX people, devs, users, potential users etc
  4. begin outward general communication

Collaborative Design Steps (cyclical)

  1. seek those interested in adopting
  2. include potential adopters in Collaborative Design Sessions
  3. make their contributions visible
  4. develop, test and use the product
  5. repeat

Discovering ba

I recently started researching what a better Open Source Software Development Lifecycle might look like. On the path, I am discovering so many amazing things. Including the work of Ikujiro Nonaka. The following quote from an article about him illustrates why I’m so excited by his work:

“Nonaka told his interviewer that they were creating ba, a Japanese term that describes a field or space where people freely and openly share what they know in the service of creating something new.

Ba resembles the concept of “flow” as set forth by psychologist Mihaly Csikszentmihalyi: It is the mental state that occurs when a person is fully immersed in whatever he or she is doing. But unlike flow, ba is never solitary; it exists among two or more people. As Nonaka says, “In ba, there is no you or me, there is only us, sharing a here-and-now relationship.” Ba can occur in a work group, a project team, an ad hoc meeting, a virtual e-mail list, or at the frontline point of contact with customers. It serves as a petri dish in which shared in­sights are cultivated and grown.

Companies can foster ba by designing processes that encourage people to think together. ”

http://www.strategy-business.com/article/08407?gko=a1212

Some Open Design Resources

Some stuff I found. More information coming.

http://opendesignnow.org/

http://openusability.org/

http://opendesign.foundation/

https://www.smashingmagazine.com/2010/09/the-case-for-open-source-design-can-design-by-committee-work/

https://github.com/opensourcedesign/resources

http://opensourcedesign.net/

https://24ways.org/2014/why-you-should-design-for-open-sourceb

Perhaps Stop Using ‘Non-code’? Whatayarekin?

It is a rampant meme – ‘non-code’. Used to describe contributions to open source projects that are not code.

This kind of language creates insider-outsider boundaries and will signal to anyone that isn’t a programmer that they are secondary citizens and that their contributions will be valued accordingly. Not very motivating.