Team:Edinburgh/HP/hierarchy
From 2014.igem.org
Samireland (Talk | contribs) |
Samireland (Talk | contribs) |
||
(6 intermediate revisions not shown) | |||
Line 2: | Line 2: | ||
<link href='http://fonts.googleapis.com/css?family=Roboto+Slab' rel='stylesheet' type='text/css'> | <link href='http://fonts.googleapis.com/css?family=Roboto+Slab' rel='stylesheet' type='text/css'> | ||
<link rel="stylesheet" href="https://2014.igem.org/Template:Team:Edinburgh/CSS?action=raw&ctype=text/css" type="text/css" /> | <link rel="stylesheet" href="https://2014.igem.org/Template:Team:Edinburgh/CSS?action=raw&ctype=text/css" type="text/css" /> | ||
- | + | <div id="topbit" style="margin-bottom: 40px;"> | |
+ | <table align="center" style="border-spacing: 5px;"><tr><td><a href="https://2014.igem.org/"><img src="https://static.igem.org/mediawiki/2014/archive/3/3f/20140702191450%21Igem.png" width="50px" height="45px"></a></td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh">Home</a></td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh/team/">Team</a></td><td id="navlink"><a href="https://igem.org/Team.cgi?id=1399">Profile</a></td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh/logic/">Background</a></td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh/project/">Project</a></td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh/HP/">Policy and Practices</a></td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh/modelling/">Modelling</td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh/log">Daily log</a></td></table></div> | ||
+ | <div id="tourleft"><a href="https://2014.igem.org/Team:Edinburgh/HP/robustness">← PP robustness</a></div> | ||
+ | <div id="tourright"><a href="https://2014.igem.org/Team:Edinburgh/HP/supervision">PP supervision →</a></div> | ||
<div id="igem"> | <div id="igem"> | ||
<div id="header"> | <div id="header"> | ||
<a href="https://2014.igem.org/Team:Edinburgh"><img id="logo" src="https://static.igem.org/mediawiki/2014/8/8e/Ed14_logo.png" width="200" height="200"></a> | <a href="https://2014.igem.org/Team:Edinburgh"><img id="logo" src="https://static.igem.org/mediawiki/2014/8/8e/Ed14_logo.png" width="200" height="200"></a> | ||
- | <h1> | + | <h1>Policy and Practices</h1> |
</div> | </div> | ||
+ | <div id="HPpage"> | ||
<table> | <table> | ||
<tr><td> | <tr><td> | ||
Line 33: | Line 37: | ||
<q>For a team as large as ours, a leader is absolutely necessary.</q></li> | <q>For a team as large as ours, a leader is absolutely necessary.</q></li> | ||
<li>For those who said they had or wanted to have a team leader, we asked to clarify what they thought the role would involve and what the benefits would be.<br> | <li>For those who said they had or wanted to have a team leader, we asked to clarify what they thought the role would involve and what the benefits would be.<br> | ||
- | <q>I think the team needs a coordinator who would keep the bigger picture in mind and integrate all parts, and keep on track which parts need more attention.</q> | + | <q>I think the team needs a coordinator who would keep the bigger picture in mind and integrate all parts, and keep on track which parts need more attention.</q><br> |
<q>A team leader could help us decide if and when we needed to drop some part of the project, and motivate us to finish things well on time.</q></li> | <q>A team leader could help us decide if and when we needed to drop some part of the project, and motivate us to finish things well on time.</q></li> | ||
<li>However, it was also indicated that it would be difficult to decide who the leader should be:<br> | <li>However, it was also indicated that it would be difficult to decide who the leader should be:<br> | ||
Line 44: | Line 48: | ||
<p>This picks up on the idea by Wittebolle and colleagues (2009) that there is a need for an even distribution of functionally redundant members. They found that if the community depends too much on a dominant strain the population is more susceptible to fluctuations. Taken together with our findings from the iGEM interviews we are inclined to believe that it might be better to have no hierarchy in our system and ensure equal contribution of all components. This is in accordance with the horizontal structure of hierarchy we wanted to achieve with population control.</p> | <p>This picks up on the idea by Wittebolle and colleagues (2009) that there is a need for an even distribution of functionally redundant members. They found that if the community depends too much on a dominant strain the population is more susceptible to fluctuations. Taken together with our findings from the iGEM interviews we are inclined to believe that it might be better to have no hierarchy in our system and ensure equal contribution of all components. This is in accordance with the horizontal structure of hierarchy we wanted to achieve with population control.</p> | ||
- | </td></tr> | + | |
+ | <br><br><br><br></td></tr> | ||
+ | </div> | ||
</div> | </div> | ||
+ | <div id="tourleftbottom"><a href="https://2014.igem.org/Team:Edinburgh/HP/robustness">← PP robustness</a></div> | ||
+ | <div id="tourrightbottom"><a href="https://2014.igem.org/Team:Edinburgh/HP/supervision">PP supervision →</a></div> | ||
</html> | </html> |
Latest revision as of 03:53, 18 October 2014
HierarchyIn several systems, a hierarchical structure can be observed, i.e. rather than everyone being equal, such positions as ‘team leader’ or similar may arise. Going back to Edwin Hutchin’s example of navigating a ship into a port, it is obvious that the social structure of the crew plays an essential role. The navigator needs to be higher ranked than the sailors. That way he can give them the necessary orders for the efficient gathering of the essential information about the ship’s location. On the other hand, many other systems perform better if all individuals have equal levels of authority. Thinking back to our bacterial system, do we need a ‘master strain’, with higher control/power? We asked the teams whether they felt that they had a team leader, and whether they felt they needed one.
Relevance for bacterial system designThis picks up on the idea by Wittebolle and colleagues (2009) that there is a need for an even distribution of functionally redundant members. They found that if the community depends too much on a dominant strain the population is more susceptible to fluctuations. Taken together with our findings from the iGEM interviews we are inclined to believe that it might be better to have no hierarchy in our system and ensure equal contribution of all components. This is in accordance with the horizontal structure of hierarchy we wanted to achieve with population control. |