Wikis, blogs, IM chats, and cloud drives, all types of collaboration tools. When I think about implementing new tool first thing that comes to mind (after my “OMG this is going to make things so much easier”) is what old crab is not going to use this? We all work with them – don’t deny it.
This is a collaboration barrier, and not the only one. Other barriers include:
- Conflict between department schedules, budgets, goals, and interest
- Learning to balance the roles between the “hired role” and the “collaboration role”
- Giving the collaboration value- “what will I get out of it?”
How do you solve the barriers? A couple of suggestions pulled from, Hutch Carpenters post “Enterprise 2.0: Culture Is As Culture Does” and Morten T. Hansen’s “When Internal Collaboration is Bad for Your Company” .
1. Eliminate the option to use something different (Carpenter, 2009).
Carpenter recommends when implementing a new collaboration tool to eliminate the option to use something different. If you want to start using IM chats, instead of responding to emails send them a message via chat and no other way.
2. When introducing the software or change provide a sense of the future with the change. Show them what it will be like if they make the change.
3. Create incentives. It is difficult to change or desire to change and put in extra effort to use something new unless their is an acceptable answer to “what do I get out of it”. Hansen encourages determining the rate of return before jumping in. Is it going to be worth it both financially and efficiently.
For every barrier there is a solution.