This is the classic designer first vs. sales/engineer first debate to designing software.
Typically in PC land, the sales team says, we need something new to sell. The engineers say sure we can do anything, but we don't know what people want, so we're just going to make it "customizable" and let users figure it out. We geek out on making it so flexible. More to do in the product often leaves less time to perfect the code which then ships with more bugs, we just patch in a service pack. It also leads to usability issues like stuffing more and more "features" into menus, eventually overstuffing the product with so much, users can't find anything to get the job done.
Apple takes the opposite approach, they battle it out in boardrooms for whether or not a feature deserves to be in the product in the first place. The designer first approach leads to a lower quantity of features, which provides them more time to get those fewer features perfected and polished to a shine.
FWIW, more and more people are giving the designer first approach a try in Silicon Valley. Top designers are being snatched up left and right.