Slashdot Mirror
Justifications For Creating an IT Department?
jjoelc writes "This may sound like an odd request, so first some background. I work at a broadcast television station, and I have found it to be very common for IT to be lumped in with the engineering department at many stations. I believe this is mainly because the engineers were the first people in the business to have and use computers in any real capacity, and as the industry moved to file-based workflows it has simply stayed that way. I believe there is a need for IT to be its own department with its own goals, budgets, etc. But I am having a bit of a rough time putting together the official proposal to justify this change, likely because it seems so obviously the way it should be and is done everywhere else. So I am asking for some pointers on the best ways to present this idea to a general manager. What are the business justifications for having a standalone IT department in a small business? How would you go about convincing upper management of those needs? There are approximately 100 employees at the station I am currently at, but we do own another 4 stations in two states (each of these other stations are in the 75-100 employee range). The long term goal would be to have a unified IT department across all 5 stations."
To synergize our leveragables into a new cloud based paradygmn, we'll need a new solutions oriented IT team to create some actionables to create a win-win in reducing internal friction and increase efficiencies to enable the monitization of our empowered workforce.
Well.. maybe. Or Maybe not. But Definitely not sort of.
And to think that I just used the last of my mod points - well played.
Social Engineering Expert: Because there is no patch for stupidity.
We put the IT in monitization.