Skip to content

Using Technology to Improve Collaboration

Simple, single functionality tools are great for collaboration. I’ve been involved in several implementations of larger-scale systems for collaboration (like Sharepoint). Adoption is generally slow, unless the tool is marketed heavily in the organization and integrated into workflow. In contrast, simple tools like wikis, Twitter, YouTube, blogs, and social networking services can help to improve collaboration without the challenges of complex software systems. The same can be said of learning management systems. It’s much easier to learn a single tool that to learn an entire system. Using technology to improve collaboration (via Harold Jarche) provides an introduction to improving productivity through web technologies.

2 Comments

  1. George
    See my blog reply to this post. http://bradleyshoebottom.wordpress.com/2009/12/14/reply-to-george-siemens-using-technology-to-improve-collaboration/

    Monday, December 14, 2009 at 7:03 am | Permalink
  2. Nicola wrote:

    I agree that more natural collaboration happens more quickly and less expensively than system wide implementations and I’m also starting to consider more whether system wide implementations do not actually achieve as effective breaking down of silos.

    With some of the projects I have recently been involved with, when offered a menu of tools, there appears to be a tendency to think in terms of organisation of their intended collaborative partners – operationally rather than cross/multi-functionally i.e. they might choose to collaborate around a project and try and seek as many different views whilst doing the project.

    If they were not doing that before then all well and good, but it could go much further. I didn’t find that the statistics highlighting the improved productivity in the report sufficient enough – exactly what information is flowing and how is that better – for whom?

    I haven’t often heard people in my organisation or in inter-agency discussions looking at what are the problems that might be happening or could happen and whether these could also be problems that could happen in other non-related projects. They could use a system search tool or function but they might not think about it at all. It doesn’t naturally come up in the conversation.

    Friday, December 18, 2009 at 1:04 pm | Permalink

One Trackback/Pingback

  1. [...] work processes in 2010 so we can work together more efficiently and productively. Many thanks to George Siemens and Harold Jarche for their pointers to this [...]