One of the repeated findings in my study was the user's awareness that the wiki was only going to be valuable if everybody was participating. They spoke of an awareness that a solo effort was a waste of time and effort.
Below is my first try at mapping the interactions between these concepts and uses the actual labels used by the participants in the study. There is minimal theory in this framework. Each link is based on evidence in the data. I share it because I am interested in feedback, both from practitioners and academics. Not just on the model itself, but also if people have seen similar frameworks published. I'm sure I cannot be the only one seeing these interactions in the wild?
The key for my study seems to hinge around group participation in the wiki. This participation generates both tangible and intangible benefits which can boost trust and encourage further spontaneous participation which was the hallmark of all the successful wiki implementations in the study.
Many people currently talking about Enterprise 2.0, including Andrew McAfee himself, mention the process of evolution where both the functions and even the tools themselves are modified or replaced over time to best suit the needs of the business. Often the idea of success or failure is based on the notion of participation. For example, Safe-Fail can be useful to detect the success or failure of systems based on the concept that participation in these systems is an emergent behaviour of a complex system, so it is unreasonable to be able to predict beforehand which tools will gain participation simply by comparing software features with business requirements.
I am interested in three areas surrounding this:
- What drives an employee to use or not use a tool?
- What part does the culture of the organisation play in this process?
- What can be done to kick start a successful adoption?