Recently hired as team lead/manager, team seems somewhat dysfunctional.

I&#x27;ve shortened the title just a bit due to the character limit.<p>72 hours of production downtime is &#x2F;insane&#x2F; to think about and with such a brass attitude coming from the team as well.... I&#x27;d be inclined to go to the board and ask for additional funding to start a new team&#x2F;begin knowledge transfer ASAP and start winding down the old team. I&#x27;d be curious to know why the CTO&#x27;s isn&#x27;t being grilled about the downtime and if they even have a CAPA process to prevent this from happening again?<p>Additionally, one of the commenters in the thread also points out just how important devops as a &#x2F;culture&#x2F; is compared to just treating it as something to be bolted on at a later point in the organization life. I&#x27;ve worked with too many devs that seem to think their involvement ends when they throw the code over the proverbial &quot;devops fence&quot;.

Start by firing the guy who pushed the code on Friday Night. Then email the rest of the team and say anyone who wants a job to just show up 9AM Monday.

I&#x27;m curious how the compensation is structured. For someone with equity in the business a 72 hours downtime is horrible.<p>But if the devs are making below market rate, and their compensation is unrelated to the business&#x27; performance, it&#x27;s a little unrealistic to expect them to be going above and beyond for on-call duties.

Pushing code to production at 11pm on a friday???<p>Yikes.