As Scott has blogged, he came to visit us in Cardiff recently, while staying at the OU for a month on a fellowship. We had a lot of great chats, and while I failed to convince him of the ways of atheist, reductionist rationalism, I did manage to convert him to my succession metaphor for technology adoption.
I used this in my VLE book a while back, and it goes something like this (from the book):
When there is a new environment, for example barren rock, a few pioneer species, such as lichens begin to grow. The acid from these decomposes some rock particles, and their own death creates a coarse soil. This is suitable for mosses, which require little soil, and in turn these decompose to enrich and deepen the soil, until it is suitable for some grasses to grow. The process ends with the establishment of a stable, climax community.
In elearning terms, VLEs, and in particular commercial VLEs have acted as the pioneer species, moving in to the new environment and creating slight changes which make the habitat suitable for secondary colonizers. These might be seen as open source VLEs, or closely integrated systems such as portals and eportfolios. The kind of environmental changes wrought by VLEs include general acceptance of the elearning approach, integration with administrative systems, staff development, recruitment of enthusiasts, changes in assessment practice, acknowledgement of tools already used by students, and so on. Once these systems have been established, then the environment would be more receptive to systems that require more radical changes in practice, such as CMSs and PLEs.
The corollary of this metaphor is that there is a 'natural' progression. Now I think we should always treat nature metaphors with a bit of caution, but if one accepts that existing technologies change their environment, then this new environment becomes one in which new technologies can flourish. It may take time though - as with plant succession you can only jump from the barren environment to the climax community by a lot of intervention, for example bringing in lots of soil and species.
But I hadn't really taken the metaphor beyond this initial comparison, but in my conversation with Scott we began to explore it further. In particular, what are the conditions that prevent succession? It doesn't always occur in nature - for instance on a beach a big storm will wipe away some of the colonizing plants. If the barren environment is your patio for example, then human intervention by way of deweeding, will prevent the environmental changes required.
In terms of learning technology, what is the equivalent of the avid gardener, killing any weeds, grasses or mosses that threaten to grow on their patio? Because if we think that there may be a natural progression through technologies, then identifying these barriers helps the process continue.
One such barrier might be the investment people and institutions have put into the existing system. This is like the succession getting to a certain level, and then the gardener maintaining it at precisely that state. When institutions deploy a VLE there is a good deal of investment in other systems which communicate with it, in staff development, and expertise. There are also people whose professional identity becomes allied to that system - they become the 'Blackboard guy' or whatever. There is thus a combination of personal and institutional forces which are acting to stop succession going further. In our analogy this is like we've trained a group of volunteers to do all the deweeding and clearing of an area, so to allow succession to happen would mean upsetting a lot of people.
A second, more insidious barrier is that of commercial interests. If succession is about the gradual replacement of one environment with another, then those with a commercial interest a particular environment will seek to maintain that. In our analogy it's like the council have signed a contract with the purveyors of weed killer - they don't want the succession model to flourish. In learning technology this can be achieved through software patents, vendor lock-in, long term contracts, and the general promotion of a 'we solve your problems' attitude.
A third barrier might be the emotional attachment people have to software. I commented once before that although we justify software choices in terms of rational decision making around features, it is often an emotional, irrational preference, much like supporting a particular football team. Like with football teams we can only be monoamorous with software. The problem here is that we often don't appreciate we are arguing from this emotional attachment stance and cloak it in other languages - around integration, access or features. In the analogy then this is like the enthusiast who wants to maintain the environment at a certain state (maybe there are some wild flowers they are particularly fond of) and so don't want to let it alter.
There may be more, but I think tugging at the seams of the metaphor as it were, has helped me think about these issues. My new motto: Let's stretch this metaphor till it snaps.
