FYI not a DXC employee.
@izs+1mcMLmqV Can you elaborate?
in all this kerfuffle - it is totally lost that silan now has MEA and all other regions got gently wiped. may be a great strategy - hopefully this works.
@byk+1mcMLmqV OP here thats what I thought aswell but then why was the decision made only 6 days after the latitude Finacial breach was made public? Coincidence? ITO struggling isnt exactly new... Also how is it that broader DXC organization was unaffected by the breach? My guess is it's because the team responsible for the breach was an ITO team at DXC that worked exclusively with Latitude finacial this would explain why Bagal was immediately fired. Why even risk the optics especially since regulators are probably going to get involved. Instead they could've just paid Bagal for week or 2 then fired the guy. What I still don't get is how Latitude Fincial would allow DXC users to access records held not only internally but by a completely seperate System integrator! What would help is if we knew what exactly DXC was doing for Latitude, was it another CSC hogan customer or something bigger? Also worth mentioning that Chris Drumgoole was formerly the CIO of GE Latitude fincials former parent so it makes sense that he'd be put in charge to try and cope with this breach. The puzzle pieces look like they may fit.
One guy is a bagel, another is a drumstick.. and another chick is a steak. we are on a evolution which is essentially a revolution.
Basically ITO and Cloud was Vinods area and it’s been suffering HUGE declines.
Vinod hasn’t been able to turn it round, Chris is/was Mike Slavinos fix it guy so he’s taking a crack.
Generally a change in leadership means more cuts. It’s a clean slate to execute a new program of the same old. Like Mike 1.0 and Mike 2.0. Both thieves, both cnuts. Same name too. Both bully’s. Both liars.
God help the poor staff.