The first phase of our Google project, migrating 550 users across the globe onto the system for email, calendar, contacts and chat, completed last week. The project has run very smoothly so far, and it looks like we are in a good position to move forward into utilising Docs and Sites in the next few months.
One of the consequences of moving to Software as a Service is that improvements and upgrades of software move from being infrequent and extensive, to frequent and of varying impact. In the past seven days, new functions for the management of labelling, and to allow inbox preview have been rolled out (oh, and completely new word processor, spreadsheet and graphics applications as well, but we haven't deployed those yet).
The continuing changes to the tools will take a really big mind-set shift for most people. We get used to tools, including their limitations, and shape the way in which we work around them. If the tools continually change, our ways of working need to as well. And whilst for some this would be seen as positively exciting, I'm sure that there is going to be resistance from some to the idea that the tools continually change.
Eventually, I'm sure that people will generally get used to it. But it's this kind of fundamental difference between the SaaS model and more traditional software that will need continued support to help everyone adapt, and an empathy to the view that new isn't necessarily always welcomed by everyone. It's also an area where the, erm, “empathy-challenged” software engineering community sometimes struggle to understand that there could even be a problem.
There is a real risk that unless we help all to adapt to new functionality, a big divide will open up between those who can and those who can't.
mmitII 