The original wiki design principles (Wiki Design Principles) encourage emergent work and do not impose structure, process or rules, contrasting applications characterised by a top-down command-and-control mentality. That can allow people to work together in self-directed ways, encouraging levels of openness, autonomy and knowledge sharing which other systems (i.e. all systems in the organisation including cultural, managerial, structural and operational systems) could not well support. Consequently, a wiki implementation should be viewed as a change process rather than the introduction of a new technology per se.
Since cyclical process frameworks have been suggested for technology management in general – i.e. as means to aid consideration of technology’s role, effects on the organisation and nature of managerial activities/involvement, from existing literature I derived a wiki management framework to help assess how in practice businesses are managing wiki implementations and the utility of such a framework for managing the change process.
That framework includes the following processes: ‘Need’ Identification, Planning, Adoption, Maintenance and Evaluation. During my research I posed a range of questions to interviewees and survey respondents regarding their practices in respect of each of the processes. I’ll be discussing the responses in a later post.
Wiki Management Cycle
