Quote:
Originally Posted by SteveDallas
I am beset by complaints from coworkers who are worried about a ma$$ive software implementation. I am trying to be diplomatic, but the time for complaints was months ago. I am trying not to point out that we've already delayed the project by four months to absolutely no effect, simply to assuage peoples' discomfort. There are many things I'm trying to to point out simply because they'd come off as insulting. But the bottom line is this is going to happen whether anybody likes it or not.
|
Keep in mind that it doesn't matter how virtuous the system is you're inflicting on people if they won't cooperate. The users have to be on board or you're wasting your money. The users are your key to success.
I think it's worth the time to assuage every reasonable worry. But some people are going to bitch and moan no matter how much training and reassurance they receive. You have to deploy sometime.
The good thing is that if this software is a key factor in the success of the company, anyone who embraces it will prosper and those who don't will eventually get left behind (if not shit-canned).
In the future, your company might try to make the users see the virtue of a new software package before making the decision to implement it. If you believe this software will make a huge difference to the bottom line and can make the users decide that they must have this software, then you're golden. When those two criteria (and some that aren't occurring to me in my just-woken phase) aren't fulfilled the software probably isn't a good idea.
(I'll stop here. I have a shit-ton more to say about this, but you're probably just venting and don't care. This Master's degree shit is warping my mind--I'm actually thinking about business!?)