I feel your pain. A lot of my job is project work/tools. While they are adopted and used some of the time, some of them just sit there.

I think the key thing for tools like that is not only management buy-in, but a policy that says it must be done that way. If using your tools are optional, people will do things the same way just to avoid learning something new. Something that I find useful in getting people to adopt something new is documentation. If they've got a reference (especially a quick reference), it seems to help.

It is a weird phenomena though... You hand somebody something that will make their lives much easier and they'd rather to do it manually.


In reply to Re: Re: Re: OT: Getting people to use tools by Rich36
in thread OT: Getting people to use tools by logan

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":