Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's the fact that something like a "disciplinary council" exists, and that it was the first tactic the CIO went with that bothers me.

There's a reason they went around the CIO. I suspect if the CIO had met with this person they could have learned and helped.



In the situation described in the article, the manager had gone to the CIO but CIO refused to help them.

"The CIO admitted that he had been approached and explained that he had informed the VP that IT already had a project with SAP to deliver what the VP needed. “Yes, but that won’t be ready for me to use for three years, and I need something today,” retorted the VP."

The manager had a valid and valuable reason ("increased revenue $1M per month") to require a service that CIO and their organization was unable to provide in a reasonable timeframe, but other companies on the market were.


The problem is bureaucracy and unwillingness of IT to be agile and responsive. Their weapon is procedure which quashes initiatives. At the same time though, going outside like that can have major effects on compliance if they are subject to audits, aside from the security considerations.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: