How do you engage your team members when you implement collaboration tools such as blogs, wikis, Microsoft SharePoint and the like?
Here is a summary of the suggestions offered from users and experts in the field on the best way to implement collaboration tools and engage the target audiences:
· Make it easy and convenient for team members to use the tools to do small but important tasks. For example, checking a blog for information, or publishing an update on a specific item to a blog (rather than using email).
· Start small by engaging those team members that have a natural tendency to collaborate and are good early adopters. Form a tiger team and do a pilot project. You can work the kinks out before a larger roll out. It is easier to get additional team members to adapt once there is initial success.
· Create a short collaborative project to evaluate certain tools (or have one person do an evaluation) and share the pros and cons of each tool with the rest of the team. Then the team can determine which tool is going to be the most productive to the whole group.
· Make it fun and exciting too! Someone suggested running contests over SharePoint (scavenger hunts) or posting helpful notes that will get people thinking more and more about the value of the tool and its use for different projects.
· Have an official cut-off date for when an old system is no longer available for use. This should be a far off date that is easy to remember (like at the turn of the fiscal year the new system comes online). This lets people know that they have a deadline to learn the new system.
· The primary factor that enables adoption of a collaboration tool: A new project with no "incumbent" technology or process to change. So pick a new project, and work with the project team to select a tool for the project.
· Find an executive sponsor who sees the benefits of the collaboration tool, and its impact on productivity and the ability to meet the key business objectives, and get their support in making the tool an important part of conducting business.
· Provide the team with mini-training sessions, both formal and informal. A lot resistance to adoption has to do with the unknown and fears of wasting time. If you help your team overcome these fears, you are likely to get a much higher level of engagement.
· Overall, the collaboration platforms should be a productivity tool, not a burden. The tool should make some important aspect of one’s job easier. Whether that is something as simple as submitting a ticket to the IT department, or viewing HR announcements, it has to be sold to the user base as something that will improve daily work life.
· Also, at the end of the day, a tool has to be useful for the intended purpose. We too often see people thinking of all these tools as interchangeable, but blogs are more of a one-to-many tool as compared to wikis that are better at capturing widely held knowledge, which is different from SharePoint, which is much better at organizing document-focused work, e.g., word processing documents, spreadsheets, and presentations, with collaboration more often in a supporting role.








