As an almost constant home worker, my work connections are 90%+ virtual. I rely heavily on a variety of collaboration tools to help me overcome the barriers to successful engagement, construction of trusted networks and getting the job done in a geographically dispersed team.
- I like how Phil puts across the plethora of tools and scenarios that are available and that the choice of tool really matters in influencing the success factor of the collaboration.
- I like how he emphasises the need for informal communication and collaboration tools like (Facebook & Twitter) to help build trust and relationships and help to bridge that gap/void of human contact in the virtual space.
- I like how he describes the appropriate uses of asynchronous and synchronous communication and collaboration tools to meet the needs of the scenario or size of team involved.
- I like the workflow framework – it’s a great launch point for starting this conversation in your team or organisation, to drive out the thought processes of the community involved to choose the best set of tools to suit their needs.
As someone who is passionate about increasing the collaborative momentum within the teams I work in, I’ll be using this framework as launch point for some of those conversations. These conversations may not be ‘game changers’ for everyone, everyone is different and experiences different levels of comfort around making a change.
However, I do believe if organisations and enterprises are going to bring about a cultural shift in how they collaborate and communicate.
It needs to recognise:
- The need to change – if things stay the same, then they’ll get worse not better
- People and situations need different tools, and they need to invest in providing that variety – so that people can make choices
- People need to educated and shown how to change, finding and using ‘champions’ is a great way to help that happen.
Steve Richards has mentioned that he has used another approach to analysing the appropriate types of collaboration required.
thx for the input Steve.