A colleague once told me that our old way of planning IT projects was like building a cathedral. Planning and more planning, construction according to solid architectural principles, years and years of building and at the end of it all you find that no-one goes to church anymore…. or at least not in the same way.
I have seen projects that have followed this model and taken so long to implement that by the time theyre done the world has moved on. I dont mean to completely reject this approach it is still fundamentally important for large projects where there are huge risks to control and dollars at stake, but this is not web20.
Web20 is about small simple viral solutions (with no licensing costs) that can be deployed by pretty well anyone. Rather than taking years, they can be rolled out in hours or accessed online in minutes. You could spend more time writing up a proposal to write a business case than you could installing and running a wiki or a blog tool.
Gartner calls them disruptive technologies, not because they have more functions and features but because they are simpler technologies that rely on social relationships. In other words all the complexity and all the value comes out of the social interactions that emerge around these technologies and not out of the planning matrix. You cannot plan for how a culture will emerge around these tools or where the community will take them. All i can say from implementing web20 for the past two years is that I never could have anticipated how colleagues would use them, it was their innovation, their genius and not the plan that has moved these things forward.
So lets look at another model. Web20 planning is like gardening. You prepare the ground, you plant the seed, you put in place supports and you watch and weed and adjust as things grow. You might have to uproot and move and occasionally some things just wont work – in which case they make it on to the compost heap to be reused. But, every once in a while there is the ‘volunteer’ something completely unanticipated and rare that shows up out of nowhere (am i going to far with the metaphor?).
Web20 needs to have planning but not the heavy handed traditional planning that is so basic to IT and IM thinking. Regardless of whether you like the gardening metaphor web20 needs a planning model that recognizes its organic, ephemeral and fundamentally social nature.
Gardening tips- making the metaphor practical
Prepare the ground – identify those groups that are likely to be open to these new tools and work with them; put in place broad guidelines and supports that keep things growing in the right direction, but,
Plant quickly the season is short – the faster they are in the ground the faster they grow in optimal conditions
Let them grow – stand back and let the culture emerge around the tools, support where you can through training and barnraisings, encourage social classification dont impose controlled vocab.
Weed and prune where necessary – have a small team of web 20 gardeners looking to consolidate duplicate content, promote proper naming conventions encourage social classification.
Make sure the garden fits within the overall landscape. recognize the information and knowledge created in web20 is valuable and needs to be integrated with traditional sources like document management systems, databases etc. See Olivia dehavilland and note google results include traditional docs but also wikis, blogs video accessible through one interface.
That reminds me i have to go rake leaves off the flower beds