There's a business strategy for new products that goes by the name of "fail fast, fail cheap". Perhaps that's the reason that Microsoft is pulling the plug on its Kin phones after just two months and one desperate price cut. But they didn't fail fast, and I doubt Kin's failure will be cheap.
There's a business strategy for new products that goes by the name of "fail fast, fail cheap". Perhaps that's the reason that Microsoft is pulling the plug on its Kin phones after just two months and one desperate price cut. But they didn't fail fast, and I doubt Kin's failure will be cheap.Remember that the Kin was a result of Microsoft's 2008 acquisition of Danger, the makers of the once-popular Sidekick phone. Two and a half years later, the Kin made it out Microsoft's door. Perhaps Kin would have worked in February 2008, when Microsoft bought Danger. But the iPhone and Android have showed that phones could be an incredible mobile platform. The Kin seems to have been built as a "better Sidekick" and that isn't something people want in 2010. At the point the Kin was released, Apple was blowing out the 3GS at $99. Verizon's monthly plans priced the Kin like a smartphone, but it's not a smartphone. Why not buy the real thing?
If you start the clock at the aquisition of Danger back in 2008, it took Microsoft more than two years to deliver its failure. In that same period of time, Apple and Android have delivered several generations of useful and functional devices. So although Microsoft pulled the plug quickly on Kin once they realized its failure, they wasted two years; that's not failing fast.
So let's look at the "fail cheap" angle. Microsoft didn't reveal the price it paid for the privately-held Danger, but it was rumored to be $500 million. Then there was the cost of the two-year-long development effort, which at this point seems like a total loss of both money and opportunity. In the post I linked to above, note the final sentence: "Given that there are a couple of devices already on the market that use Danger software (unlike Android's prototypes), Microsoft might actually be able to get some disgruntled Android developers switching to its platform." Oh, the false optimism of 2008.
Microsoft's death notice for Kin puts the best possible face on the fiasco, saying that it was integrating the Kin team into the Windows Phone 7 team. Let's hope they learned enough about what they did wrong to prevent Windows Phone 7 from becoming the next of Kin.
Building A Mobile Business MindsetAmong 688 respondents, 46% have deployed mobile apps, with an additional 24% planning to in the next year. Soon all apps will look like mobile apps – and it's past time for those with no plans to get cracking.
InformationWeek Must Reads Oct. 21, 2014InformationWeek's new Must Reads is a compendium of our best recent coverage of digital strategy. Learn why you should learn to embrace DevOps, how to avoid roadblocks for digital projects, what the five steps to API management are, and more.