Second Toyota Paradox: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
https://sloanreview.mit.edu/article/the-second-toyota-paradox-how-delaying-decisions-can-make-better-cars-faster/ | https://sloanreview.mit.edu/article/the-second-toyota-paradox-how-delaying-decisions-can-make-better-cars-faster/ | ||
Also known as [[Set-Based Concurrent Engineering]] | Also known as [[Set-Based Concurrent Engineering]]. It is not a linear process - all steps are done at the same time as Concurrent Engineering implies. | ||
For open source product development, modular breakdown and concurrent engineering are kit. Mix in a dash of the Second Toyota Paradox - and we have the most rapid and efficient development method. | |||
It is about delaying decisions by evaluating sets of prototypes. It involves excessive prototyping. | It is about delaying decisions by evaluating sets of prototypes. It involves excessive prototyping. | ||
Revision as of 14:30, 10 September 2019
Also known as Set-Based Concurrent Engineering. It is not a linear process - all steps are done at the same time as Concurrent Engineering implies.
For open source product development, modular breakdown and concurrent engineering are kit. Mix in a dash of the Second Toyota Paradox - and we have the most rapid and efficient development method.
It is about delaying decisions by evaluating sets of prototypes. It involves excessive prototyping.