Collaborative Efficiency: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 13: | Line 13: | ||
*Widsom Day - Learning How To Learn - You learn the method of [[Headwrapping]] using [[Mindmaps]] | *Widsom Day - Learning How To Learn - You learn the method of [[Headwrapping]] using [[Mindmaps]] | ||
*Design Days - [[Build Task Specifications]] clearly defined. | *Design Days - [[Build Task Specifications]] clearly defined. | ||
* | *Contribute to [[Pattern Language Libraries]] of open design - you do that as a team | ||
*Teacher and students collaborate. 2 levels of student (18 & 21 yo). Chance to level up at 3 levels. [[Leveling Up]] | |||
Latest revision as of 19:56, 3 September 2024
Characterisitcs of Collaborative Efficiency
- In design and builds, get more done, learn faster.
- Modularity teaches you communication and Collaborative Literacy
- Professionals create Pattern Language Libraries, not proprietary knowhow
- Product ecosystems make it easier to diversify
- Grow the pie, as opposed to take slices
5 Day Program: How to Insert Collaborative Efficiency
- 2 work days - in swarms of 24
- Module-based design means you are building Quad Modules
- Quad modules are easily convertable to kits
- Widsom Day - Learning How To Learn - You learn the method of Headwrapping using Mindmaps
- Design Days - Build Task Specifications clearly defined.
- Contribute to Pattern Language Libraries of open design - you do that as a team
- Teacher and students collaborate. 2 levels of student (18 & 21 yo). Chance to level up at 3 levels. Leveling Up