Turning Microsoft's business model on its head
This is a fascinating article from the New York Times. It's all about how Google is challenging Microsoft by turning its business model on its head - the switch from licensing software that's installed on desktop computers, to free web-based software.
Microsoft changed the software business for ever by being the upstart that challenged the old mainframe model and replaced it with the desktop. IBM didn't see that one coming at the time, and now MS is the entrenched giant with a new upstart changing the game yet again. Only this time the 'upstart' is actually a huge, well-funded company. I just find it UNBELIEVABLE that they can't seem to see what's coming.
This little case study is a perfect example of how different the Google approach to product development is. The Google engineer at the centre of this story previously worked for 15 years at Microsoft. Can you imagine MS making a product happen in this way?
Early this month, Google released new cellphone software, with the code-name Grand Prix. A project that took just six weeks to complete, Grand Prix allows for fast and easy access to Google services like search, Gmail and calendars through a stripped-down mobile phone browser. (For now, it is tailored for iPhone browsers, but the plan is to make it work on other mobile browsers as well.)
Grand Prix was born when a Google engineer, tinkering on his own one weekend, came up with prototype code and e-mailed it to Vic Gundotra, a Google executive who oversees mobile products. Mr. Gundotra then showed the prototype to Mr. Schmidt, who in turn mentioned it to Mr. Brin. In about an hour, Mr. Brin came to look at the prototype.
“Sergey was really supportive,” recalls Mr. Gundotra, saying that Mr. Brin was most intrigued by the “engineering tricks” employed. After that, Mr. Gundotra posted a message on Google’s internal network, asking employees who owned iPhones to test the prototype. Such peer review is common at Google, which has an engineering culture in which a favorite mantra is “nothing speaks louder than code.”
As co-workers dug in, testing Grand Prix’s performance speed, memory use and other features, “the feedback started pouring in,” Mr. Gundotra recalls. The comments amounted to a thumbs-up, and after a few weeks of fine-tuning and fixing bugs, Grand Prix was released. In the brief development, there were no formal product reviews or formal approval processes.
Recent Comments