Attention: Microsoft
- 6 August 2010
About a year ago, Google launched Wave, an application for on-line real-time collaboration. Kind of IM on steroids. While it never reached a Facebook-level frenzy, it was at least partly supported by some big names: SAP, SalesForce, Novell.
This week, Google announced it was ending the project.
Mashable writer Christina Warren lists lessons that Google can learn from closing down its Wave application:
Lesson 1: Keep Expectations in Check
Lesson 2: Make Your Product Clear
Lesson 3: Launch When Ready
Lesson 4: Have Real Value
Learn From the Past
Warren implies that Google rushed to market and did not explain the product.
And where have we seen that before?!
Software manufacturers must balance the tension between the need to roll out new products (and new versions of existing products) to keep the money rolling in; some customers wanting the latest thing; and the other customers needs for stable products that deliver value.
Too often, in my view, Microsoft rushes to market with remarks like “this is the first release; we know it’s not completely finished; wait for v2″. But by the time the next version rolls around the keen person who started the idea has gone off to a new job, and a feature—or a whole product—becomes abandonware.
Footnotes:
Any number of other people are also writing ‘lessons learned’ pieces.
How many puns can headline writers write? ‘Wave crashing’, ‘Wave goodbye’, ‘it’s a wipeout’.



Sometimes, online shopping is the best thing since—umm—sliced bread. And sometimes, it’s just too hard.
