Microsoft loses chief software architect Ray Ozzie
Bill Gates replacement finished
Ensure Ease of Recovery with Asigra’s Agentless Software
Bill Gates' replacement at Microsoft, Ray Ozzie, is leaving the company after just five years.
Ozzie is stepping down as chief software architect - the jobs Gates last occupied - and will only remain with Microsoft to transition his teams and people to other groups. Ozzie joined Microsoft in 2005 and became chief software architect a year later when Gates' exit from Microsoft was announced.
The chief software architect role will not be filled after Ozzie's exit, chief executive Steve Ballmer has said (warning: PDF) in an email.
No date was given for when Ozzie will leave Microsoft, but before he leaves, Ozzie will also be "focusing his efforts in the broader area of entertainment." Ozzie has no plans beyond this, Ballmer said.
Ballmer didn't say exactly what that meant or whether that involves working on Xbox, Kinect - previously codenamed Project Natal - or Windows Phone.
Microsoft's CEO credited Ozzie with helping to catalyze Microsoft's move to the cloud.
During his time, computing's famously quiet thought leader wrote a memo that's credited with being instrumental in Microsoft's transition toward cloud and software-as-a-service: the Internet Services Disruption memo.
Ballmer enthused that during the last five years, Microsoft has accomplished much, having moved SharePoint and Exchange to the cloud and launched its Windows Azure platform for running applications in the cloud.
Ozzie was a hot hire for Microsoft in 2005, coming on board with the acquisition of his online collaboration start-up Groove Networks. Ozzie became Microsoft's chief technical officer.
Chiefly credited with creating Lotus Notes, a piece of collaborationware Microsoft has spent years trying to eradicate, Ozzie was looked up to by Gates - a rarity for a somebody famously intolerant of others. Ozzie was named Gates' replacement as chief software architect when Microsoft announced a two-year transition for Gates out of Microsoft.
During his time with Microsoft, Ozzie created the team that built Windows Azure, now in the Microsoft's Server and Tools division, and he championed FUSE Labs and its work bringing Office collaboration capabilities online via Facebook via Docs.com.
But Microsoft's chief software architect has never really shone. He's rarely spoken in public to articulate or evangelize a vision to inspire the Windows or .NET faithful.
Ozzie's exit will be seen in mixed tones. On the one hand, it'll be seen as one more mark against a company struggling to regain the position at the vanguard of innovation. Also, further proof Microsoft is unable to attract and retain on a long-term basis talent from outside.
Given Ozzie's low profile, and his status as architect of the less-than-exciting Notes, his exit will likely barely register among many.
Either way, Ozzie's move is as sudden as it is curious: Ballmer's email painted Ozzie's exit as the end of major combat operations in terms of Microsoft having delivered on Ozzie's cloud thinking.
But Ozzie's move begs the questions: who's doing the big technology thinking now, and who will conceive and captain the "three-screens and a cloud" idea Ozzie helped popularize and was so happy to quote? The three screens in this scenario referred to the PC, phone, and TV.
Now we know why Ozzie was recently clearing out his office. ®
Requirements Checklist for Choosing a Cloud Backup and Recovery Service Provider
COMMENTS
"a company struggling to regain the position at the vanguard of innovation"...
Seriously? When were MS ever at the "vanguard of innovation"? Dates and products please.
So, last Thursday, "I'm back!". 5 days later, "I'm outa here!"
I believe the ructions from this one will prove much more profound than the author appears to suggest. Ozzie really was supposed to be 'the one', 'the saviour', a fitting replacement for Gates, for the long haul. Last Thursday, after an absence of 12 months on his blog, we get this post saying he's back - and now he's just as gone (and more), in less than a week! What's that all about? And at such short notice? Why announce your return last Thursday, if you had sensibly-planned exist strategy for sometime, the week after?
Balmer may now say that Ozzie doesn't need replacing, because he has "strong technical leaders in each business group", but this is exactly the reason why Ozzie was supposedly there: each business group has characteristically spent the last two decades, at war with each other an undermining one another's efforts because of these raging barons in their rival factions. Ozzie's role was to control those "strong technical leaders" (and read minimsft, for the rank-and-file opinion on how "strong", "technical" or "leader-like" many of those unit managers are often seen to be, within Redmond).
I'm sorry, but even if this is a case of "ship the damn phone and get the Hell out", the announcement appears to have come so precipitately, that I cannot help but think that this signals that the famously "shouty" Redmond atmosphere, may have moved up a notch, towards outright civil war in the upper ranks.

IT infrastructure monitoring strategies
Requirements Checklist for Choosing a Cloud Backup and Recovery Service Provider
Data control in the cloud
Cloud based data management
Enabling efficient data center monitoring