Communication Guidelines: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
*Fundamental problem solving approach: When communicating, provide potential solutions instead of statements of why something may not work. Negative comments do not imply a solution. | *Fundamental problem solving approach: When communicating, provide potential solutions instead of statements of why something may not work. Negative comments do not imply a solution. | ||
*Do background research: before critiquing OSE work, find out the rationale and requirements for OSE's design choices. While your comments may be useful in usual situations, they may not be applicable to OSE's work due to its unique design constraints of test-driven [[Extreme Manufacturing]] approach, and [[Product Ecologies]]. | *Do background research: before critiquing OSE work, find out the rationale and requirements for OSE's design choices. While your comments may be useful in usual situations, they may not be applicable to OSE's work due to its unique design constraints of modular, test-driven [[Extreme Manufacturing]] approach, and associated [[Product Ecologies]]. | ||
Latest revision as of 21:43, 3 October 2014
When communicating with or about OSE or on its channels, we encourage these values:
- Fundamental problem solving approach: When communicating, provide potential solutions instead of statements of why something may not work. Negative comments do not imply a solution.
- Do background research: before critiquing OSE work, find out the rationale and requirements for OSE's design choices. While your comments may be useful in usual situations, they may not be applicable to OSE's work due to its unique design constraints of modular, test-driven Extreme Manufacturing approach, and associated Product Ecologies.