Collaboration Architecture 101 - Revision history

Marcin: /* Links */

2024-12-21T03:41:35Z

Links

← Older revision		Revision as of 03:41, 21 December 2024
Line 33:		Line 33:

	=Links=		=Links=
	*[[Collaboration Architecture~~#Summary~~]]		*[[Collaboration Architecture]]. Includes many links.
	*[[Collaborative Literacy]]		*[[Collaborative Literacy]]

Marcin: /* Links */

2024-12-21T03:40:55Z

Links

← Older revision		Revision as of 03:40, 21 December 2024
Line 34:		Line 34:
	=Links=		=Links=
	*[[Collaboration Architecture#Summary]]		*[[Collaboration Architecture#Summary]]
			*[[Collaborative Literacy]]

Marcin: /* Tactical */

2024-12-21T03:40:39Z

Tactical

← Older revision		Revision as of 03:40, 21 December 2024
Line 24:		Line 24:
	*Think at all times how this will be applied by the [[Man in the Arena]]. Become the Man in the Arena.		*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.		*Design for everyone, as we are all in it together.

			=Practical=
			*Use [[Atomic Design]]. Develop shared understanding for how this is done.
			*Use simple process, in such a fashion that any newcomer can start contributing to process complexity with minimal onboarding time. Ideally, novices enter and adapt for cohort capacity immediately.

	=Details of Competency=		=Details of Competency=

Marcin: /* Tactical */

2024-12-08T02:04:02Z

Tactical

← Older revision		Revision as of 02:04, 8 December 2024
Line 24:		Line 24:
	*Think at all times how this will be applied by the [[Man in the Arena]]. Become the Man in the Arena.		*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.		*Design for everyone, as we are all in it together.

			=Details of Competency=
			*Once you can include comprehensive vBOMs, you understand the component use [https://docs.google.com/presentation/d/1IglMwlvzJzA5S6ePZJcBh-0rtOnXw41Hl-RiOQfvbNk/edit#slide=id.g320d1c18e73_0_0]

	=Links=		=Links=
	*[[Collaboration Architecture#Summary]]		*[[Collaboration Architecture#Summary]]

Marcin: /* Tactical */

2024-12-07T00:29:44Z

Tactical

← Older revision		Revision as of 00:29, 7 December 2024
Line 22:		Line 22:
	*Use automation and open information for replicability		*Use automation and open information for replicability
	*Think at all times how an unlimited number of people can participate		*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]]		*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.

	=Links=		=Links=
	*[[Collaboration Architecture#Summary]]		*[[Collaboration Architecture#Summary]]

Marcin: /* Mundane Ascpects */

2024-12-07T00:29:15Z

Mundane Ascpects

← Older revision		Revision as of 00:29, 7 December 2024
Line 2:		Line 2:
	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.		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 ~~Ascpects~~=		=Mundane Aspects=
	*Development can apply to technology artifacts, to culture, economies, to institutions, to anything.		*Development can apply to technology artifacts, to culture, economies, to institutions, to anything.
	*For products, standard techniques of [[Product Development]] are used.		*For products, standard techniques of [[Product Development]] are used.
Line 13:		Line 13:
	*Then we document the technical aspects using wikis, cloud editable documents, file repos, CAD, computer code for automation, etc.		*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.		*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]]

	=Links=		=Links=
	*[[Collaboration Architecture#Summary]]		*[[Collaboration Architecture#Summary]]

Marcin: /* Mundane Ascpects */

2024-12-07T00:27:04Z

Mundane Ascpects

← Older revision		Revision as of 00:27, 7 December 2024
Line 8:		Line 8:
	*For culture, the approach is new ways of doing things, etc.		*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]]		*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, construction sets for technology, mental models of philosophy for ~~insitution~~, etc.		*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.		*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.

	=Links=		=Links=
	*[[Collaboration Architecture#Summary]]		*[[Collaboration Architecture#Summary]]

Marcin: /* Mundane Ascpects */

2024-12-07T00:24:11Z

Mundane Ascpects

← Older revision		Revision as of 00:24, 7 December 2024
Line 9:		Line 9:
	*In all cases, we break down the field of endeavor into parts, as in [[Modular Design]]		*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, construction sets for technology, mental models of philosophy for insitution, etc.		*For all cases, we look for primitive elements, such as phonics for learning reading, pattern languages for design, construction sets for technology, mental models of philosophy for insitution, etc.
	*We [[Time-Bind]], or stand on the shoulders of giants. Hence [[History]] of everything and a study of industry standards ~~helps~~.		*We [[Time-Bind]], or stand on the shoulders of giants. Hence [[History]] of everything and a study of industry standards is a helpful beginning.

	=Links=		=Links=
	*[[Collaboration Architecture#Summary]]		*[[Collaboration Architecture#Summary]]

Marcin: /* Mundane Ascpects */

2024-12-07T00:23:47Z

Mundane Ascpects

← Older revision		Revision as of 00:23, 7 December 2024
Line 9:		Line 9:
	*In all cases, we break down the field of endeavor into parts, as in [[Modular Design]]		*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, construction sets for technology, mental models of philosophy for insitution, etc.		*For all cases, we look for primitive elements, such as phonics for learning reading, pattern languages for design, construction sets for technology, mental models of philosophy for insitution, etc.
	*We [[Time Bind]], or stand on the shoulders of giants. Hence [[History]] of everything and a study of industry standards helps.		*We [[Time-Bind]], or stand on the shoulders of giants. Hence [[History]] of everything and a study of industry standards helps.

	=Links=		=Links=
	*[[Collaboration Architecture#Summary]]		*[[Collaboration Architecture#Summary]]

Marcin: /* Technique */

2024-12-07T00:23:25Z

Technique

← Older revision		Revision as of 00:23, 7 December 2024
Line 2:		Line 2:
	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.		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 Ascpects=
			*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, construction sets for technology, mental models of philosophy for insitution, etc.
			*We [[Time Bind]], or stand on the shoulders of giants. Hence [[History]] of everything and a study of industry standards helps.

	=Links=		=Links=
	*[[Collaboration Architecture#Summary]]		*[[Collaboration Architecture#Summary]]