Requiring user testing for shades of blue and thicknesses of border is the height of silliness. I'm reminded of those room makeover shows they have on TV. At the beginning, the designer tells the couple one of the colors they've chosen. The couple is aghast. "What, I can't stand magenta. No way!" Sometimes, the wife looks like she's about to cry. At the end, magenta is used and the design is breathtaking.
There is no way user testing has gotten efficient enough to beat a designer at that level of detail. Moreover, users often don't know they want something until a designer shows them they do. You can never get to those designs by testing blues and borders.
No it isn't, if a designers ideas cannot withstand a little objective scientific testing, they aren't worth using.
> Moreover, users often don't know they want something until a designer shows them they do. You can never get to those designs by testing blues and borders.
Which is the whole point of objective testing, do the design, throw it in front of real users and see how it performs next to the original design.
I think what's really going on is that more often than not, designers want what they like rather than what works best. Engineers want what works best, and Google has an engineering culture. Form does and rightfully should take a back seat to function.
Say, which do you think is better, emacs or vim?
Even in a data-driven environment oftentimes the argument gets pushed back from "what to do" to "what to measure."
Emacs vs. Vim, Ruby vs. Python, or whatever.
And those things are quantifiable to some extent. Take a random sample of engineers, give them identical tasks to complete, and vary the editor.
The best thing about a data-driven approach is that it gives room to be wrong. And we're proven wrong all the time: basically every meeting, there's some measured data where we go "that can't be right" - and then we either discuss ways in which we might've misinterpreted it or say "Okay, assuming this is right, then what do we do?" It sounds idiotic, but really we're (humanity in general) the idiots.
Malcolm Gladwell had an interesting podcast about people's ability/inability to express what they really mean and feel. He uses the Aeron chair as an example of a product that was despised/considered ugly but eventually embraced for it breakthrough functionality/aesthetic.
I can see how data-backed design decisions can produced locally optimized results, the "ideal" shade of blue, logo size, typography, etc.. But I wonder if on the whole, all those optimizations work together optimally, as a wholistic experience?
[edit] Gladwell's Podcast: http://itc.conversationsnetwork.org/shows/detail230.html
So, it looks like the designer didn't know.
I'd contend that's because most designers don't optimize for performance, they optimize for aesthetic. When those two are in conflict which should win?
It sounds like Bowman thinks the latter, while Google thinks the former. As a stockholder I'm thankful that's the company's attitude.
That doesn't mean he's a bad designer - I'm sure he's not. But Google occupies a particular place in the market ecosystem: many of its users want a UI that's clean, spartan, and utilitarian. There're undoubtably market niches for stuff that's more visually stunning (wasn't one of PG's ideas for startups "A form of search that depends upon design"), but people interested in that would be far more economically productive seeking out new markets of people that are underserved by Google's spartan design rather than trying to force something visually impressive upon Google's existing users.