@BBigford said in CrashPlan - Bug?:
@Jason said in CrashPlan - Bug?:
@BBigford said in CrashPlan - Bug?:
., but the CEO immediately shot down anything with that kind of latency.
Why is this the CEO decision? He shouldn't even be in involved. That should be the IT Director and CIO.
We restructured. IT was reporting to Engineering Manager > IT Director > VP of Operations > CEO (who writes off all big stuff). Took forever for approvals to do anything. EM quit after 10 years so we reported to the VP of Ops for 2 weeks. Then we're told IT is a corporate function, not Engineering/Ops, so started reporting to the CEO for everything. Approvals that took years just to get shot down because of the chain, started getting approved in minutes. We can now use a ton of hosted services we were told go against contracts. All in all, I'm totally cool with the transition even if some of the smaller, stupid stuff gets dragged along.
So they decided that things were bad and .... did this as the fix? Sounds like a problem from the top. Even with the new structure, this makes zero sense. The CEO is still getting involved where no manager should be. Sounds like the CEO is likely the root cause here.