I recently was forced to describe Web2.0 as a “Multi-Headed Beast”, and as the numbers of heads went up from Cerberus to Hydra proportions, I thought I’d whimsically arrange them into a spectrum of Web2.0 adoption, beginning with the ignorably trivial and working through towards the more larger goals of Web2.0; the result led to blind alleys and confusion, so I was forced to split it into two parts:
First, I propose a list of (some of) the stages of Web2.0 adoption:
- “We have wikis, internally”
- “We have blogs, internally”
- “We have employees who write blogs”
- “We have employees who write blogs, hosted upon a corporate blog server”
- “All our press releases are posted on the blogserver and have a RSS feed”
- “Several of our CxOs have got blogs”
- “The CEO has a blog and actually writes his own postings”
- “We have wikis, externally, and allow employees to modify them”
- “We have employees who read and comment upon blogs of their peers, partners and customers”
- “We assign our employees a significant percentage of time to write, read and comment on blogs”
- “We have wikis, externally, and allow anyone to modify them”
- “We stopped writing press releases, and started communicating with people instead”
- “We wash our corporate laundry in public on the blogserver”
- “We disabled AJAX hyperlink popups, realising they are evil”
- “We fired our public relations and marketing staff, realising they are no longer relevant”
…and then there is the list of Web2.0 things which are NOT REALLY Web2.0 things – ie: things you can do without actually achieving anything:
- “Our website contains a mashup with google maps”
- “We sell hardware and software to ‘web2.0-focused’ startups and service providers”
- “We sell software and consultancy to ordinary companies which want to do blogs and wikis internally”
- “Our developers live and breathe AJAX, and have enabled cute popups on all our hyperlinks”
More suggestions are welcomed in the comments section. 🙂
Leave a Reply