Difference between revisions of "Team:Imperial College/ltat"
| (19 intermediate revisions by the same user not shown) | |||
| Line 204: | Line 204: | ||
function endMessage(){ | function endMessage(){ | ||
if (answers[0] == document.getElementById("HR").getAttribute("statement")){ | if (answers[0] == document.getElementById("HR").getAttribute("statement")){ | ||
| − | document.getElementById("end_page").innerHTML = "Thank you for using LTAT to bring up your issue, press the | + | document.getElementById("end_page").innerHTML = "Thank you for using LTAT to bring up your issue, press the send button to submit your issue to HR and they will shortly get in contact to help facilitate resolving your problem." |
} | } | ||
else if (answers[0] == document.getElementById("Everyone").getAttribute("statement")){ | else if (answers[0] == document.getElementById("Everyone").getAttribute("statement")){ | ||
| − | document.getElementById("end_page").innerHTML = "Thank you for using LTAT to bring up your issue, press the | + | document.getElementById("end_page").innerHTML = "Thank you for using LTAT to bring up your issue, press the send button to notify your team of your issue, as well as HR who will get in contact to help facilitate resolving your problem" |
} | } | ||
else if (answers[0] == document.getElementById("Honchos").getAttribute("statement")){ | else if (answers[0] == document.getElementById("Honchos").getAttribute("statement")){ | ||
| − | document.getElementById("end_page").innerHTML = "Thank you for using LTAT to bring up your issue, press the | + | document.getElementById("end_page").innerHTML = "Thank you for using LTAT to bring up your issue, press the send button to submit your issue to the principal investigator and they should contact you shortly to help facilitate resolving your problem" |
} | } | ||
} | } | ||
| Line 1,389: | Line 1,389: | ||
<div class="Title"> | <div class="Title"> | ||
| − | <h1> | + | <h1 style="width:33%; color:#24305E;">Let's Talk About This</h1> |
| − | <p>Your aid for raising difficult but important conversations</p> | + | <p style="margin-top:50px; font-size:18px; color:#24305E;">Your aid for raising difficult but important conversations</p> |
</div> | </div> | ||
| Line 1,396: | Line 1,396: | ||
<div class="introBody"> | <div class="introBody"> | ||
| − | <p>Working in a team can have its challenge and sometimes be difficult. Opposing opinions, misunderstandings, lack of communication and personal issues can cause stress and conflict within a team, which is detrimental to the teams’ health and to the team’s success with regards to their project.</p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;">Working in a team can have its challenge and sometimes be difficult. Opposing opinions, misunderstandings, lack of communication and personal issues can cause stress and conflict within a team, which is detrimental to the teams’ health and to the team’s success with regards to their project.</p> |
| − | <p>These kinds of issues need to be addressed as early as possible, otherwise allowing such negative factors to fester in the team can have dire consequences, such as members outright fighting, or wishing to leave the team.</p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;">These kinds of issues need to be addressed as early as possible, otherwise allowing such negative factors to fester in the team can have dire consequences, such as members outright fighting, or wishing to leave the team.</p> |
| − | <p>One of the most effective methods for dealing with internal team pressure is simply to talk about them in the open. By speaking out loud and listening patiently, many conflicts and unnecessary stress can be avoided, improving the wellbeing of the individual, as well as benefiting the whole team. </p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;">One of the most effective methods for dealing with internal team pressure is simply to talk about them in the open. By speaking out loud and listening patiently, many conflicts and unnecessary stress can be avoided, improving the wellbeing of the individual, as well as benefiting the whole team. </p> |
| − | <p>However, starting these kinds of conversations can be quite awkward and difficult, especially in the beginning of a project where everyone is new and the team members do not know each other very well. This lack of communication can lead to issues being bottled up, causing stress and frustrations that lead to arguments and loss of productivity, which is unhealthy for the individual and the team. </p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;">However, starting these kinds of conversations can be quite awkward and difficult, especially in the beginning of a project where everyone is new and the team members do not know each other very well. This lack of communication can lead to issues being bottled up, causing stress and frustrations that lead to arguments and loss of productivity, which is unhealthy for the individual and the team. </p> |
| − | <p>To help initiate conversations about issues within a team, we decided upon our solution, Let’s Talk About This (LTAT). </p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;">To help initiate conversations about issues within a team, we decided upon our solution, Let’s Talk About This (LTAT). </p> |
| − | <p>There are two key elements to LTAT:</p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;">There are two key elements to LTAT:</p> |
<div class="ltat_twoElements" > | <div class="ltat_twoElements" > | ||
| − | <h1>Human Resources</h1> | + | <h1 style="color:#24305E;">Human Resources</h1> |
| − | <p>We thought that each team should have their own Human Resources (HR) person, who is elected by the team. The HR’s role would be to act as a listener and mediator of issues that are raised in the team. They would help solve issues where they can or involve more appropriate parties where they see fit.</p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;">We thought that each team should have their own Human Resources (HR) person, who is elected by the team. The HR’s role would be to act as a listener and mediator of issues that are raised in the team. They would help solve issues where they can or involve more appropriate parties where they see fit.</p> |
| − | <h1>The LTAT web application</h1> | + | <h1 style="color:#24305E;">The LTAT web application</h1> |
| − | <p>communicating one’s issues can be awkward, even to someone dedicated to listening to these kinds of things. It can also be difficult to break down your own problems and think of them objectively. Also, having to use a personal communication channel (such text or email) to raise an issue can be intimidating, especially if the user is unsure or nervous. We decided that a level and unbiased platform for specifically communicating issues is needed, on which a user is assisted in objectively breaking down their problem, and they should be able to access and use the platform with ease. Furthermore, we want the HR to receive the message in a way they can efficiently and effectively understand the problem. </p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;">communicating one’s issues can be awkward, even to someone dedicated to listening to these kinds of things. It can also be difficult to break down your own problems and think of them objectively. Also, having to use a personal communication channel (such text or email) to raise an issue can be intimidating, especially if the user is unsure or nervous. We decided that a level and unbiased platform for specifically communicating issues is needed, on which a user is assisted in objectively breaking down their problem, and they should be able to access and use the platform with ease. Furthermore, we want the HR to receive the message in a way they can efficiently and effectively understand the problem. </p> |
</div> | </div> | ||
| − | <p style="margin-top:24px;">The LTAT web app is a tool to raise an issue in a discrete and orderly manner. It is up to the user and the HR to meet in person, with other relevant parties, to discuss the issue further and resolve it in person. </p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;margin-top:24px;">The LTAT web app is a tool to raise an issue in a discrete and orderly manner. It is up to the user and the HR to meet in person, with other relevant parties, to discuss the issue further and resolve it in person. </p> |
| Line 1,423: | Line 1,423: | ||
<div class="breaker"></div> | <div class="breaker"></div> | ||
<div class="bodyBlock"> | <div class="bodyBlock"> | ||
| − | <h1>But first, is LTAT really needed?</h1> | + | <h1 style="color:#24305E">But first, is LTAT really needed?</h1> |
| − | <p>Before going into making our LTAT app, we needed to confirm that something like LTAT is needed in the real world, and whether other teams would find it useful. We contacted several iGEM teams from all over the world to fill out our survey, in which we asked individuals general questions about their team management system and about issues they have within their team. Through our survey we wanted to confirm two key things. First, do <span1 class="toolTip">individuals | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;">Before going into making our LTAT app, we needed to confirm that something like LTAT is needed in the real world, and whether other teams would find it useful. We contacted several iGEM teams from all over the world to fill out our survey, in which we asked individuals general questions about their team management system and about issues they have within their team. Through our survey we wanted to confirm two key things. First, do <span1 class="toolTip">individuals |
<span class="toolTipText"><b>Why individuals?</b> <br> The app is to be used by individuals to communicate issues with the team, therefore it is best to get an idea of issues faced in other teams from an individual’s perspective. Furthermore, this allows the individual filling our survey to be more comfortable about honestly answering the questions, rather than feeling pressured into choosing answers that creates a false-positive image of their team.</span> </span1> | <span class="toolTipText"><b>Why individuals?</b> <br> The app is to be used by individuals to communicate issues with the team, therefore it is best to get an idea of issues faced in other teams from an individual’s perspective. Furthermore, this allows the individual filling our survey to be more comfortable about honestly answering the questions, rather than feeling pressured into choosing answers that creates a false-positive image of their team.</span> </span1> | ||
in other teams feel like they have communication issues within their team, and secondly, whether LTAT would be able to help resolve these issues. A total of 68 individuals from 14 different teams responded to our survey, the results of which further motivated us to develop our app to completion.</p> | in other teams feel like they have communication issues within their team, and secondly, whether LTAT would be able to help resolve these issues. A total of 68 individuals from 14 different teams responded to our survey, the results of which further motivated us to develop our app to completion.</p> | ||
| − | <h2>Do other team's have communication issues?</h2> | + | <h2 style="color:#24305E;">Do other team's have communication issues?</h2> |
<div class="dataChart"> | <div class="dataChart"> | ||
| − | <h2>How often do you perceive communication issues within your team?</h2> | + | <h2 style="color:#24305E;">How often do you perceive communication issues within your team?</h2> |
| − | <h2>How often do you feel you have communication issues with your team?</h2> | + | <h2 style="color:#24305E;">How often do you feel you have communication issues with your team?</h2> |
<br> | <br> | ||
<img src="https://static.igem.org/mediawiki/2018/c/c1/T--Imperial_College--Issues_in_team.png" class="pieChart"> | <img src="https://static.igem.org/mediawiki/2018/c/c1/T--Imperial_College--Issues_in_team.png" class="pieChart"> | ||
| Line 1,440: | Line 1,440: | ||
</div> | </div> | ||
<br class="clr"> | <br class="clr"> | ||
| − | <p class="summary">These confirmed to us that individuals in other teams do perceive challenges and difficulties when it comes to communication. One fifth of the respondents believe that issues occur regularly is a considerable amount, and a total of 61.8% believing that there is at least one issue a week. Furthermore, slightly over half of the total respondents believe that they themselves have at least one communication issue a week. These data suggest that other iGEM teams also have communication issues and so LTAT could potentially be used by others. </p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;"class="summary">These confirmed to us that individuals in other teams do perceive challenges and difficulties when it comes to communication. One fifth of the respondents believe that issues occur regularly is a considerable amount, and a total of 61.8% believing that there is at least one issue a week. Furthermore, slightly over half of the total respondents believe that they themselves have at least one communication issue a week. These data suggest that other iGEM teams also have communication issues and so LTAT could potentially be used by others. </p> |
<div class="breaker"></div> | <div class="breaker"></div> | ||
| − | <h2>Would other teams be interested in LTAT?</h2> | + | <h2 style="color:#24305E">Would other teams be interested in LTAT?</h2> |
<div class="dataChart"> | <div class="dataChart"> | ||
| Line 1,454: | Line 1,454: | ||
</div> | </div> | ||
<br class="clr"> | <br class="clr"> | ||
| − | <p class="summary">These results showed some promise, as majority of individuals do agree that a dedicated HR could possibly be useful, but most of them are sceptical about how well it could be implemented by the team, which is a reasonable thought to have. However, one participant commented <i> “We've implemented this [HR] role this year and it has helped immensely, especially because our team is very large”</i>. This particular response was encouraging to hear and supported our belief that a dedicated HR in a group would be beneficial to everyone. It’s unfortunate that we couldn’t contact this individual further, as we the responses are recorded as anonymously.</p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;" class="summary">These results showed some promise, as majority of individuals do agree that a dedicated HR could possibly be useful, but most of them are sceptical about how well it could be implemented by the team, which is a reasonable thought to have. However, one participant commented <i> “We've implemented this [HR] role this year and it has helped immensely, especially because our team is very large”</i>. This particular response was encouraging to hear and supported our belief that a dedicated HR in a group would be beneficial to everyone. It’s unfortunate that we couldn’t contact this individual further, as we the responses are recorded as anonymously.</p> |
<div class="breaker"></div> | <div class="breaker"></div> | ||
| − | <h2>In Summary...</h2> | + | <h2 style="color:#24305E">In Summary...</h2> |
| − | <p class="summary">From our survey we received confirmation that other teams also have communication issues and many individuals felt that they personally had some form of communication issue with their team. Furthermore, the responses to having a dedicated HR and a tool to communicate team issues through were positive, encouraging us that LTAT could be successful at helping initiating conversations about issues within a team.</p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;" class="summary">From our survey we received confirmation that other teams also have communication issues and many individuals felt that they personally had some form of communication issue with their team. Furthermore, the responses to having a dedicated HR and a tool to communicate team issues through were positive, encouraging us that LTAT could be successful at helping initiating conversations about issues within a team.</p> |
</div> | </div> | ||
| Line 1,463: | Line 1,463: | ||
<div class="bodyBlock"> | <div class="bodyBlock"> | ||
| − | <h1>Demo of Let's Talk About This</h1> | + | <h1 style="color:#24305E">Demo of Let's Talk About This</h1> |
| − | <p>With the help of the iGEM community we were able to develop a beta of our web application Let’s Talk About | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;" >With the help of the iGEM community we were able to develop a beta of our web application Let’s Talk About This<p> |
| − | <p>The application is coded in HTML, JavaScript and PHP, and the app is hosted on a Raspberry Pi model 3B+ server. Our team has a personal account that is active at all times and can be accessed by every member through this web address: <i>“www.icigem.com/LTAT/LTAT.html”</i>. Our personal account is password protected, therefore only members of the Imperial iGEM Team can access it, however a demo of the app as it were to be used in a web browser can be found at this web address: <i>“www.icigem.com/LTAT_demo/LTAT.html”</i>.</p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;" >The application is coded in HTML, JavaScript and PHP, and the app is hosted on a Raspberry Pi model 3B+ server. Our team has a personal account that is active at all times and can be accessed by every member through this web address: <i>“www.icigem.com/LTAT/LTAT.html”</i>. Our personal account is password protected, therefore only members of the Imperial iGEM Team can access it, however a demo of the app as it were to be used in a web browser can be found at this web address: <i>“www.icigem.com/LTAT_demo/LTAT.html”</i>.</p> |
| − | <p>How the web application works is that the user can access the app through any web browser (also including mobile devices) by typing the web address for the app into any web browser. When the app is opened, the user is asked a series of questions regarding their issue. These responses are recorded and at the end an email is sent to the appropriate person with the responses collated as a letter. </p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;" >How the web application works is that the user can access the app through any web browser (also including mobile devices) by typing the web address for the app into any web browser. When the app is opened, the user is asked a series of questions regarding their issue. These responses are recorded and at the end an email is sent to the appropriate person with the responses collated as a letter. </p> |
| − | <p>A fully functional demo of the web app is available for you to explore below. </p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;" >A fully functional demo of the web app is available for you to explore below. </p> |
<div class="breaker"></div> | <div class="breaker"></div> | ||
| − | <h2>Let's Talk About This: Demo Web App</h2> | + | <h2 style="color:#24305E;">Let's Talk About This: Demo Web App</h2> |
<div class="breaker"></div> | <div class="breaker"></div> | ||
| Line 1,503: | Line 1,503: | ||
<!--<div class = "notes"> | <!--<div class = "notes"> | ||
| − | <p> Welcome to the home page of Let's Talk About This. Sometimes raising an issue or a concern in a team environment can be hard, especially if you don't know the other team members very well. This can reduce | + | <p> Welcome to the home page of Let's Talk About This. Sometimes raising an issue or a concern in a team environment can be hard, especially if you don't know the other team members very well. This can reduce productivity, increase stress and most importantly take away the enjoyment of working on a project. To help mediate the initiation of difficult conversations regarding to team, we developed our app Let's Talk About This (LTAT). LTAT in a sense is a digital complaints box, with the added features of assisting the user break down their problem step by step, which allows them to reflect further on their issue. Their inputs are then compiled and sent as a letter to the person they wish to speak to regarding their issue, this allows the person addressed to to quickly and efficiently read through the problem and begin addressing it as soon as possible</p> |
</div> --> | </div> --> | ||
<h2>Let's Talk About This</h2> | <h2>Let's Talk About This</h2> | ||
| − | <p style="margin-top:15px;">Welcome to LTAT, your aid for raising difficult but important conversations</p> | + | <p style="font-family:'Patrick Hand';text-align:center;margin-top:15px;">Welcome to LTAT, your aid for raising difficult but important conversations</p> |
| − | <p>Press the button below to begin</p> | + | <p style="font-family:'Patrick Hand';text-align:center;margin-top:15px;">Press the button below to begin</p> |
<div> | <div> | ||
| Line 1,524: | Line 1,524: | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,543: | Line 1,543: | ||
<div id="announce_who" name="announce_who" style="display:none" > | <div id="announce_who" name="announce_who" style="display:none" > | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,563: | Line 1,563: | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,586: | Line 1,586: | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,607: | Line 1,607: | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,624: | Line 1,624: | ||
<div id="q3y" name="q3y" title="" style="display:none;"> | <div id="q3y" name="q3y" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,640: | Line 1,640: | ||
<div id="q4" name="q4" title="" style="display:none;"> | <div id="q4" name="q4" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,657: | Line 1,657: | ||
<div id="q4y" name="q4y" title="" style="display:none;"> | <div id="q4y" name="q4y" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,675: | Line 1,675: | ||
<div id="q5" name="q5" title="" style="display:none;"> | <div id="q5" name="q5" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,692: | Line 1,692: | ||
<div id="q5y" name="q5y" title="" style="display:none;"> | <div id="q5y" name="q5y" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,717: | Line 1,717: | ||
<div id="q6" name="q6" title="" style="display:none;"> | <div id="q6" name="q6" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,733: | Line 1,733: | ||
<div id="q6y" name="q6y" title="" style="display:none;"> | <div id="q6y" name="q6y" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,760: | Line 1,760: | ||
<div id="q7" name="q7" title="" style="display:none;"> | <div id="q7" name="q7" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,776: | Line 1,776: | ||
<div id="q7y" name="q7y" title="" style="display:none;"> | <div id="q7y" name="q7y" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,802: | Line 1,802: | ||
<div id="q8" name="q8" title="" style="display:none;"> | <div id="q8" name="q8" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,822: | Line 1,822: | ||
<div id="q8.1" name="q8.1" title="" style="display:none;"> | <div id="q8.1" name="q8.1" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,838: | Line 1,838: | ||
<div id="q8.1y" name="q8.1y" title="" style="display:none;"> | <div id="q8.1y" name="q8.1y" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,857: | Line 1,857: | ||
<div id="end_mess" name="end_mess" title="" style="display:none;"> | <div id="end_mess" name="end_mess" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| − | <p id="end_page" class="endPage"></p> | + | <p style="font-family:'Patrick Hand'; font-size:20px" id="end_page" class="endPage"></p> |
<button class="backButton" type="button" onclick="goBack(); undo()"><i class="far fa-arrow-alt-circle-left"></i></button><br> | <button class="backButton" type="button" onclick="goBack(); undo()"><i class="far fa-arrow-alt-circle-left"></i></button><br> | ||
| Line 1,871: | Line 1,871: | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,891: | Line 1,891: | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,908: | Line 1,908: | ||
<div id="q10y" name="q10y" title="" style="display:none;"> | <div id="q10y" name="q10y" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,933: | Line 1,933: | ||
<div id="q10y2" name="q10y2" title="" style="display:none;"> | <div id="q10y2" name="q10y2" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,958: | Line 1,958: | ||
<div id="q10y3" name="q10y3" title="" style="display:none;"> | <div id="q10y3" name="q10y3" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,974: | Line 1,974: | ||
<div id="q11" name="q11" title="" style="display:none;"> | <div id="q11" name="q11" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 1,990: | Line 1,990: | ||
<div id="q12" name="q12" title="" style="display:none;"> | <div id="q12" name="q12" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,016: | Line 2,016: | ||
<div id="q13" name="q13" title="" style="display:none;"> | <div id="q13" name="q13" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,033: | Line 2,033: | ||
<div id="q14" name="q14" title="" style="display:none;"> | <div id="q14" name="q14" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,050: | Line 2,050: | ||
<div id="q15" name="q15" title="" style="display:none;"> | <div id="q15" name="q15" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,075: | Line 2,075: | ||
<div id="q16" name="q16" title="" style="display:none;"> | <div id="q16" name="q16" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,091: | Line 2,091: | ||
<div id="q16y" name="q16y" title="" style="display:none;"> | <div id="q16y" name="q16y" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,115: | Line 2,115: | ||
<div id="q17" name="q17" title="" style="display:none;"> | <div id="q17" name="q17" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,131: | Line 2,131: | ||
<div id="q18" name="q18" title="" style="display:none;"> | <div id="q18" name="q18" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,150: | Line 2,150: | ||
<div id="q19" name="q19" title="" style="display:none;"> | <div id="q19" name="q19" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,175: | Line 2,175: | ||
<div id="q20" name="q20" title="" style="display:none;"> | <div id="q20" name="q20" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,192: | Line 2,192: | ||
<div id="q21" name="q21" title="" style="display:none;"> | <div id="q21" name="q21" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,219: | Line 2,219: | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,236: | Line 2,236: | ||
<div id="q22y" name="q22y" title="" style="display:none;"> | <div id="q22y" name="q22y" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,262: | Line 2,262: | ||
<div id="q23" name="q23" title="" style="display:none;"> | <div id="q23" name="q23" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,278: | Line 2,278: | ||
<div id="q24" name="q24" title="" style="display:none;"> | <div id="q24" name="q24" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,303: | Line 2,303: | ||
<div id="q25" name="q25" title="" style="display:none;"> | <div id="q25" name="q25" title="" style="display:none;"> | ||
<div class="topBanner"> | <div class="topBanner"> | ||
| − | <p>Let's Talk About This</p> | + | <p style="font-family:'Kaushan Script', cursive; text-align:center;font-size:20px">Let's Talk About This</p> |
</div> | </div> | ||
| Line 2,339: | Line 2,339: | ||
<div class="walkThru" > | <div class="walkThru" > | ||
| − | <p id="welcome" name="welcome" style="display:block;"> | + | <p id="welcome" name="welcome" style="font-family:'Varela Round', sans-serif; font-size:22px;color:#24305E;display:block;"> |
<b>Let's Talk About This</b><br> | <b>Let's Talk About This</b><br> | ||
<span class="walkThruText"> | <span class="walkThruText"> | ||
| Line 2,349: | Line 2,349: | ||
</p> | </p> | ||
| − | <p | + | <p style="font-family:'Varela Round', sans-serif; font-size:22px;color:#24305E;display:none;" id="anon" name="anon" > |
<b>Be known or be anonymous</b><br> | <b>Be known or be anonymous</b><br> | ||
<span class="walkThruText"> | <span class="walkThruText"> | ||
| Line 2,358: | Line 2,358: | ||
</p> | </p> | ||
| − | <p | + | <p style="font-family:'Varela Round', sans-serif; font-size:22px;color:#24305E;display:none;" id="mediator" name="mediator"> |
<b>Choosing the mediator </b><br> | <b>Choosing the mediator </b><br> | ||
<span class="walkThruText"> | <span class="walkThruText"> | ||
| Line 2,369: | Line 2,369: | ||
</p> | </p> | ||
| − | <p | + | <p style="font-family:'Varela Round', sans-serif; font-size:22px;color:#24305E;display:none;" id="probType" name="probType" > |
<b>General Issue type</b><br> | <b>General Issue type</b><br> | ||
<span class="walkThruText"> | <span class="walkThruText"> | ||
| Line 2,378: | Line 2,378: | ||
</p> | </p> | ||
| − | <p | + | <p style="font-family:'Varela Round', sans-serif; font-size:22px;color:#24305E;display:none;" id="questionz" name="questionz" > |
<b>Series of questions</b><br> | <b>Series of questions</b><br> | ||
<span class="walkThruText"> | <span class="walkThruText"> | ||
| Line 2,385: | Line 2,385: | ||
</p> | </p> | ||
| − | <p | + | <p style="font-family:'Varela Round', sans-serif; font-size:22px;color:#24305E;display:none;" id="askTeam" name="askTeam" > |
<b>Getting the team involved or talk to someone</b><br> | <b>Getting the team involved or talk to someone</b><br> | ||
<span class="walkThruText"> | <span class="walkThruText"> | ||
| Line 2,393: | Line 2,393: | ||
</p> | </p> | ||
| − | <p | + | <p style="font-family:'Varela Round', sans-serif; font-size:22px;color:#24305E;display:none;" id="askHealth" name="askHealth" > |
<b>Asking about their health</b><br> | <b>Asking about their health</b><br> | ||
<span class="walkThruText"> | <span class="walkThruText"> | ||
| Line 2,401: | Line 2,401: | ||
</p> | </p> | ||
| − | <p | + | <p style="font-family:'Varela Round', sans-serif; font-size:22px;color:#24305E;display:none;" id="askMessage" name="askMessage"> |
<b>Message to the team</b><br> | <b>Message to the team</b><br> | ||
<span class="walkThruText"> | <span class="walkThruText"> | ||
| Line 2,410: | Line 2,410: | ||
</p> | </p> | ||
| − | <p | + | <p style="font-family:'Varela Round', sans-serif; font-size:22px;color:#24305E;display:none" id="finMessage" name="finMessage" > |
<b>Submission page</b><br> | <b>Submission page</b><br> | ||
<span class="walkThruText"> | <span class="walkThruText"> | ||
| Line 2,424: | Line 2,424: | ||
<div class="bodyBlock"> | <div class="bodyBlock"> | ||
| − | <h2> | + | <h2 style="color:#24305E">Mail Box Of Recipient</h2> |
</div> | </div> | ||
| Line 2,565: | Line 2,565: | ||
<div class="bodyBlock"> | <div class="bodyBlock"> | ||
<div class="breaker"></div> | <div class="breaker"></div> | ||
| − | <h2 style="text-align:center;">To refresh the demo, <span class="text1" onclick="location.reload()"><u>click here</u></span></h2> | + | <h2 style="color:#24305E;text-align:center;">To refresh the demo, <span class="text1" onclick="location.reload()"><u>click here</u></span></h2> |
| − | <p> | + | <p style="font-family:'Varela Round', sans-serif; font-size:14px; text-align:center;"> |
| − | The program files and documentation for the LTAT web app can be found on our <a href="">GitHub directory</a>. | + | The program files and documentation for the LTAT web app can be found on our <a href="https://github.com/icigem?tab=repositories">GitHub directory</a>. |
| − | + | </p> | |
| − | + | ||
| − | + | ||
</div> | </div> | ||
| Line 2,576: | Line 2,574: | ||
<div class="bodyBlock"> | <div class="bodyBlock"> | ||
| − | <h1>How has the app changed the way we work?</h1> | + | <h1 style="color:#24305E">How has the app changed the way we work?</h1> |
| − | <p>The LTAT app has on a few occasions been used to raise issues with the HR and PI of our teams. | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;>The LTAT app has on a few occasions been used to raise issues with the HR and PI of our teams. |
These mediators were informed in good time and were able to respond to the situation quickly and | These mediators were informed in good time and were able to respond to the situation quickly and | ||
with discretion. Knowing that we have a tool with which to communicate issues clearly and | with discretion. Knowing that we have a tool with which to communicate issues clearly and | ||
| Line 2,586: | Line 2,584: | ||
</p> | </p> | ||
| − | <p>With the aid of the app, we were able to work together more coherently, and in fact found that | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;>With the aid of the app, we were able to work together more coherently, and in fact found that |
after a certain time it was no longer needed as the main platform for raising issues, and people | after a certain time it was no longer needed as the main platform for raising issues, and people | ||
felt more natural talking about it to one another in person. By working more coherently, we were | felt more natural talking about it to one another in person. By working more coherently, we were | ||
| Line 2,598: | Line 2,596: | ||
<div class="bodyBlock"> | <div class="bodyBlock"> | ||
| − | <h1>Giving back to the iGEM community</h1> | + | <h1 style="color:#24305E">Giving back to the iGEM community</h1> |
| − | <p>After making the beta, we distributed copies of the app to other teams. | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;">After making the beta, we distributed copies of the app to other teams. |
However, as the app will be used for communicating personal and often sensitive material, | However, as the app will be used for communicating personal and often sensitive material, | ||
| − | we drafted a terms and conditions document for the app | + | we drafted a terms and conditions document for the app to which the |
users and the developer must agree to. | users and the developer must agree to. | ||
| − | </p> | + | </p > |
| − | <p>In summary the document reassures the client (the iGEM team) that their account is secure and independent | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;">In summary the document reassures the client (the iGEM team) that their account is secure and independent |
from Imperial College London, that the developer has access to all the | from Imperial College London, that the developer has access to all the | ||
information however they will not and cannot use this information in any way and doing | information however they will not and cannot use this information in any way and doing | ||
| Line 2,612: | Line 2,610: | ||
web application from distribution without the developer’s permission. </p> | web application from distribution without the developer’s permission. </p> | ||
| − | <p>An account for you team can very easily be created by the developer, | + | <p style="font-family:'Varela Round', sans-serif; font-size:18px;color:#24305E;">An account for you team can very easily be created by the developer, |
you would just need to download the terms and conditions document, | you would just need to download the terms and conditions document, | ||
follow the instructions on the document and contact the developer. | follow the instructions on the document and contact the developer. | ||
Latest revision as of 03:56, 18 October 2018
Let's Talk About This
Your aid for raising difficult but important conversations
Working in a team can have its challenge and sometimes be difficult. Opposing opinions, misunderstandings, lack of communication and personal issues can cause stress and conflict within a team, which is detrimental to the teams’ health and to the team’s success with regards to their project.
These kinds of issues need to be addressed as early as possible, otherwise allowing such negative factors to fester in the team can have dire consequences, such as members outright fighting, or wishing to leave the team.
One of the most effective methods for dealing with internal team pressure is simply to talk about them in the open. By speaking out loud and listening patiently, many conflicts and unnecessary stress can be avoided, improving the wellbeing of the individual, as well as benefiting the whole team.
However, starting these kinds of conversations can be quite awkward and difficult, especially in the beginning of a project where everyone is new and the team members do not know each other very well. This lack of communication can lead to issues being bottled up, causing stress and frustrations that lead to arguments and loss of productivity, which is unhealthy for the individual and the team.
To help initiate conversations about issues within a team, we decided upon our solution, Let’s Talk About This (LTAT).
There are two key elements to LTAT:
Human Resources
We thought that each team should have their own Human Resources (HR) person, who is elected by the team. The HR’s role would be to act as a listener and mediator of issues that are raised in the team. They would help solve issues where they can or involve more appropriate parties where they see fit.
The LTAT web application
communicating one’s issues can be awkward, even to someone dedicated to listening to these kinds of things. It can also be difficult to break down your own problems and think of them objectively. Also, having to use a personal communication channel (such text or email) to raise an issue can be intimidating, especially if the user is unsure or nervous. We decided that a level and unbiased platform for specifically communicating issues is needed, on which a user is assisted in objectively breaking down their problem, and they should be able to access and use the platform with ease. Furthermore, we want the HR to receive the message in a way they can efficiently and effectively understand the problem.
The LTAT web app is a tool to raise an issue in a discrete and orderly manner. It is up to the user and the HR to meet in person, with other relevant parties, to discuss the issue further and resolve it in person.
But first, is LTAT really needed?
Before going into making our LTAT app, we needed to confirm that something like LTAT is needed in the real world, and whether other teams would find it useful. We contacted several iGEM teams from all over the world to fill out our survey, in which we asked individuals general questions about their team management system and about issues they have within their team. Through our survey we wanted to confirm two key things. First, do
The app is to be used by individuals to communicate issues with the team, therefore it is best to get an idea of issues faced in other teams from an individual’s perspective. Furthermore, this allows the individual filling our survey to be more comfortable about honestly answering the questions, rather than feeling pressured into choosing answers that creates a false-positive image of their team.
Do other team's have communication issues?
How often do you perceive communication issues within your team?
How often do you feel you have communication issues with your team?
These confirmed to us that individuals in other teams do perceive challenges and difficulties when it comes to communication. One fifth of the respondents believe that issues occur regularly is a considerable amount, and a total of 61.8% believing that there is at least one issue a week. Furthermore, slightly over half of the total respondents believe that they themselves have at least one communication issue a week. These data suggest that other iGEM teams also have communication issues and so LTAT could potentially be used by others.
Would other teams be interested in LTAT?
Would having a dedicated Human Resource person improve communication within the team?
Would a tool that allows members to voice issues and encourages the team to sort them out together improve team communication?
These results showed some promise, as majority of individuals do agree that a dedicated HR could possibly be useful, but most of them are sceptical about how well it could be implemented by the team, which is a reasonable thought to have. However, one participant commented “We've implemented this [HR] role this year and it has helped immensely, especially because our team is very large”. This particular response was encouraging to hear and supported our belief that a dedicated HR in a group would be beneficial to everyone. It’s unfortunate that we couldn’t contact this individual further, as we the responses are recorded as anonymously.
In Summary...
From our survey we received confirmation that other teams also have communication issues and many individuals felt that they personally had some form of communication issue with their team. Furthermore, the responses to having a dedicated HR and a tool to communicate team issues through were positive, encouraging us that LTAT could be successful at helping initiating conversations about issues within a team.
Demo of Let's Talk About This
With the help of the iGEM community we were able to develop a beta of our web application Let’s Talk About This
The application is coded in HTML, JavaScript and PHP, and the app is hosted on a Raspberry Pi model 3B+ server. Our team has a personal account that is active at all times and can be accessed by every member through this web address: “www.icigem.com/LTAT/LTAT.html”. Our personal account is password protected, therefore only members of the Imperial iGEM Team can access it, however a demo of the app as it were to be used in a web browser can be found at this web address: “www.icigem.com/LTAT_demo/LTAT.html”.
How the web application works is that the user can access the app through any web browser (also including mobile devices) by typing the web address for the app into any web browser. When the app is opened, the user is asked a series of questions regarding their issue. These responses are recorded and at the end an email is sent to the appropriate person with the responses collated as a letter.
A fully functional demo of the web app is available for you to explore below.
Let's Talk About This: Demo Web App
11:22
Let's Talk About This
Welcome to LTAT, your aid for raising difficult but important conversations
Press the button below to begin
Let's Talk About This
Welcome to LTAT.
Even though this is the wiki demo version of the LTAT web app,
it still has all the functionality of the full web app and represents it quite truly.
Press the button to begin the demo.
Mail Box Of Recipient
- Search
- Inbox
- Sent
- Spam
- Deleted
- Priority
- Updates
- Social
- Work
- idt: Your IDT order has been shipped
- upv valencia: We've sent over your parts
- igemhq: Wiki freeze deadline is approaching!
- t.ouldridge: Order Approvals Needed
- i.mullor-ruiz: I thought you'd find this paper useful!
- neborders: Your High-fidelity Q5 will be arriving soon
- ucl_igem: What time is the meet-up?
- oxford: IDT parts order?
- oxford: New Scientist Live payment receipt
- benchling: T-shirts are on their way
- sue: regarding agarose and missing brush
- t.ouldridge: Don't forget the pub quiz this firday!
To refresh the demo, click here
The program files and documentation for the LTAT web app can be found on our GitHub directory.
How has the app changed the way we work?
With the aid of the app, we were able to work together more coherently, and in fact found that after a certain time it was no longer needed as the main platform for raising issues, and people felt more natural talking about it to one another in person. By working more coherently, we were able to dedicate our time and energy to developing our project and taking it further to completion, rather than dealing with internal stresses leading to lack of productivity and hurting the team’s mental health.
Giving back to the iGEM community
After making the beta, we distributed copies of the app to other teams. However, as the app will be used for communicating personal and often sensitive material, we drafted a terms and conditions document for the app to which the users and the developer must agree to.
In summary the document reassures the client (the iGEM team) that their account is secure and independent from Imperial College London, that the developer has access to all the information however they will not and cannot use this information in any way and doing so will put them at risk of serious prosecutions. And finally, the document also protects the web application from distribution without the developer’s permission.
An account for you team can very easily be created by the developer, you would just need to download the terms and conditions document, follow the instructions on the document and contact the developer.
