Discussion Locked

Force users to use the system

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
If I implemented a system and I want to courage the users to use the systems until they feel they can not live without it?

7 replies

by timthetoolman

Hi,

You cant really force anyone to use a system... At least not as a IT guy. If you're the user's manager, then you can say things like "your performance review will include understanding and use of new technologies.." Assuming you have some sort of annual performance review.

If the system is worth using, then people will use it. If it makes their life easier, then people will use it.

You need to train them of course and show them why the *should* use it. But at the end of the day, ifthe users do it one way and it works, then asking them to do it another way wont get you anywhere unless there is some benefit for them!

Cheers,
Tim.

by shanghai sam

Getting user acceptance of a new system is always tricky. I use the following:

1. Try to get early buy-in. If possible have the users help you design the system. It always helps for acceptance to have someone on your side who is also on the "inside" of the user community.

2. Make the transition to the new tool as painless as possible. That means being available to answer questions, having lots of training available, writing good user and help manuals, opening a help desk, and producing a supporting website. Keep good notes from all of these sources. This will tell you more about what needs to improve than just about any other thing in the business.

3. Be open to criticism and willing to improve. Nothing stops a deployment faster than an unresponsive developer.

4. Keep the price reasonable for the type of tool that it is. Don't go too high or too low. If your competitors are at $40 a copy, don't sell for less than $30. If you go too low, people will think yourtool is not worth it. If you go higher than the competitor, people will not transfer to your product.

5. Advertise. This is true whether it is an internal company product or something that has to be sold. It's obvious to outside a company. It gets rare for inside a company. There is nothing wrong with "tooting the horn" on the new tool. Take out an ad in the company's employee news letter. Put up posters in the user area. Have a launch day ceremony. Give special presentations to the managers.

by premjith

I would recommend an approach which involves both push and pull. I am assuming the case where in the system is being developed by a third party vendor.

1. Have a key sponsor from the business community (say the department head for whom the systemis being developed) as part of a steering committee. The CIO should also be part of this committee.

2. Have a group of business users designated as key users. Identify super-users also. They should be trained initially on the features of the product/technology/solution. They should definitely be part of the development process in requirements gathering. Their explicit approval must be sought on all project deliverables - requirements specifications, high level design, detailed design, etc.
3. Have the same user community accept the solution through an already agreed upon User Acceptance Test plan.

4. Measure ROI for the solution after a few months of usage of the system and address key user problems before transitioning into maintenance mode.

The key users will act as champions of the solution, as it has their expressed approval throughout. The business sponsor will help tailor processes to suit maximum usage of developed system. IS department will continue to have ownership and will be able to show case ROI earned on their balanced score cards.

This discussion is closed to new replies.