baloise
Chapter in the Open Organization books series
@semioticrobotic and I spoke yesterday about the possibility of turning this #127 / #171 presentation into a future chapter in the Open Organization books series, which we would very much like to explore!
From an email I sent to @MarkusTiede yesterday (logging here for visibility):
I especially like the part of the talk outline that reads:
Our Reasons
- as an individual: (intrinsic) motivation
- as a team: constant learning
- as a department: sharing / reducing costs, reducing (vendor) lock-in risk(s)
- as an insurer: attractive employer
- as a group: inner-sourcing <-> open-sourcing
This seems (to me, anyway) a critical part of the organization's story, because it speaks to more than just the technical benefits of using open source software. It speaks to the benefits of embracing open principles across the enterprise more broadly. That's exactly what the Open Organization community is always exploring and I'd love to hear more of your take on it. What, in other words, can someone in an industry with a reputation for being "closed" gain by making an effort to "open up"? I think this would make a helpful chapter for our readers and our broader community.
We can start doing that in a number of ways. If you have a more detailed outline you'd like to work on and review together, we can do that. Or, if you'd like to begin drafting something, we can collaborate on that, too. In the meantime, we can look over the existing books in the Open Organization series to decide which is the best "home" for your chapter, then open up an issue in the book's repository to indicate that we're working on a chapter for a future new version of the book.
