Collaboration Architecture 101
Technique
Starting with Principles of Collaborative Literacy, we see a need for true collaboration. Once this happens, we seek out the technical skills. At OSE, the practical aspect means large-scale collaborative development of culture and institutions via knowhow. Knowhow is the technology or howto of executing ideas. If grounded in moral intelligence, humane progress follows. Such as Drucker, who was on a quest to make enterprise both efficient and humane, or social leaders such as Douglass who sought to end slavery. Today man is still fighting the machine, proverbially and literally, thus the need for true collaboration in the modern day.
Mundane Aspects
- Development can apply to technology artifacts, to culture, economies, to institutions, to anything.
- For products, standard techniques of Product Development are used.
- For economies, the product may be Open Sector Enterprise
- For culture, the approach is new ways of doing things, etc.
- In all cases, we break down the field of endeavor into parts, as in Modular Design
- For all cases, we look for primitive elements, such as phonics for learning reading, pattern languages for design, architectures, algorithms, construction sets for technology, mental models of philosophy for institutions, etc.
- We Time-Bind, or stand on the shoulders of giants. Hence History of everything and a study of industry standards is a helpful beginning.
- With a breakdown, we can start developing the parts, knowing that we are developing Complex Systems, and thus a comprehensive, interdisciplinary, inclusive, intersectoral, open, collaborative, holistic method must be used
- Then we document the technical aspects using wikis, cloud editable documents, file repos, CAD, computer code for automation, etc.
- We generate libraries and construction sets, so many physical or cultural artifacts/products can be designed.
Tactical
- Build information architecture skeleton.
- Document
- Keep breaking things down into smaller parts, while keeping the whole in mind
- Invite an open process
- Make it scalable, fractal
- Use automation and open information for replicability
- Think at all times how an unlimited number of people can participate
- Think at all times how this will be applied by the Man in the Arena. Become the Man in the Arena.
- Design for everyone, as we are all in it together.
Details of Competency
- Once you can include comprehensive vBOMs, you understand the component use [1]
