Lessons from Google Wave failure
Summary: If you're going it alone you better have a business model. Or have something truly innovative. Even if you're ginormous.
If you're going it alone you better have a business model. Or have something truly innovative. Even if you're ginormous.
(This Google tribute to Leonardo DaVinci ran on its own home page early in the 2000s.)
There are a lot of lessons there for Google, which announced the failure of Google Wave on its blog yesterday. Despite the efforts of 6,000 developers and 100,000 users, it never came out of beta.
As Ina Fried and Josh Lowensohn recounted at CNET, Google has failed before. Dodgeball, Jaiku, Notebook, Lively, Hello and Answers are just some of the projects that it has shuttered after announcing them to the media.
But let's parse that first paragraph again:
- Going It Alone -- An individual or small group going it alone is courageous. A behemoth going it alone is suspicious. Without allies, without external support, a Google project run by Google alone is in trouble.
- Business Model -- Google has a tendency of going with cool stuff first and worrying about how the money will come back later. That's how it bought Blogger and YouTube. That leads to trouble.
- Truly Innovative -- Wave sounded innovative, but it really just combined a lot of services that already existed. Was it a service or a user interface -- I was never certain.
- Ginormous -- Google is huge, humongous, enormous, the 800-pound gorilla. It bought fiber when it was dirt cheap, it innovated on server farms, it focused like a laser on electricity costs, it became the low-cost producer of all Internet services. But that also put a target on its back.
Contrast the failures with successes like Google Code and Google Android. Both have lots of friends. Both have real hardware business models. In both cases Google followed the wave, rather than trying to create it. That's what big companies do.
You can argue that in all this Google is just a tech venture capitalist, that the success of Android excuses the failure of Wave and the others. You can also argue that Google has learned to make lemonade from its lemons, like Blogger and YouTube, so why should it change?
I say it's because Google has a target on its back. When a kitten falls it's cute. When an elephant falls a lot of things get trampled, and their friends don't like it.
I'm not calling for wholesale changes here. But before announcing any project to the world the company needs to know it's putting its global reputation on the line. Such announcements are news, a big Biden deal.
Until you know what a project is about, or until you really need to tell people, keep it to yourself. It's less embarrassing.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
Style points for trying, though
Kudos for that!
Now Google should sit down with partners and draw design a real standard for something which could incrementally grow into something like Wave.
RE: Lessons from Google Wave failure
Isn't that wave federation?
http://www.waveprotocol.org/
RE: Lessons from Google Wave failure
For this guy to say they should have "kept it to themselves" until they were sure it would work is just ludicrous and obvious he knows nothing about running a software product. How would they know its a failure unless they had users? 100,000 users is pretty good by most standards.
RE: Lessons from Google Wave failure
It's interesting to read this article "The Wrong Stuff : Error Message: Google Research Director Peter Norvig on Being Wrong" http://goo.gl/rbjE
(BTW, an argument that Google did not innovate with Android is laughable)
What have you done?
RE: What have you done?
Yea, I agree with you. Google didn't become as big as they are by following, they're innovations are a huge part of their success. Some of their innovations are a hit, some flop...just a matter of time before the next hit.
RE: Lessons from Google Wave failure
Absolutely agree with you. I read my daily bulletin of this person and almost everytime disagreed.
This time I want to express myself.
What a wrong idea: let the others innovate, let them create, and if it works I'll do the same.
What a poor way of thinking. Jumping on the bus where the others are going on too (only it it's already going on!).
If you want th be a REALLY good <person/creative/company/anything> you MUST to try knowing that it can works and be accepted or not and it will be shut down and think on another thing, or at least study it and give it "another turn of nut" as Buzz, do you hear about it?
C'mon! Flat minded! When you're small a bad hit could hurt or kill your business but when you grow up you can afford a slamp. Ok, Google is big enough to resist the slapm of not-accepted ideas and even reports like this one!
Keep going on Google.
RE: Lessons from Google Wave failure
Blog posts are the start of a discussion. They are never the final word. I know mine aren't anyway.
RE: Lessons from Google Wave failure
http://drop.io/
Please crawl out of your "Google is the shizz" dungeon.
Google is being a hack with some totally redundant rip offs. Chrome OS will fall too.
RE: Lessons from Google Wave failure
I write
RE: Lessons from Google Wave failure
Sorry if I came out rude. I'm not saying that we shouldn't critic some ones work. But at least we should take time to do a bit of research before reporting. Sorry to say that the reporting done by the so called tech journalists is nothing but shame.
RE: Lessons from Google Wave failure
Sensing that wave might not be going places, we've put it on facebook now as well, but still with Google Wave's realtime features. It's at apps.facebook.com/travel-withme.
RE: Lessons from Google Wave failure
What about Google's Project 10^100 ? I hear a lot of silence...
RE: Lessons from Google Wave failure
Google's Project Google? lol.
RE: Lessons from Google Wave failure
What a load of CRAP! This guy is a moron.
RE: Lessons from Google Wave failure
RE: Lessons from Google Wave failure
RE: Lessons from Google Wave failure
Strangely Flawed