Here in Franksville, I think it’s all about creating collaborative software that doesn’t get in the way. A long time ago I wrote a little thing called Sidekick that allowed instantaneous task switching. It was a big hit back then, simply because it helped people do the jobs they were meant to be doing without distraction.
It should be just like that with collaborative tools. Sure, they need to support the need for aggregated management information, but who wants them to get in the way of what you want to do? Their adoption should be easy. In the old days I taught an entire programming language, Turbo Pascal, in a mere 300 pages. I’ve seen far bigger instruction manuals out there for collaborative software that does much less. Or probably doesn’t get used.
Put bluntly, it doesn’t matter how many features your software has if people are confused by its complexity. To work as a true team we need tools that are ‘desirable’ enough for strong adoption at grass roots level. Have you/we got them? And does your office truly work without walls? Let me know what you think.