Have the guts to say it and then do it. PMs will get onboard when they get nervous that work won't get to clients.

Since you obviously need to be spoon-fed, here are the numbers for FY2010: Total Income: >$8 BILLION Total Profits: $679 Million Where are these losses you are talking about? And to back it up, just one of many sources you could have found: http://www.eurogamer.net/articles/ms-shifts-10-3m-xbox-360s-in-fy2010

It's been a long-term investment - financially and in the brand. I think you will find (if you actually look at the the profits) that it has paid off big time for Microsoft and its partners. We're talking billions here and for several years now.

I believe that software algorithms are able to be used to "throw out" "dirty" data points so that your resulting 3D pointcloud is clean enough for most practical (non-scientific) uses. Or so I've been told by those performing such operations at certain national institutions. I think they know what they are talking about.

Yeah, I'm sure Google didn't offer Unisys any assistance in securing that contract. Also, GSA already had a deal with MS and backed out of it for a solution that didn't meet their requirements after forcing MS to make changes in order to get the contract in the first place. Not to mention that the Unisys deal ships yet more jobs overseas.

So, Google (via Unisys) was allowed to cheat government rules to get a contract (http://washingtontechnology.com/articles/2010/12/03/gsa-cloud-microsoft.aspx), but they're going to talk about how Microsoft is breaking rules with this DoI deal? Hypocrites!

The real reason that Wave has failed to gather the following of so many other great ideas is that they launched an experimental product that they hoped would go viral and become wildly successful, but they restricted it to the smallest group of people possible: those that don't use Internet Explorer. They probably thought that the "explosion" of popularity of Wave would help them grab browser market share (or at least take it away from IE), but they failed miserably at that as IE usage is actually up now. The claim was that they were focusing their efforts on the quality of the product or some crap like that, so they didn't want to waste time on IE compatibility, but not supporting the browser that had and still has the largest share of the market is just suicide. And let's face it, it's not like it's that hard to get an AJAX app to work in IE - I did it before it was cool and that app still purrs on IE, Firefox & Safari without me really trying to support them. So it seems to me that Google deliberately "broke" Wave on IE. Which means they did the opposite of what they were claiming to do: not wasting time on IE; instead they wasted time on making it not work and wated time on trying to get browser share. Lesson learned? I doubt it. And I'm pretty sure no one here will agree or learn from the lesson, but at least I've tried. The lesson, in case you didn't get it, is: don't launch a product that people might have a hard time seeing the need for to the most restricted segment of a population: those not running IE (you can apply this to other markets, too).

Outlook has this ability via Categories, of which items can be assigned to several.