The responses were exactly what I would have expected to see: so many conflicting priorities and groups that nobody can actually solve the problem. This is a standard problem at large companies and one of the reasons they are able to be disrupted by technology and market changes.
There was a lot of jot potato in the thread, but I don't think it signifies anything negative about the people trying to solve the problem. If you don't worry about e "right" way to deal with cross-team issues, your life span at beaurocratic institutions will be very short (spoken from experience :).
However, one huge problem that was identified is that delivering bits isn't seen as part of the "product". Product managers (program managers at MS) need to view getting the bits the same way they would view getting shelf space at a big box retailer. If you don't make sure it is done right, your product will have problems no matter how good it is. If PMs aren't empowered to ensure that process is good, you are in trouble.
And this is why Apple's software and devices are more usable than Microsoft's: one very powerful person at the top, Steve Jobs, dictates what he wants, precisely. No inter-group fighting, or conflicting priorities.
No inter-group fighting, or conflicting priorities.
I'd put good money on the opposite being the case. I get the impression there's a lot of passionate people working at apple, and passion doesn't yield lightly
Absolutely. Have you seen some of the "off the cuff" town hall style meetings he's had? The one before the release of OSX was telling, he repeatedly said that if he were making the decisions, he'd do X, but he's not. It was very eye opening that sometimes it isn't all Steve's fault (of course it isn't.)
Likewise, it's amazing to see that it isn't all Bill's fault. Here he is advocating passionately for a huge change in usability and getting nowhere. Lots of these problems still haven't been solved as of Windows XP (Vista/7 have fixed a lot of update quirks by virtue of being a native app.)
There was a lot of jot potato in the thread, but I don't think it signifies anything negative about the people trying to solve the problem. If you don't worry about e "right" way to deal with cross-team issues, your life span at beaurocratic institutions will be very short (spoken from experience :).
However, one huge problem that was identified is that delivering bits isn't seen as part of the "product". Product managers (program managers at MS) need to view getting the bits the same way they would view getting shelf space at a big box retailer. If you don't make sure it is done right, your product will have problems no matter how good it is. If PMs aren't empowered to ensure that process is good, you are in trouble.