Comments on: New Tools, Same Problems on IT Projects http://www.philsimonsystems.com/blog/management-blog/collaboration/collaboration/ Musings on technology, management, books, writing, and whatever else piques my interest. Mon, 06 Feb 2012 15:18:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Social Networking in the Workplace http://www.philsimonsystems.com/blog/management-blog/collaboration/collaboration/comment-page-1/#comment-133 Social Networking in the Workplace Mon, 23 Nov 2009 10:24:40 +0000 http://philsimonblog.com/?p=380#comment-133 [...] actually addressed this a while back in a previous post. To recap, I’d cite three main mistakes. First, organizations often fail to implement usage [...] [...] actually addressed this a while back in a previous post. To recap, I’d cite three main mistakes. First, organizations often fail to implement usage [...]

]]> By: Martin Wildam http://www.philsimonsystems.com/blog/management-blog/collaboration/collaboration/comment-page-1/#comment-81 Martin Wildam Tue, 06 Oct 2009 15:45:59 +0000 http://philsimonblog.com/?p=380#comment-81 EMail is for messages of temporary interest. I think this is the core issue that many are not aware of. Every information that is business related or of longer interest than until next week should go into the appropriate location - whether it is a Wiki, DMS/ECM, Forum or whatever (a Wiki is also not the all-in-one system suitable for every purpose). In general I notice that there were better times. Nowadays in nearly every company there are multiple systems containing information: At least one Wiki, one Forum, some CMS or/and DMS, file shares and so on. In these days it is important to specify what information should go where. Under the hype word "ECM" people try to have one single container where they can drop everyting into. I think this can be dangerous because some end up with a big pot of everything and nobody knows what stuff is in there because nobody wants to maintain meta information either. I think the best way is to have one Wiki, one Forum and one DMS/ECM like system and there must be a simple and clear spec what should go where. All the DMS and ECM systems I have seen lately do lack drastically in either the Wiki, Forum or DMS features, so I don't think there is a good all-in-one product available yet. EMail is for messages of temporary interest. I think this is the core issue that many are not aware of.

Every information that is business related or of longer interest than until next week should go into the appropriate location – whether it is a Wiki, DMS/ECM, Forum or whatever (a Wiki is also not the all-in-one system suitable for every purpose).

In general I notice that there were better times. Nowadays in nearly every company there are multiple systems containing information: At least one Wiki, one Forum, some CMS or/and DMS, file shares and so on.

In these days it is important to specify what information should go where. Under the hype word “ECM” people try to have one single container where they can drop everyting into. I think this can be dangerous because some end up with a big pot of everything and nobody knows what stuff is in there because nobody wants to maintain meta information either.

I think the best way is to have one Wiki, one Forum and one DMS/ECM like system and there must be a simple and clear spec what should go where. All the DMS and ECM systems I have seen lately do lack drastically in either the Wiki, Forum or DMS features, so I don’t think there is a good all-in-one product available yet.

]]> By: Phil Simon http://www.philsimonsystems.com/blog/management-blog/collaboration/collaboration/comment-page-1/#comment-80 Phil Simon Tue, 06 Oct 2009 07:40:36 +0000 http://philsimonblog.com/?p=380#comment-80 Good points, John. I suppose that I'm holding clients up to a higher standard. As consultants, we absolutely bounce around, not that we should be held to a different standard. I just expect more from those who don't bounce as much. Good points, John. I suppose that I’m holding clients up to a higher standard. As consultants, we absolutely bounce around, not that we should be held to a different standard. I just expect more from those who don’t bounce as much.

]]> By: John Henley http://www.philsimonsystems.com/blog/management-blog/collaboration/collaboration/comment-page-1/#comment-79 John Henley Mon, 05 Oct 2009 23:11:58 +0000 http://philsimonblog.com/?p=380#comment-79 As you imply, email is ubiquitious, which is why it's still the de facto collaboration tool. For instance, since I bounce around amongst various clients, I'm not connected to their sites in a lot of cases, and can't keep my documents updated on their wiki/shared sites. But I can send the project team an email with attachments. It's really a losing battle, assuming they keep the sites within their private network. We will likely see some progress with cloud-based sites, like Google Apps and Central Desktop, but those are hard to adopt for most organizations, and open up a ton of security and privacy questions. As you imply, email is ubiquitious, which is why it’s still the de facto collaboration tool. For instance, since I bounce around amongst various clients, I’m not connected to their sites in a lot of cases, and can’t keep my documents updated on their wiki/shared sites. But I can send the project team an email with attachments. It’s really a losing battle, assuming they keep the sites within their private network. We will likely see some progress with cloud-based sites, like Google Apps and Central Desktop, but those are hard to adopt for most organizations, and open up a ton of security and privacy questions.

]]>