Complexity theory: lessons from the Savannah


From time to time it’s instructive (and fun) to explore other systems and theories, as a way of learning and coping with problems in our projects, company or wider business environment. Take, for instance complexity theory and life in the Kruger National Park.

Broadly speaking, complexity theory suggests there is an underlying natural order to the behaviour and evolution of complex systems - be they ecosystems, financial systems, business operations or herds of buffalo. The following clip illustrates how herds and prides comprise sub-systems in the greater (Savannah) system. Each buffalo (or lion) operating with its fellow herd (or pride) member to form a unit, seeking to achieve a common goal, without anyone of them managing the operation! Each unit in the clip responded to the action of the other (and a third party intervention - in this case that of the crocodiles) - and together effected a pattern of self-organising behaviour, where the group was responsible for dividing and attacking the target. Something that each individual could not have achieved alone.

In other words, the disparate elements worked together in a self-directed manner to achieve coherence in the overall outcome. With each actor having some freedom to attack or kick from a certain angle or at a given target, allowing them to spontaneously adapt to the situation - all elements of ’survival learning’.

So what are the implications for our work with people, information and technology?

Many organisations, in particular legal and professional services firms, are eternally challenged with ‘managing’ knowledge (and associated spin-offs for innovation). Until recently, they have been trying to do this through standardised inflexible top-down controlled systems, which require ‘knowledge’ to be distilled, refined and polished (all as separate time consuming activities to people’s daily work load), and then ‘filed’ in pre-determined siloed categories with associated taxonomies. Not much room in there for self-directed action!

That has led some to implement more flexible solutions and processes - including the use of social tools. Complexity theory suggests that, given enough latitude, people will self-organise and bring about their own natural order by using tools such as wikis, blogs, tagging, etc, to suit their information and process needs. (Social tools having the innate flexibility to support that type of behaviour.) That has direct implications, amongst other things, in respect of any top-down structuring of content, and managerial support and direction in the use of the tools.

It follows that people should be allowed and encouraged to use the tools to create their own view of the information, by tagging, linking and bookmarking content which is useful to them - i.e. bottom-up activity. Not only will that help the individual later find and use the content, but when each individual’s activity in the wiki is aggregated with that of others, it creates a collective intelligence and signals about the information people find most useful and the way they are categorising/labeling it to promote its future findability (because people use terms and content which are relevant and useful - rather than ‘miscellaneous’). As people use the tools, and reflect on and update the information/knowledge therein, they learn how to adapt their behaviour and what works best in their circumstances.

In other words, this behaviour is self-directed and emergent because it is dependent on the current issues and opportunities people have to deal with. Those issues and opportunities in turn impact on the value of yesterday’s information, which usually needs constant attention and updating to ensure it is current and relevant, so as to be able to help in solving today’s problems. So, as people query, discuss, update and re-categorise information, they leave crucial footprints and create new information - all of which can be captured (as part of the participation process) within the social tools, and collated to form new information which is fed into the stream of current awareness people use to make decisions about the issues they face. As such, trying to plan for and create wholly top-down structures (like categories and taxonomies) for information, and responsibilities for its capture and upkeep, is somewhat futile. That approach cannot reflect real-time changes and learning derived from people’s experience with the system.

And the take-away point here is: Allow people to self-organise in their use of social tools, and the creation, updating and maintenance of information/knowledge therein.

As I outlined in my last post, that will require businesses to take a different tact regarding control - i.e. stepping back and letting people develop their own patterns rather than trying to predict and standardise the structure of information and its use from the outset.

But that doesn’t necessarily mean a wholesale departure from top-down categorisation since the system may, to a certain extent, still depend on the interactions with certain pre-defined/categorised elements. Nor does it mean that the use of social tools, and the management of information therein, should be devoid of strategic planning for their development, enhancement and future growth. Planned emergence can play a key role here in helping to ensure we develop our ideas, knowledge and expertise, and systems in support thereof, in a way that helps us best deal with our everyday problems and ambuguities. As the lions demonstrated, it’s just not enough to catch your prey, you’ve got to be able to follow through in uncertain rapidy changing circumstances.

  • Comments Off

The spiral of wiki adoption

