Re: Resistance to using RDi

That's a scarily accurate narrative Buck. For me, the hump I had to cross
wasn't so much SEU to RDi. We've all used Word, as you say, so it not that
big of a hurdle. The big change is PDM or whatever change management tool
you're using. Flipping through your library and getting to the source you
want to edit is very fast in PDM, and it might always be faster. I found
value when I was able to organize all that stuff in a source library into
whatever project I'm working on. So, I'm not having to flip though a large
source library or list of checkouts. Once you're able to navigate source
that been filtered by filters or your CM tool plugin, RDi becomes much more
efficient, or at least more organized.

What I'm saying is that if you're using Ctrl-Alt-Q to regularly maintain
source, you're probably not going to see much benefit.

Here is an example of how I did it:
- Connection for production, test, and development library lists
- Filter pools called Active, OnHold, and Closed.
- Filters created within the Active filter pool reference the *USRLIBL, so
that when they're opened in the various connections, you see the right
source. Each filter is a project task for me.
- CM tool helps moving between the levels, but this method makes it easy to
do it manually.