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...
Cri-du-coeur for real communication as Cloud outage crashes confidence
Last week - and this weekend - saw major outages at Amazon and Sony. Gamers hoping to get down to some serious wins over Easter were struck by the fail - highlighted here on the Playstation blog, while Amazon's super fail affected sites far and wide, most notably, Quora, Hootsuite and Reddit.
Amazon's latest health reports show that things have improved since the problem occurred and, realisitically, this kind of thing is bound to happen as increasing numbers take to the Cloud as a means to manage server demand. Mistakes happen, sites get attacked, someone unplugs the wrong connection. What counts is the ability to keep customers, users and other stakeholders informed, up-to-date and confident that you can fix the problem as quickly as possible.
If your web presence is your main communication channel and you are rendered invisible by someone else's crash, what can you do? Hidden among the acres of copy written in the last few days, probably the most useful is over at ZDNet, where Phil Wainewright has some salutary lessons for the user.
But what of the providers themselves? What lessons should they learn? The greatest cri-du-coeur has been that Amazon failed to communicate clearly and effectively with its customers during the crisis. Personally, I'm not surprised. Without exception, today's web giants are, I believe, appallingly bad at communicating with their users. For many years they were able to shield themselves behind remote access walls, responding only to emails (eventually), with very little human contact (if at all) and, in latter years, using minimal statements on blogs and webwalls to update users in a crisis. But believe me boys, (as mostly boys you are) a blog post does not mean you have 'communicated', created trust, understanding or cemented the necessary forgiveness to maintain your licence to operate.
Anyone who has ever tried to communicate directly with Facebook, Google, Amazon or other large web corporates will know exactly the level of frustration I am talking about. In a world where instant two-way communication is the lifeblood of a system that champions trust, engagement, transparency and the user as the vital ingredients of the service mix, our web giants are lacking in their ability to generate and maintain the kind of real relationships they tout so readily on the global stage but which they spectacularly fail to deliver at a user level.
Their technology may be great but the business model - as far as their public relations and communications is concerned - is more akin to the impenetrable walls of corporate non-communication circa 1950. And we all know how that turned out.
Some day soon, the big guys are going to have to wake up to the fact that they can no longer hide behind nerdy geekdom when it comes to good communications practice. If they don't, then some day soon, they'll suddenly find their licence to operate withdrawn by the users, customers and stakeholders they fail.
Fabulous - if fixable - code is not enough. You have to talk, respond and act and engage - just like the rest of us.
Posted at 02:58 PM in Action required, Comment, Communication, crisis communications, Culture, digital life, Internet, public relations, real life, relationships, Web/Tech | Permalink | Comments (0) | TrackBack (0)
Reblog (0) | | |