Google Apps Team Edition
In this post ars technia berates Google for trying to slip one by your local I.T. department. They argue;
Unlike the Powered by Postini product suite, Google Apps Team Edition is aimed at enabling user and group-level collaboration without the need for approval from the IT department.
Now I understand the mentality of the I.T. department. After all, they support your business applications. They need to make sure that the data is secure and that there is some method to recover the data in the event of loss. They also need the company to understand that the new Google apps may be a duplication of significant legacy knowledge management applications and sharing applications which are already in place (and perhaps even under utilized). And Helpdesk may be the first place employees will call for support.
I know the thinking. I used to be one of those I.T. guys.
But once the security and training issues are addressed, isn't it a better outcome for all if your users collaborate more rather than less? Isn't the goal of seamless communications and collaboration to enable faster and better decisions and project outcomes?
With the development of more and more web services applications, I.T. departments would do well to devise a strategy with their corporate leadership to address web services adoption.
After all, if you're using Sharepoint, Team Rooms, MS Project Server, individually or group shared documents on Google, Basecamp, Blogs, Wikis, Forums and any other number of applications, you're investing heavily in training and support. And your corporate knowledge is stored all over the place.
It makes sense to try new applications (especially if they're free and the "rules" are well understood.)
But in the end you'll need to agree on a data map - where stuff is kept and under what conditions, so your company can make informed decisions as to whether the newer products work well, how they'll be internally supported (if at all) and also when (and how) to sunset those duplicate legacy systems.
In the end, the decision should be a business and I.T. collaboration. Even "free" apps come at a cost.
I know the thinking. I used to be one of those I.T. guys.
But once the security and training issues are addressed, isn't it a better outcome for all if your users collaborate more rather than less? Isn't the goal of seamless communications and collaboration to enable faster and better decisions and project outcomes?
With the development of more and more web services applications, I.T. departments would do well to devise a strategy with their corporate leadership to address web services adoption.
After all, if you're using Sharepoint, Team Rooms, MS Project Server, individually or group shared documents on Google, Basecamp, Blogs, Wikis, Forums and any other number of applications, you're investing heavily in training and support. And your corporate knowledge is stored all over the place.
It makes sense to try new applications (especially if they're free and the "rules" are well understood.)
But in the end you'll need to agree on a data map - where stuff is kept and under what conditions, so your company can make informed decisions as to whether the newer products work well, how they'll be internally supported (if at all) and also when (and how) to sunset those duplicate legacy systems.
In the end, the decision should be a business and I.T. collaboration. Even "free" apps come at a cost.