In an earlier post I indicated that wiki ‘adoption’ refers to the stages through which users typically progress before committing to a new technology, with different adopter ‘types’ (e.g. innovators, early and late adopters) progressing through the stages at different times and speeds. Perhaps an even simpler (although less scientific) way of categorising users lies in the distinction between those who are technical (e.g. technologically familiar or curious) or non-technical, with ‘technical-users’ more readily adopting wikis and associated concepts of teamwork, knowledge capture and sharing, and learning therefrom. ‘Technical users’ tend to be ‘innovators’ and ‘early adopters’ often comprising people from technical companies and engineers. In fact, my survey of 102 companies corroborates this generalisation, with the greatest proportion (37.26%) of participants coming from the IT sector followed by the professional services sector, and 22.55% being IT engineers and 15.69 being consultants.

The survey results indicated that high levels of self-learning (69.93% of responses) have been supported by peer-to-peer learning (18.18%) with very little targeted/tailored training (1.40%) or issue of best practice/usage guidelines (10.49%). Popular mechanisms used to supplement self-motivated usage and ‘unlearning’ of older inefficient yet familiar habits include information being placed on to the wiki, people being involved in projects using a wiki and emailing links to the wiki. Those mechanisms moved users rapidly through the first adoption stages of becoming aware of the wiki, to understanding through trial/experimentation with the wiki.

The Wiki Adoption Spiral depicts how ‘technical-users’ move through adoption stages and spread wiki usage virally to later adopters. It reflects that:

  • adoption stages for ‘technical users’ (constituting the first adopter categories) are shorter and converge as they proceed quickly through initial (awareness, understanding and trial) stages, creating their own ‘transition mechanisms’ involving self-learning and experimentation with wiki use.
  • adoption categories and processes are fluid, as different users can be drawn into the process without early categories having completed the ‘typical’ cycle. For example, due to organic growth other categories maybe made aware of the wiki prior to its ‘adoption’ (e.g. through involvement in projects wikis), and commence their adoption process.
  • progress through stages can be halted (i.e. no growth through abandonment or rejection) if there is no perceived ‘need’ to use the wiki and/or barriers are not overcome.

Whilst early adopters more readily enter the adoption process because they are more technically competent/inquisitive, the implication from the above points is that top-down support /facilitation is equally important for developing good ‘wiki’ practices within the initial adopter group as for later adopters. Such facilitation involves generation of a shared understanding about collaboration goals, wiki purpose, responsibilities and ‘gardening’ practices. The experience/knowledge of those adopters can then be coupled with other transition mechanisms (e.g. more ‘technical training’, involvement in projects using a wiki and information being made available on the wiki) to accelerate the diffusion process to other adopter categories.

The high level of ‘learning by doing’ and peer-to-peer support illustrates an opportunity for users to participate in a collaborative learning experience, which provides an ideal platform for encouraging communication and collaborative behaviours in general (e.g. helping transfer knowledge/ideas throughout the company, working across organizational boundaries and learning from past experience/best practices of others).

Although reliance on email and familiarity of other tools may illustrate a reluctance to ‘unlearn’ habitual less effective work practices, there needs to be a balance between directive wiki usage and support for different communication styles as people become accustomed to using wikis and the different capabilities they can provide. That also requires responsiveness to feedback and anlyses of ways in which existing tools can be integrated with wikis to best support people in their work.

The spiral of wiki adoption


In an earlier post I indicated that wiki ‘adoption’ refers to the stages through which users typically progress before committing to a new technology, with different adopter ‘types’ (e.g. innovators, early and late adopters) progressing through the stages at different times and speeds. Perhaps an even simpler (although less scientific) way of categorising users lies in the distinction between those who are technical (e.g. technologically familiar or curious) or non-technical, with ‘technical-users’ more readily adopting wikis and associated concepts of teamwork, knowledge capture and sharing, and learning therefrom. ‘Technical users’ tend to be ‘innovators’ and ‘early adopters’ often comprising people from technical companies and engineers. In fact, my survey of 102 companies corroborates this generalisation, with the greatest proportion (37.26%) of participants coming from the IT sector followed by the professional services sector, and 22.55% being IT engineers and 15.69 being consultants.

The survey results indicated that high levels of self-learning (69.93% of responses) have been supported by peer-to-peer learning (18.18%) with very little targeted/tailored training (1.40%) or issue of best practice/usage guidelines (10.49%). Popular mechanisms used to supplement self-motivated usage and ‘unlearning’ of older inefficient yet familiar habits include information being placed on to the wiki, people being involved in projects using a wiki and emailing links to the wiki. Those mechanisms moved users rapidly through the first adoption stages of becoming aware of the wiki, to understanding through trial/experimentation with the wiki.

