A few weeks ago I asked how you'd spend 100 feature dollars on Windows Mobile. 

When we do this exercise, we typically brainstorm a list of features that we'd like to do or that have been requested in the past. We cost the features ourselves, and then ask customers to spend feature dollars on them. Obviously, if a feature is cheap to implement and customers really want it, then that's an easy win for us. If a feature is expensive and customers don't want it, we can shelve the feature with a clear conscience. If a feature is expensive and customers really want it, then we have to try to make space for it.

Since I didn't provide you with a list of features to decide between, the suggestions varied widely. So what I did was sum the requests roughly by which team internally would be doing the work. Here are the results:

IE Mobile: 125 (2%)

Messaging: 156 (2%)

Office Mobile: 300 (5%)

Connection Manager: 350 (5%)

Device Management & Security (my team): 360 (6%)

Phone: 377 (6%)

PIM (calendar, contacts, etc.): 405 (6%)

Windows CE: 420 (6%)

Sync (primarily wireless sync): 640 (10%)

Shell: 1425 (22%)

Other (OEM requests, or things too generic to categorize): 1473 (23%)

I put most of the one-handed navigation requests into Shell, although it's really something that has to be implemented across all applications running on the device. Connection Manager doesn't have its own team, but I made it a first class entity because it got so much attention.

I also noticed at least 480 feature dollars that requested things I know we have already implemented for future releases. There's probably more - that's just what I identified off the top of my head.

Thanks for all the detailed suggestions! I'll get it to product planning and the appropriate feature teams.

Scott