Iron Triangle - Revision history

Marcin: /* About */

2026-02-13T00:06:42Z

About

← Older revision		Revision as of 00:06, 13 February 2026
Line 8:		Line 8:
	*To have good - you need open source libre design.		*To have good - you need open source libre design.
	*To have speed - you need modularity and [[Extreme Design]], [[Integrated Design]].		*To have speed - you need modularity and [[Extreme Design]], [[Integrated Design]].
	*To have quality - you need good design. This comes from [[Lifetime Design]], [[Construction Set Design]], [[Product Ecologies]], [[Integrated Design]], [[Design For Disassembly]], [[Transparent Design]], [[Robustification]], and other aspects. All of these in one can be achieved through collaborative design, as opposed to proprietary barriers.		*To have quality - you need good design. This comes from [[Lifetime Design]], [[Construction Set Design]], [[Product Ecologies]], [[Integrated Design]], [[Design For Disassembly]], [[Transparent Design]], [[Robustification]], and other aspects. All of these in one can be achieved through collaborative design, as opposed to proprietary barriers. These properties are captured in [[OSE Specifications]].


	=OSE Case=		=OSE Case=

Marcin: /* OSE Case */

2026-02-13T00:05:41Z

OSE Case

← Older revision		Revision as of 00:05, 13 February 2026
Line 4:		Line 4:

	[[Image:fastcheapgreat.jpg]]		[[Image:fastcheapgreat.jpg]]

			=About=
			*To have good - you need open source libre design.
			*To have speed - you need modularity and [[Extreme Design]], [[Integrated Design]].
			*To have quality - you need good design. This comes from [[Lifetime Design]], [[Construction Set Design]], [[Product Ecologies]], [[Integrated Design]], [[Design For Disassembly]], [[Transparent Design]], [[Robustification]], and other aspects. All of these in one can be achieved through collaborative design, as opposed to proprietary barriers.


	=OSE Case=		=OSE Case=

	==Simply Put==		==Simply Put==
	The notion that a product or service cannot be optimized in all of its aspects is a clear example of scarcity thinking. Such thinking misses the point that open collaboration and development produces superior results. See [[Linux of Vaccines]] as a good and powerful example of breaking the iron triangle. OSE's [[Extreme Manufacturing]] and [[Extreme Enterprise]] models are examples where the Iron Triangle is smashed - with open collaboration.		The notion that a product or service cannot be optimized in all of its aspects is a clear example of scarcity thinking. Such thinking misses the point that open collaboration and development produces superior results. See [[Linux of Vaccines]] as a good and powerful example of breaking the iron triangle. OSE's [[Extreme Manufacturing]] and [[Extreme Enterprise]] models are examples where the Iron Triangle is smashed - with open collaboration.

Marcin: /* How */

2023-08-22T18:02:21Z

How

← Older revision		Revision as of 18:02, 22 August 2023
Line 40:		Line 40:
	#[[Second Toyota Paradox]].		#[[Second Toyota Paradox]].
	#[[Degeneracy]] to one - not one item but one [[Construction Set]]		#[[Degeneracy]] to one - not one item but one [[Construction Set]]

			=Links=
			*[[OSE School]]

Marcin: /* How */

2023-08-22T17:56:16Z

How

← Older revision		Revision as of 17:56, 22 August 2023
Line 39:		Line 39:
	#[[DfM]], [[DfD]]		#[[DfM]], [[DfD]]
	#[[Second Toyota Paradox]].		#[[Second Toyota Paradox]].
	#[[Degeneracy]] to one - but one [[Construction Set]]		#[[Degeneracy]] to one - not one item but one [[Construction Set]]

Marcin: /* How */

2023-08-22T17:56:00Z

How

← Older revision		Revision as of 17:56, 22 August 2023
Line 39:		Line 39:
	#[[DfM]], [[DfD]]		#[[DfM]], [[DfD]]
	#[[Second Toyota Paradox]].		#[[Second Toyota Paradox]].
			#[[Degeneracy]] to one - but one [[Construction Set]]

Marcin: /* Technically Speaking */

2023-08-22T17:54:49Z

Technically Speaking

← Older revision		Revision as of 17:54, 22 August 2023
Line 19:		Line 19:

	Lowered development costs for optimizing design, and [[Technological Recursion]] down to producing raw materials - makes things cheap.		Lowered development costs for optimizing design, and [[Technological Recursion]] down to producing raw materials - makes things cheap.

			[[Degeneracy]], [[Modularity]], and [[Lifetime Design]] make things 100x cheaper.

			[[Swarm Builds]] make things 10x faster.
			Open collaborative design makes things 10x better.

	=How=		=How=

Marcin: /* How */

2023-05-29T01:22:39Z

How

← Older revision		Revision as of 01:22, 29 May 2023
Line 32:		Line 32:
	#[[Tech Recursion]] up to 'free' materials		#[[Tech Recursion]] up to 'free' materials
	#[[Product Ecologies]] fro integration into a larger ecosystem		#[[Product Ecologies]] fro integration into a larger ecosystem
	#[[DfM]]		#[[DfM]], [[DfD]]
			#[[Second Toyota Paradox]].

Marcin: /* How */

2023-05-29T01:21:54Z

How

← Older revision		Revision as of 01:21, 29 May 2023
Line 31:		Line 31:
	#Consider the integrated process of [[CAD-BOM-Build]] that comes from build experience, then design experience, then enterprise experience.		#Consider the integrated process of [[CAD-BOM-Build]] that comes from build experience, then design experience, then enterprise experience.
	#[[Tech Recursion]] up to 'free' materials		#[[Tech Recursion]] up to 'free' materials
			#[[Product Ecologies]] fro integration into a larger ecosystem
			#[[DfM]]

Marcin: /* How */

2023-05-29T01:21:26Z

How

← Older revision		Revision as of 01:21, 29 May 2023
Line 30:		Line 30:
	#Focus on open design and collaboration as an advantage		#Focus on open design and collaboration as an advantage
	#Consider the integrated process of [[CAD-BOM-Build]] that comes from build experience, then design experience, then enterprise experience.		#Consider the integrated process of [[CAD-BOM-Build]] that comes from build experience, then design experience, then enterprise experience.
			#[[Tech Recursion]] up to 'free' materials

Marcin: /* How */

2023-05-29T01:20:58Z

How

← Older revision		Revision as of 01:20, 29 May 2023
Line 29:		Line 29:
	#Focus on environmentally sound practice		#Focus on environmentally sound practice
	#Focus on open design and collaboration as an advantage		#Focus on open design and collaboration as an advantage
			#Consider the integrated process of [[CAD-BOM-Build]] that comes from build experience, then design experience, then enterprise experience.