====== Thoughts ======
Replacing a system or solution should be easy and fluent. When users get to a point where they are using outside systems or methods themselves, its about time to replace. 

It may be good to replace WITH the system the user is using, or to ask that user to list the 10 most important components of that system, and the 10 most important working components of the former system. Try to get a new system that combines the two. You want a mix of functionality that the old one supplied, with additional needed functionality.

====== Chat ======

Russell Briggs
1:16 PM
webex needs a facelift

Nick Yeates
1:17 PM
yeah its UI and many windows is confusing

Russell Briggs
1:17 PM
i'll invite you to my next gotomeeting and you can check out the interface

Nick Yeates
1:17 PM
ko

Russell Briggs
1:17 PM
i like it...its simpler and just works

Nick Yeates
1:17 PM
what u use gotomeeting for?

Russell Briggs
1:17 PM
same thing as webex...i just get so frustrated w/ webex sometimes i had to get another option
1:18 PM
so i pay for the GTM account myself 

Nick Yeates
1:18 PM
heh

Russell Briggs
1:18 PM
when you're on a 2 hour call and can't even read the screen because of scaling issues, then you tend to look for something that does work 

Nick Yeates
1:20 PM
yeah that happens sometimes....ive had to do that for our knowledgebase articles....i make em on my own wiki first, as it has tons of feature that are almost critical to have....and then copy/paste it over to our piece of crap
1:21 PM 
of course, mine doesnt integrate into other systems, or involve everyone in the company...so same issues with you and webex probly....takes a bit more for an organziation to migrate away from stuff that isnt optimal

Russell Briggs
1:21 PM
very true...

Nick Yeates
1:22 PM
im gonna have to keep that in mind for the future when I become a decision maker