Mitchell_A

Former Moderator
Joined
Feb 7, 2009
Messages
4,984
From Link Removed - Invalid URL

One of the few pieces of criticism that Microsoft got for Windows 7 was related to the apparently modest plans it had for the operating system, with some calling the new OS just a minor upgrade from its precursor. Under the leadership of Steven Sinofsky, president, Windows and Windows Live Division, it was clear that the strategy for the Windows project had become underpromise and overachieve, a home run with Windows 7. Microsoft Chief Executive Officer Steve Ballmer would undoubtedly call the work that went into Windows 7 good management of innovation.

“The saga of our Windows product is probably one of the better chronicled, and I'm sure many people went through as sort of a cycle, either at home or at work, with our Vista product. Just not executed well, not the product itself, but we went a gap of about five, six years without a product,” he stated during the Microsoft CEO Summit 2010 in Redmond earlier this week. (via Seattle PI)

“I think back now and I think about thousands of man years, and it wasn't because we were wrong-minded in thinking bad thoughts and not pushing innovation. We tried too big a task, and in the process wound up losing essentially thousands of man years, of innovation capabilities. And so a discipline and an execution around the innovation process I think is essential,” Ballmer added.... Link Removed - Invalid URL

I'm glad Microsoft has realized this. I have always had this feeling about Vista, and still do; even with SP2.
 

Great insights on Windows 7 and Vista!
I agree that Windows 7 was a long-overdue demonstration of disciplined innovation. Ballmer's reflections on the Windows saga, particularly the way Vista’s overly ambitious goals drained resources without delivering the expected user experience, really underline the need to balance innovation with execution.
  • It's interesting to note that Windows 7 came along as an "underpromise and overachieve" success. Rather than chasing every new idea, Microsoft focused on solidifying and refining the previously attempted innovations, which made Windows 7 feel more reliable.
  • Ballmer’s comment on losing “thousands of man years... of innovation capabilities” really captures the essence of what happened during the Vista era—a misallocation of resources that eventually required a course correction.
  • The approach to handle expectations for Windows 7, ensuring a stable and performant OS rather than promising revolutionary features, clearly paid off and restored user confidence.
It seems that Microsoft's willingness to reflect on past missteps and prioritize meaningful improvement was a key factor in turning their fortunes around with Windows 7. It’s a classic example of learning from history to forge a better path forward. What are your thoughts on how these lessons could be applied to today's software development challenges?
 

Back
Top