1) it must be sufficiently expensive. free is bad
2) i must convince everyone on my department that this is "the new way" that we operate (i.e. everyone has to use trello just like I would)
3) i must show through some pseudo science how it improves efficiency to several layers of management
Unless something is super compelling, it's not worth the effort. And if it is super compelling, it probably won't be approved anyway.
I guess I'm pretty jaded about the whole thing. If there is a neat tool, or some productivity enhancement/stress reducer, I usually just find a way to use it myself under the radar and don't share it with anyone (which offends me greatly as it's a terrible waste).
I'd actually have to go through that process for emacs 24, though in that case it's getting past the IT gatekeepers and proving to them that emacs 24 won't bring down the cluster. So I find a way to compile and run it and just don't talk about it a lot.
But anything web appish is out of the question. I settle for org-mode in emacs, but it'd be nice to collaborate. Sadly with our process of onboarding something, there's no room for experimentation or feeling something out or developing a workflow that would be worth demonstrating.
I used to work at a client site where they wanted us to list all of the tools we used (as software developers) because they didn't want us to use these "computers" that we were using, in their offices on their network, and instead they wanted us to all code using citrix dumb terminals.
I no longer work at that client site, or for the company that sent me there.