I'm not trying to attack anyone here, but I thought that I would add my recent experience with what I consider to be accountability.
We reside in a network where users bring in their own equipment and hopefully abide by policies that we have developed, (ie. having anti-virus, spyware protection, software firewalls, etc.) However, this is only policy. I have dreamed about holding a user accountable in a monetary fashion for several years since it's usually ME that spends the countless hours cleaning up the mess. IT mgmt feels the same as we, but no one took the time to develop a way to place a dollar amount on an outage.
Well, it was time and so I stepped up to the challenge. Now granted, I'm a little one sided, but we had to start somewhere.
I've recently implemented an incident report template to be used whenever a virus attack, nw outage due to neglegance, theft, etc., occurs.
The last section is Costs of lost opportunities. When I first developed the draft and presented it to non-IT mgmt, they of course got very upset because their claim is that you can't put a dollar amount on something that is not set in stone. They of course are referring to the fact that our users work on a commission basis and that varies per person so it's not like....okay, we've got john doe here and he makes $30/hr and his machine was infected and total cleanup took 8 hrs so that's $30*8. I did have my numbers based on an average and basically the numbers were right. But, because the particular case study that I demonstrated showed a lost of $2.8Mil per hour for 2 hours was devastating to them (hence the importance of accountability I'm trying to bring to light!!), they didn't want to go that route. Now granted, I see their side of the picture. They feel that if we start charging back to those that allowed the incident to occur, then we put ourselves in a he said, she said attack mode and that's just not good business. So the next time that we cause an outage because of a programming error, they will try to charge that $2.5mil back to us (which is understandable).
So, we went back to the drawing board and with IT CIO we were able to make a compromise. We used a percentage to at least represent some type of opportunity costs lost. Now we did have some definite dollar amount charges (We have 3 sections - HO costs for man hours and loss of Internet costs, - Costs for the individuals that had to be down, - Costs for larger outages), but we were able to give representation to upper-management that these are serious and we need their support to help educate the users about the responsibility on their end, not just ours.
My point I guess is that, it's painful to hear the truth and so they try to avoid it, this is true, but if you're committed to making things better than it's up to you to work with others to get the message across even if it means working together/compromising without sacrificing to come to a resolution that works.
I definitely feel that even though this incident report will not make people happy, it will help management come around and begin supporting the IT department that so desparately needs their support in order to be able to function as needed.
This is what we've had to do start on the right track....
I do agree that blatent (sp?) neglect of policy, should ABSOLUTELY be cause for reprimand and then dismissal.
Put simply...if I tell you not to touch the HOT pan of boiling water on the stove and you go right over and touch it, then I have no simpathy for you when you burn your hand. And then if you
re dumb enough to do it again, then you get what you deserve.