Lakhasly

Garth committed a number of serious errors throughout the Blue Sky Project, which ultimately influenced his involvement at the Eastern Oceanography Institute (EOI).Inadequate Communication and Team Cohesion: Another obstacle was Garth's failure to communicate openly with his team, especially with respect to before the intersection of Blue Sky.In contrast with Tom, who proactively fostered relationships in the institute, Garth fled to his office and limited himself to interaction with coworkers only when necessitated.Lack of Proactive Problem-Solving: When technical issues arose, such as a graduate assistant mistakenly deleting important data, Tom took the initiative to develop a warning system to prevent future errors.Meanwhile, Garth remained focused on technical configurations rather than addressing operational challenges that impacted daily workflow.Risky Decision-Making in Vendor Selection: Garth's choice of OpenRange as the cloud service provider was based primarily on cost savings, disregarding concerns about security and reliability.Tom had argued in favor of larger, well-established providers like VMware or Microsoft, which would have provided more stability.These incidents reinforced doubts about whether the right provider was chosen.1.2.3.4.5.

Garth committed a number of serious errors throughout the Blue Sky Project, which ultimately influenced his involvement at the Eastern Oceanography Institute (EOI).

1. 
   

   Poor leadership and Poor Engagement: The biggest mistake Garth made was his limited engagement with staff and colleagues. In contrast with Tom, who proactively fostered relationships in the institute, Garth fled to his office and limited himself to interaction with coworkers only when necessitated.

   
   


2. 
   

   Inadequate Communication and Team Cohesion: Another obstacle was Garth's failure to communicate openly with his team, especially with respect to before the intersection of Blue Sky. Even after Tom had asked multiple times regarding job security, Garth maintained an ambiguous nature that fostered insecurity and also a detachment from the team.

   
   


3. 
   

   Inadequate Training Process/Plan: Although it was important to conduct training as part of the plan, Garth did not put together what constitutes an effective training plan. The trainers from OpenRange were both inexperienced with teaching methods and poorly prepared, leading to questions and eventually refractor by staff. Instead of intervening, Tom was allowed to reinforce as he managed the changes within training plan. Tom settled into the leadership role, while Garth playfully considered himself behind the scenes.

   
   


4. 
   

   Risky Decision-Making in Vendor Selection: Garth’s choice of OpenRange as the cloud service provider was based primarily on cost savings, disregarding concerns about security and reliability. Tom had argued in favor of larger, well-established providers like VMware or Microsoft, which would have provided more stability. However, Garth pushed for OpenRange, a newer company, which later led to system failures and operational disruptions**. These incidents reinforced doubts about whether the right provider was chosen.

   
   


5. 
   

   Lack of Proactive Problem-Solving: When technical issues arose, such as a graduate assistant mistakenly deleting important data, Tom took the initiative to develop a warning system to prevent future errors. Meanwhile, Garth remained focused on technical configurations rather than addressing operational challenges that impacted daily workflow. This further reduced his visibility as a leader.