The news from Google this week that the Wave has crashed and burned was a bit of a shame. I had high hopes for this development, but sadly, the platform was just too hard for people to get the hang of.
One of the reasons that the social web - particularly social networking and blogging - has done so well and grown so dramatically in the last five years is because it is easy to do. You don't require a high degree of technical skill, you can point and press and it takes moments to share stuff with others.
Despite the anticipation, the huge build up, the long wait for a Wave invite, once faced with their Waves, most people tended to look at it blankly, realise they had no idea where to start and quietly put it back in the box - a bit like an IKEA cabinet where you can see the screws are there but they are taped so tightly to the packaging you never get round to putting it together.
There were some excellent bits to Wave and I suspect that they will be used elsewhere - the rumoured 'Google Me' might pick up a few or perhaps they will build in some additions to the rather lame Buzz.
I am a big fan of Google's development processes and think they are to be applauded for continually exploring what else we can do (even though I have serious and long-term misgivings about the potential for misuse of power and information that exists around an organisation so large having so much information in its control). What these clever folk need to always keep in mind is that for the web to work it has to be easy. Geek it up for mass use and you are on a hiding to nothing.
Given we are talking Waves here, Google - and others - need to remember that many on the web are paddlepusses, delighted to play in the shallows but not yet ready, willing or able to take on the big surf.
So perhaps the big lesson for Wave is make sure the box contains clear and simple instructions next time around. The failure was perhaps not so much the product itself, but the communication that surrounded it. Building the anticipation is fine to a degree, but if the why, how and what for is not clearly communicated then expectations are dashed and reputation suffers. Which, if I recall correctly, sits somewhere in Lesson 101 Communications Management...
Earthquake changes communications landscape
If there is an organisation left in New Zealand that has, post-February 22 - failed to appreciate the power and potential of online and social media then seriously - we need to talk.
The ferocity and scale of the second Christchurch earthquake meant that organisations were forced to leave 'old' communications processes behind and venture in to uncharted waters as the urgent need to communicate outweighed entrenched opinions of how 'communication' should be undertaken.
I take my hat off to all those involved in the post-quake communication, many of whom were having to deal with both the professional and personal aftermath of the quake.
For some, that meant learning to use 140 characters or less while under great stress, for others, it was simply about saying 'I don't know - but I'm finding out'.
I would particularly salute Christchurch City Council's communications team and the many volunteer techies who built valuable and vital web platforms - sometimes in hours - so that people could access information that helped them towards the basic necessities of life.
Lots of people will, in the months to come, pontificate on what was good and what was bad, the lessons to be learned and so on. As for me, I think that unless you have lived through such an experience, you can't legislate one way or another. Those involved have done the best possible job in extreme circumstances with what was to hand.
Post-quake communications will continue to be vital for the Canterbury region for many years ahead, long after the world at large has switched its gaze elsewhere. Christchurch communicators - and all of us involved in this line of work - are in this for the long haul. So Kia kaha. And well done.