A prerequisite for successful internal collaboration is a culture which is conducive to such collaboration. Projects such as internal wikis tend work better, for example, if those involved in creating them are technically savvy, freely share knowledge, have flexible hours, and have strong managerial support (Kelly, 2009). All this presupposes a baseline level of trust and communication between employees, as well as between employees and their managers.
Internal collaboration projects often fail when their intended purpose is not entirely clear, but having the necessary resources and institutional support are also key. The intended software must be able to fulfill an institutional need that might not otherwise be achieved (Suarez, 2007), and those in charge must be entirely clear on what that need is and how the application can fulfill it. Similarly, management should be able to convey the benefits of using the new technology without appearing to coerce staff into it.
Finally, once it has been established that the application is apropos, that staff can handle the technical demands, and that management is supportive and encouraging about using it, staff must make an effort of their own to update it regularly. This can take any form from email notifications of changes to setting aside time on a regular basis to look the collaborative effort over. However, if it is done diligently and thoroughly, organizations can end up creating a resource that will prove its value to them many times over.
References
Kelly, W. (2009). "Corporate Culture, Not Technology, Drives Online Collaboration." Web Worker Daily.
Suarez, L. (2007). “When Wikis Won't Work: 10 questions to ask before full adoption.” elusa.
I agree that the need for a clear objective is crucial. As well as universal support from employees and management. If everything is set up correctly from the beginning then you can have a great resource that will continue to grow and flourish over time. Great resources you cited.
ReplyDelete