Line 18: | Line 18: | ||
<h3>Summary of Integrated Human Practices</h3> | <h3>Summary of Integrated Human Practices</h3> | ||
</br> | </br> | ||
− | <p1>In order to identify potential issues and applications of our system, we engaged in direct dialogue with stakeholders, as per the <b><a href="https://2018.igem.org/Team:Imperial_College/scicomm">Communication Strategies Guide (CSG)</a></b>. This approach allowed us to devise potential applications for our system, as well as correct design flaws such as the use of toxic pyocyanin as a redox-cycling molecule. This led us to repurpose our system with a safer molecule (phenazine methosulfate -PMS-), which also resulted in being a cheaper inducer molecule even when compared with broadly used inducers. We also identified that internal friction in teams is a common issue as proven to us by our experience as well as a survey that we conducted amongst 67 iGEM members from 14 other teams. To address this issue we developed our <b>team communication app (LTAT)</b> to help improve team communication both internally and in other teams. </p1> | + | <p1>In order to identify potential issues and applications of our system, we engaged in direct dialogue with stakeholders, as per the <b><a href="https://2018.igem.org/Team:Imperial_College/scicomm">Communication Strategies Guide (CSG)</a></b>. This approach allowed us to devise potential applications for our system, as well as correct design flaws such as the use of toxic pyocyanin as a redox-cycling molecule. This led us to repurpose our system with a safer molecule (phenazine methosulfate -PMS-), which also resulted in being a cheaper inducer molecule even when compared with broadly used inducers. We also identified that internal friction in teams is a common issue as proven to us by our experience as well as a survey that we conducted amongst 67 iGEM members from 14 other teams. To address this issue we developed our <a href="https://2018.igem.org/Team:Imperial_College/ltat"><b>team communication app (LTAT)</b></a> to help improve team communication both internally and in other teams. </p1> |
</br> | </br> | ||
<h3>Safety</h3> | <h3>Safety</h3> |
Revision as of 22:51, 16 October 2018