The Wiki Adoption Spiral depicts how ‘technical-users’ move through adoption stages and spread wiki usage virally to later adopters. It reflects that:

  • adoption stages for ‘technical users’ (constituting the first adopter categories) are shorter and converge as they proceed quickly through initial (awareness, understanding and trial) stages, creating their own ‘transition mechanisms’ involving self-learning and experimentation with wiki use.
  • adoption categories and processes are fluid, as different users can be drawn into the process without early categories having completed the ‘typical’ cycle. For example, due to organic growth other categories maybe made aware of the wiki prior to its ‘adoption’ (e.g. through involvement in projects wikis), and commence their adoption process.
  • progress through stages can be halted (i.e. no growth through abandonment or rejection) if there is no perceived ‘need’ to use the wiki and/or barriers are not overcome.

Whilst early adopters more readily enter the adoption process because they are more technically competent/inquisitive, the implication from the above points is that top-down support /facilitation is equally important for developing good ‘wiki’ practices within the initial adopter group as for later adopters. Such facilitation involves generation of a shared understanding about collaboration goals, wiki purpose, responsibilities and ‘gardening’ practices. The experience/knowledge of those adopters can then be coupled with other transition mechanisms (e.g. more ‘technical training’, involvement in projects using a wiki and information being made available on the wiki) to accelerate the diffusion process to other adopter categories.

The high level of ‘learning by doing’ and peer-to-peer support illustrates an opportunity for users to participate in a collaborative learning experience, which provides an ideal platform for encouraging communication and collaborative behaviours in general (e.g. helping transfer knowledge/ideas throughout the company, working across organizational boundaries and learning from past experience/best practices of others).

Although reliance on email and familiarity of other tools may illustrate a reluctance to ‘unlearn’ habitual less effective work practices, there needs to be a balance between directive wiki usage and support for different communication styles as people become accustomed to using wikis and the different capabilities they can provide. That also requires responsiveness to feedback and anlyses of ways in which existing tools can be integrated with wikis to best support people in their work.

  • Comments Off

Wikis - more than just a technology enabler for information dissemination?

I was curious to discover whether wikis are acting as more than just a technology enabler for information dissemination within organisations, and if they could serve a deeper function of facilitating changes to culture and stimulating organisational learning practices.

Consequently, I asked survey repondents and interviewees (i) what factors facilitate collaboration in the company, and (ii) whether those factors were prerequisites for successful wiki implementations or if wikis could be used as a means to develop better collaborative work practices. Common threads throughout the responses to (i) highlighted the need for organization-wide communications, access to/sharing of information/knowledge and a willingness to contribute/collaborate. In respect of (ii) views diverged. Some interviewees considered that, whilst wikis can provide a solution to the problem of locating information, they simply support existing information sharing/communication practices, since politics and cultural issues often hinder wiki usage. However, others considered that wikis encourage transparency by “questioning how people are thinking” and “can be used to increase awareness of people’s contribution to the workplace”.

Ross Mayfield of SocialText concurred with the latter view stating that “the best thing a wiki can do is to make transparent an existing culture. It can change culture overtime but if you try to introduce it into a controlling environment too quickly the entire notion of it will get slapped down”. That emphasizes the importance of ‘managing’ wikis’ incremental implementation so as to build towards a supportive user-community.

I also asked survey respondents to characterize their companies before and after the wiki implementation based on factors derived from the literature review. The overall picture is one of change towards ‘learning organisation’ characteristics (even if only slight in some areas). The greatest shifts occurred in relation to the level of information flows and new ideas being sought/tried, and people’s willingness to help one another carry out work. These changes appear to have occurred in a relatively short timeframe, with 47% of wiki installations being under a year-old. Most respondents considered that the wiki implementation has a minor (27.72%) to moderate (30.69%) impact in shaping companies’ characteristics.

Furthermore, the apparent benefits to be gained from wiki implementations in relatively short periods seem to have rather modest barriers/disadvantages, where survey respondents considered time to contribute (11.67% of responses), and reliance on email (11.67%) to be more significant barriers to wiki usage than culture (9.05%) and lack of managerial support (7.14%). That maybe partly attributable to the climate of openness and trust, and other learning characteristics, which organisations were considered to possess prior to the wiki implementation.

Consequently, the evidence suggests that wikis have improved organisational information flow, enabled people to work/communicate more efficiently and effectively, learn from past experience and share knowledge/ideas, in organizational contexts which are not averse to collaboration and learning. Accordingly, wikis have provided platforms for collaborative and emergent behaviour, which could not satisfactorily proceed through existing technology.

