Sharing IT Problems with Executives?
dicey asks: "Later this week all of the IT department at my company (50-80 people) is having a dinner with the company President and VP/CIO. One major reason for this is so that they can get a better understanding of what is going on in IT and how it impacts the company overall. Ideally, with the ideas and sharing, these guys will have a better appreciation for us, adjust our budgets appropriately, and help us in our business.
However, many of us are wary to speak about what is going on because it will inevitably reveal problems with the company. We are worried about what we discuss coming back to our directors ultimately to bite us. I am curious what my fellow Slashdot readers have done in similar circumstances, where there is a great chance to let someone high up in your company know of problems so that they can be rectified, but whereby revealing them you may get hurt in the process."
A carefully considered, previously agreed-upon statement would be fine, but I would cringe at anyone who would speak "off the cuff" to management. If you can approach them in the right way, you may well end up with what you need. Or at least what they think you need. Anyone in your department who has a deep-seated need to impress the brass should be given the wrong location and time for the dinner. Best of luck!
"Never pet a burning dog."
Send out an email to your IT staff, avoiding the managers. Let them know that a box will be made available at some accessable point, where anonymously _typed_ papers can be dropped off.
Encourage folks to not only write down the bad stuff, but write up good things as well. And always give examples and suggestions with the bad. But make sure that the examples focus on the issues, not specific people.
Deliver the box to the VP/manager/PHB and tell him it was done this way to prevent personal bias influencing the issues.
Support FSF: Stop thinking with your wallet, and think with your imagination. (cc/non-commercial)
A good admin/support person should have the ability to at his desk and goof off on his computer. When caught doing so, and asked what actual work I was doing, I point to the support hotline phone and the fact that it isn't ringing. If nothing was broken and my routine maintainance was up-to-date, the only reason why I have left to not call it a day the day is because I need to be on call in the hopefully unlikely event something causes that phone to ring.
I agree with your points, but you are forgetting exactly how much management subordinates/discredits/undervalues/detests/fears us.
"IT provides a service. We know that the service must be worth something, but we understand nothing about it. If we cannot understand it, then it cannot be important, but everybody has an IT department so we better have one. But it is filled with inexperienced children who have not spent their life climbing the corporate ladder, so they cannot understand the "complexity" of the business and how it needs to improve. But we have to have them, and they make almost as much as we do so we better smile when they are around. Please, please don't let them say anything because I will feel stupid because they know all this jargon that I do not. But they do not understand business as well as management and we set the rules so we are on top and my life is worthwhile. Just do not let them speak."
The big issue is that all computer technology is just magic to management. Computers seem to help the business, but the effects usually cannot be quantified until after they are deployed. So why do it? Because all the management magazines tell them that some other company used software for something and is now saving tons of money.
We save them when they have lost that important file, but they know they would not have lost it if it was on paper. Almost everything with computers means they have to learn something new, and they hate that.
The other side is that we are often closely involved with many parts of the business. We hear the complaints from the whole company. We may not know the big picture, but most working IT people could quickly pick 5 tasks that could be cheaply improved by technology in completely non-IT departments, because they know what is frustrating the employees.
I posted a story about trying to sell a business process improvement. I believe I did it on their terms. I reminded them how many people were required to fix the bad data. I demonstrated how this system was better. I talked about how the related processes would be integrated to improve accuracy and reduce the cost across the enterprise. I did not talk about technology other than to say the current hardware could easily handle it. I got some excitement from them, but lost because THEY CANNOT JUDGE GOOD SOFTWARE FROM BAD SOFTWARE even after they use it.
I am in a special position here. They are not my only client, but I worked almost 1000 hours last year FOR THEM, and they spent more for my services than for the 60-hours-every-week IT manager (including all compensation.) I probably cost them as much as his boss, the decision-maker. I am the high-priced outside expert who has an unbroken record of delivering better than they require before any deadlines and always staying under the budget. I do business strategy consulting at other companies. They should greatly respect my opinions, but I am still "just an IT guy."
And it does not help that I look young. The white hair keeps going away when I do not work. I almost wish it would all turn white so I would look older. The "decision-maker" is only 10 years older, but has a full head of white hair. Maybe I should dye (bleach?) mine.
If you really want to get a suggestion to management, have a salesperson from another company contact them and tell them that this idea is incredible and all the other companies are doing it and they need it too. He will get much more respect than any employee, and has much more credibility than any nerd.
I spend my life entertaining my brain.