Â My personal view is that collaboration is hard.Â I want it to be simpler.Â I hope I can help make it simpler where I have influence.Â I’ve talked previously about making collaborative interfaces, in terms of email, suit the users that it serves (1,2).
Today’s “rant” is really about vendors not bridging the gap between the various areas that the user performs their work.Â The information workers we deal with day in, day out have a plethora of needs when it comes to the software they use.Â So let me write down my top 10 annoyances with collaboration:
- Poor interaction between the file system and collaborative systems.Â Why in most cases do I need to enter the collaborative application, click on attach, browse to theÂ file I want to attach then …..Â etc.Â Why is there not a method with most solutions for Right Click, Send To with a logical expanding menu to send the file to the application of choice.Â Take a lesson from Flickr here with their uploader tool and also a right click tool.
- Why even in recent releases of some instant messaging products can I not drag a file into the chat to send it?
- Within collaborative workspaces why do most vendors not consider import/export of data between workspaces, remembering that project spaces have finite lives before they become legacy, however elements of the projects will remain relavent and data may be required in other spaces.
- Why are most implementation of collaborative environments not self provisioning?Â Recently within my employer this trend has changed.
- When self provisioning environments are enabled how easy is it to delegate access control and is the act of producing the access list a straight forward process.Â In one example I see regularly the self provisioning workspace is excellent whereas the interface and directory for access management is god awful.
- If most of a users collaboration is in their email why don’t we utilise this more?Â Why do we insist the user must move data here, and there, and then over here.Â What the user sees is one thing that hasn’t changed in terms of folder structure for years, it has been defined by them to suit them.Â OK we IT bods may have migrated them from system A to system B but their folder system and emails are generally still there.Â Hence, they like it, they feel comforatable with it.Â They use it more than any other interface.Â Why force them to move data into collaborative workspaces for projects?Â Why not just share data within email files between users engaged on projects?Â If I had my way then every folder in a users mail file except the in-box or a “keep hidden” folder would be indexed for searching and retreaval by collegues.Â After all its a corporate system, the data is corporate.Â Someone is already saying “yes but what if someone sees data they shouldn’t”.Â Well training should help there, and how many of us know of examples of sensitive information being sent to large numbers of users via email?Â I can think of many examples.
- Reply to all with attachments ……rrrggghhhhhhh!!Â Default it to OFF, please!
- People who set themselves on IM to do not disturb all day long.Â There should still be a way of highlighting to that user that you need to chat to them.Â Perhaps by clicking on them and then your icon in their buddy list turning a different colour.Â Sametime 7.5 has selective do not disturbs, which are good, but my view is there are still times when I need to get someones attention and they may be on a conf call.
- Don’t fill portals with useless information!Â We hate it, so users will hate it.
- And finally ….. use subscription based approaches to collaborative software wherever possible.Â Train users of the benefits of subscription and feeds.Â Foster collaboration from ground up.Â Don’t be scared of corporate blogging.Â Worst case is if you don’t do it internally some of your employees will be doing it externally (case to point here).Â I’d love the opportunity to have a corporate blog internally and discuss items I can’t post here.Â I’d also like an aggregator as part of my desktop suite of applications rather than rely on bloglinesÂ at work.
Â In conclusion corporate collaboration needs to be user friendly, interactive between various interfaces and corporates need to open more to disruptive technologies and let their leading edge people use the new tools internally ratherÂ than force them to use them externally.