Time will tell whether the reported changes in certain organizational learning characteristics continue to grow and become more pronounced as wikis mature. Certainly, the level of grassroots’ implementations, facilitation and organic growth, illustrate instances of people at operational levels challenging mindsets regarding work practices and the utility of existing systems, experimenting with new solutions and adopting individual/team practices (including peer-to-peer learning) conducive to double-loop learning.

To grow this behaviour across the company and tap people’s “massive undeveloped potential” (Moss-Jones (2005)), management must be more alert to those initiatives and address barriers which inhibit wiki use. To that end, undertaking activities proposed in the wiki management cycle offers managers opportunities to engage in organizational learning practices and develop corresponding capabilities.

So, whilst there is much more to organizational learning and much more than can be supported by wikis alone, I think their use/management maybe informed by practices associated with the ‘learning organisation’ which in turn may facilitate changes to culture and stimulate organisational learning practices, making wikis more than a mere technological enabler for wider information dissemination.

Wikis - more than just a technology enabler for information dissemination?


I was curious to discover whether wikis are acting as more than just a technology enabler for information dissemination within organisations, and if they could serve a deeper function of facilitating changes to culture and stimulating organisational learning practices.

Consequently, I asked survey repondents and interviewees (i) what factors facilitate collaboration in the company, and (ii) whether those factors were prerequisites for successful wiki implementations or if wikis could be used as a means to develop better collaborative work practices. Common threads throughout the responses to (i) highlighted the need for organization-wide communications, access to/sharing of information/knowledge and a willingness to contribute/collaborate. In respect of (ii) views diverged. Some interviewees considered that, whilst wikis can provide a solution to the problem of locating information, they simply support existing information sharing/communication practices, since politics and cultural issues often hinder wiki usage. However, others considered that wikis encourage transparency by “questioning how people are thinking” and “can be used to increase awareness of people’s contribution to the workplace”.

Ross Mayfield of SocialText concurred with the latter view stating that “the best thing a wiki can do is to make transparent an existing culture. It can change culture overtime but if you try to introduce it into a controlling environment too quickly the entire notion of it will get slapped down”. That emphasizes the importance of ‘managing’ wikis’ incremental implementation so as to build towards a supportive user-community.

I also asked survey respondents to characterize their companies before and after the wiki implementation based on factors derived from the literature review. The overall picture is one of change towards ‘learning organisation’ characteristics (even if only slight in some areas). The greatest shifts occurred in relation to the level of information flows and new ideas being sought/tried, and people’s willingness to help one another carry out work. These changes appear to have occurred in a relatively short timeframe, with 47% of wiki installations being under a year-old. Most respondents considered that the wiki implementation has a minor (27.72%) to moderate (30.69%) impact in shaping companies’ characteristics.

Furthermore, the apparent benefits to be gained from wiki implementations in relatively short periods seem to have rather modest barriers/disadvantages, where survey respondents considered time to contribute (11.67% of responses), and reliance on email (11.67%) to be more significant barriers to wiki usage than culture (9.05%) and lack of managerial support (7.14%). That maybe partly attributable to the climate of openness and trust, and other learning characteristics, which organisations were considered to possess prior to the wiki implementation.

Consequently, the evidence suggests that wikis have improved organisational information flow, enabled people to work/communicate more efficiently and effectively, learn from past experience and share knowledge/ideas, in organizational contexts which are not averse to collaboration and learning. Accordingly, wikis have provided platforms for collaborative and emergent behaviour, which could not satisfactorily proceed through existing technology.

Time will tell whether the reported changes in certain organizational learning characteristics continue to grow and become more pronounced as wikis mature. Certainly, the level of grassroots’ implementations, facilitation and organic growth, illustrate instances of people at operational levels challenging mindsets regarding work practices and the utility of existing systems, experimenting with new solutions and adopting individual/team practices (including peer-to-peer learning) conducive to double-loop learning.

To grow this behaviour across the company and tap people’s “massive undeveloped potential” (Moss-Jones (2005)), management must be more alert to those initiatives and address barriers which inhibit wiki use. To that end, undertaking activities proposed in the wiki management cycle offers managers opportunities to engage in organizational learning practices and develop corresponding capabilities.

