Ed's profileTechBytes and BitsPhotosBlogListsMore Tools Help

TechBytes and Bits

Sailing along the Information Superhighway

Ed Oswald

Occupation
Location
August 09

Niall Kennedy's Departure: Sour Grapes or Real Problems?

After only four short months with Microsoft, RSS guru Niall Kennedy is calling it quits. Many would have likely just poo-poo this announcement away, if it wasn't for this gem in his blog post:
"Windows Live is under some heavy change, reorganization, pullback, and general paralysis and unfortunately my ability to perform, hire, and execute was completely frozen as well."
Oh dear.  Could it be not even a year after Microsoft launched it's initiative to focus on a web-based service architecture, the company is already stumbling?
 
The guys at LiveSide.net interviewed Kennedy, where we got more perspective into his decision. He said he would have stayed as excited about his work at Microsoft if they had only given him the resources, but alas they didn't. He criticizes Microsoft's Redmond-centric mentality, which I couldn't agree more with.
"Microsoft has a 'come to Redmond' mentality, which warps the world placing Redmond at the center of a software universe. Placing individual product groups in various locations will help solve overcrowding and spur innovation. We've seen it happen with moving Xbox and Bungie off-site, I think a change of workplace setup could invigorate the groups."
It's true. A focus is put on coming to Redmond when working with Microsoft. I agree with the premise of decentralizing the company -- while some may argue that it would slow things down, I believe it would do the opposite. By having all your eggs in one basket, it is too easy for the big wigs to tinker too much. It wouldn't be as easy to poach developers off one team if the others a significant distance away. This would allow things to be completed, and give the groups a sense of autonomy and control over their own destiny.
 
For Niall to come straight out publicly and make such statements is a sign of some issues within Windows Live. Not only to the fact that they are obviously not keeping their employees happy, but also to the fact that the company is still making the same mistakes its been making for over a decade -- starting out gung ho on an idea, but not seeing it to completion: either by spreading themselves out too thin, or not properly allocating resources to a project, or having no clear direction.
 
This mentality is what killed promising projects such as SPOT (yes, it's still alive but barely) and others. I've often opined that I believe Windows Live has way too many simultaneous projects going on at the same time (they say 20+), and the company is diluting the brand just like they did to the .NET initative. I am beginning to think that Microsoft is trying to do too much, and when something like this happens, and one of your employees is pushed to complain publicly about it, it's time to take a second look at how you're doing things.
 
Part of the massive reorganization of Microsoft was to make the company more focused, but if what Niall is telling us is true, it's not working.
 
With companies like Google hot on your heels, MS needs to consider the ramifications. How much do you want to bet that Google is extremely interested in Kennedy, and may talk to him about his ideas (if they haven't already)?
August 08

WL Spaces Downtime and BetaNews Coverage

(Note: Reposted from my old blog)
 
I have had a few people voice their displeasure with BetaNews' story regarding Microsoft's bug-ridden migration to Windows Live Spaces. Someone said we like "negative Microsoft articles." I couldn't disagree with this statement more. It's completely untrue.
 
The fact is, MS' move to Windows Live Spaces was pretty darn bad. In some cases, people were either locked out, or had some serious problems accessing the service for nearly a day. This is past unacceptable. While some pro-Microsoft folks said this it to be expected, in reality it is not. There are many other services who have millions of users that perform near-flawless upgrades on a regular basis. It seems that Microsoft has not mastered this yet.
 
Maybe the problem here is the Spaces crew is biting off more than it can chew. I find it hard to believe that some of the problems the service had were not detected in their test environments as the team says. How can such errors go undetected, and why for what i can remember for the second time the service has been seriously degraded for an extended period of time (maybe there is others, but I can remember one other serious outage other than this one.
 
It's issues like this which turn off people to new and exciting services. I'm by no means poo-pooing the potential of Windows Live.. but when you have some 50 million plus users with possibly a large portion of them getting their first exposure to Windows Live, having serious issues like this is a bad first impression.
 
This might also be a time for Microsoft to reconsider their rollout/migration strategy. To prevent problems like this in the future, why not migrate only a portion of users at random to the new format, and watch for issues? That way, an outage does not affect everyone, and you have a lot less pissed off people.
 
As for our negative articles, we've written unflattering stuff about just about every company, including AOL (which some people say we are unfairly biased positively for).
 
Ah yes. Journalism is so much fun. Damned if you do, damned if you don't.
 
There are no photo albums.
No list items have been added yet.