Maybe the people you are developing these tools for are command line phoebes!. You may have run into non-analyticals.
You say you "just want to make their lives easier", but you thought
that maybe their lives are just struggle? You need to make them feel
smart and important (If you cannot have them fired!)
That is the definition of "Buy In".
Try making your code UI/browsers based.
I know you know that this is easy but they don't know that. ;)
Re: OT: Getting people to use tools
Replies are listed 'Best First'.
Maybe the people you are developing these tools for are
command line phoebes!
Ah, yes. We're on the same page. I actually did do a web interface, hoping that would solve the problem. No luck. I work in a unix house, and one of my end non-users is total command-line guy. He won't use aliases, command-completion, or shell prompts. I've tried to show him shortcuts ("You know, you could just use the alias 'll' for 'ls -lA'. It's already set up for you in your .tcshrc file."), and he won't do it. Even after demonstrating how it will make their jobs easier, nobody wants to play.
"What do I want? I'm an American. I want more."
I wonder the same thing about command line users (even occasional users) who have no clue about file-name completion. It drives me nuts to have to type a long multi-node file name, and can't understand why other people just do that instead of finding something that avoids it.