So, whilst there is much more to organizational learning and much more than can be supported by wikis alone, I think their use/management maybe informed by practices associated with the ‘learning organisation’ which in turn may facilitate changes to culture and stimulate organisational learning practices, making wikis more than a mere technological enabler for wider information dissemination.

 

  • Comments Off

A quick review of ‘learning organisation’ themes

In an earlier post I indicated that during my research on ‘Managing Wikis in Business’ I was interested in finding out how themes of the ‘learning organisation’ can aid and be reflected in the management of wikis in business, and the extent to which such management can in turn encourage organisational learning and foster collaborative behaviour. Whilst there is still some lack of clarity regarding the distinction between the ‘learning organisation’ (end form) and ‘organisational learning’ (means), interwoven themes are apparent and common to both.

John Moss Jones (OU) summarises those themes and their relationship as follows:

“In order to perceive the [learning organisation] concept the organisation needs to be perceived with a systems perspective. The leadership group is the prime mover in establishing vision and identity, and modifying the internal culture. The vision must give high priority to people issues to maximise learning, for people are the vital element in learning. The ongoing learning needs to focus on challenging existing mind-sets, and developing creativity, adaptiveness, effective team working, and feedback. And taking all these together, it is argued that the whole organisation needs to develop a culture which promotes all these themes continually.”

‘Systems thinking’ is a cornerstone of the ‘learning organisation’. It encapsulates the idea that business behaviour like complex systems. As such they should be viewed holistically in terms of their subsystem connections, and how changes to one sub-system affect or can be affected by other subsystems.

‘Leadership group’ refers to the new view of leadership, where managers are designers, stewards and teachers, and are vital for encouraging the generation and spreading of new ideas/practices about purpose, values and vision. ‘Vision’ requires the maximum number of people to contribute to and share a picture of where the organization is going in terms of its external context (e.g. target products/clients) and internal design, development and operation. ‘People’ includes the principal and often “massive undeveloped potential” that exists within every organization, and raises issues about creating and sustaining cultures/processes to tap that potential.

‘Learning’ refers to double-loop learning which requires challenging existing mindsets that form the basis of (possible out-of-date) behaviour and affect perception of feedback. It probes the cause of things going wrong at a system level rather than simply identifying and correcting errors within existing organizational routines. The ultimate goal being to spread such learning from individuals and teams throughout the organization, ensuring that work experiences are captured, consolidated and disseminated so as to create new capabilities as a whole.

Within that learning process, ‘teamwork’ involves working across organisational boundaries, questioning routines and providing feedback. ‘Creativity’ and ‘adaptiveness’ are required to cope with rapidly changing environments and act upon learning by altering behaviours. That requires generating attitudes, processes, skills and knowledge, and translating them into more effective organisational practices. Finally, feedback is central to systems thinking, and critical to learning and adaptation, because “current perceptions of what is going on must continually be as close as possible to ‘reality’” (Moss-Jones (2005)).

A quick review of ‘learning organisation’ themes


In an earlier post I indicated that during my research on ‘Managing Wikis in Business’ I was interested in finding out how themes of the ‘learning organisation’ can aid and be reflected in the management of wikis in business, and the extent to which such management can in turn encourage organisational learning and foster collaborative behaviour. Whilst there is still some lack of clarity regarding the distinction between the ‘learning organisation’ (end form) and ‘organisational learning’ (means), interwoven themes are apparent and common to both.

John Moss Jones (OU) summarises those themes and their relationship as follows:

“In order to perceive the [learning organisation] concept the organisation needs to be perceived with a systems perspective. The leadership group is the prime mover in establishing vision and identity, and modifying the internal culture. The vision must give high priority to people issues to maximise learning, for people are the vital element in learning. The ongoing learning needs to focus on challenging existing mind-sets, and developing creativity, adaptiveness, effective team working, and feedback. And taking all these together, it is argued that the whole organisation needs to develop a culture which promotes all these themes continually.”

‘Systems thinking’ is a cornerstone of the ‘learning organisation’. It encapsulates the idea that business behaviour like complex systems. As such they should be viewed holistically in terms of their subsystem connections, and how changes to one sub-system affect or can be affected by other subsystems.

‘Leadership group’ refers to the new view of leadership, where managers are designers, stewards and teachers, and are vital for encouraging the generation and spreading of new ideas/practices about purpose, values and vision. ‘Vision’ requires the maximum number of people to contribute to and share a picture of where the organization is going in terms of its external context (e.g. target products/clients) and internal design, development and operation. ‘People’ includes the principal and often “massive undeveloped potential” that exists within every organization, and raises issues about creating and sustaining cultures/processes to tap that potential.

‘Learning’ refers to double-loop learning which requires challenging existing mindsets that form the basis of (possible out-of-date) behaviour and affect perception of feedback. It probes the cause of things going wrong at a system level rather than simply identifying and correcting errors within existing organizational routines. The ultimate goal being to spread such learning from individuals and teams throughout the organization, ensuring that work experiences are captured, consolidated and disseminated so as to create new capabilities as a whole.

Within that learning process, ‘teamwork’ involves working across organisational boundaries, questioning routines and providing feedback. ‘Creativity’ and ‘adaptiveness’ are required to cope with rapidly changing environments and act upon learning by altering behaviours. That requires generating attitudes, processes, skills and knowledge, and translating them into more effective organisational practices. Finally, feedback is central to systems thinking, and critical to learning and adaptation, because “current perceptions of what is going on must continually be as close as possible to ‘reality’” (Moss-Jones (2005)).

  • Comments Off

Wiki Management Cycle

In my previous post I introduced the idea of using a process framework for managing the wiki implementation. Here’s some more detail about the concepts behind each of the framework’s processes:

Wiki Management Cycle

  • Identify ‘needs’: This requires focusing first on the business needs, collaborative behaviours and capabilities to be developed, then on identifying the technologies which can support those needs/capabilities.
  • Plan: Having identified a wiki as a suitable technology, its implementation and management must be considered. This should balance planned and emergent approaches to foster learning and allow patterns of use and self-sustaining behaviour to evolve over time, whilst providing direction/purpose to co-ordinate and guide efforts towards a shared vision of what is to be achieved. Consideration should also be given to the practical applications and purpose(s) of the wiki, how it will fit with existing technology systems and work processes, and the nature of facilitation (e.g. initial structuring and seeding of the wiki) to support and sustain use.
  • Adopt: Wiki ‘adoption’ refers to the stages through which users typically progress before committing to a new technology, with different adopter ‘types’ progressing through the stages at different times and speeds. Rogers’ Model of Technology Adoption Categories below illustrates the characteristic responses of adopters to technology innovation:

Rogers’ Technology Adopter Categories

Typically, those users become aware of a technology’s potential and then develop an understanding of it, which can lead to testing through trial use, and if successful, to its application in everyday work, before full adoption across the organisation as a key element in work processes. Whilst that path may not be linear, recognising the different stages may help to identify support/transition mechanisms to ensure each user-category is more likely to adopt the wiki, and help avoid its rejection, which may occur during any stage of the adoption process. In particular, the issue here is how to strike the balance between voluntary grass-roots adoption and directive use to encourage participation, raising considerations about the nature of training, teamwork, use of facilitators, support for different communication styles and unlearning of old habits regarding overuse of inefficient/ineffective technologies.

  • Maintain: Closely related to adoption is wiki growth and propagation of good practice throughout the organisation. Issues here relate to managerial support, content management and wikis’ integration with other systems and work processes. Of interest here is whether managers have in fact absorbed the advice from industry and academic literature indicating they should be directly involved in the implementation by leading by example, mandate and reminding, reducing barriers to use, encouraging experimentation with the wiki and monitoring its use for ideas and best practices then propagating them throughout the organisation. Content management is also a key issue. Since wiki content should become more useful, structured and navigable over time if people are updating, linking and tagging, consideration needs to be given to the mechanisms which best encourage that type of behaviour.
  • Evaluate: Of interest here is whether, and if so how, businesses are evaluating their wiki implementations. Such evaluation can be a mechanisms for encouraging feedback and learning from the implementation process, and allowing for revisions to implemenation plans, and wikis’ design, usage and maintenance. Measuring users’ progress through adoption stages and how often people are using wikis will provide some elementary figures on wiki diffusion and infusion in the organisation, and may provide grounds for investigating any barriers to the implementation process. However, more difficult issues relate to evaluation of wikis’ impact on bottom-line performance and development of organisational learning practices. Measurements focusing solely on bottom-line performance improvement in terms of accelerated project cycle times, reduced email overload and search costs may provide some hard data to support ROI, but they do not consider more important effects of wiki management/usage on organisational learning and collaborative capability development. Not only is it more difficult to establish direct causal connections between wiki management/use and improvements here, any evidence would be in the form of people’s opinions/perceptions.

Wiki Management Cycle

A
  • Comments Off

Wiki implementations - a change process

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

Wiki Management Cycle

Next Page »