Live data from Hacker News

Goodbye Google: "Visual Design Lead" leaves Google

stopdesign.com

91–100 of 103 posts

Re: Goodbye Google: "Visual Design Lead" leaves Google

#91
post #84

Earlier quoted context omitted.

> I've found sound to be critical in software usability Very little is worse than web pages that use sound. It's no accident that most sites don't use sound, your tastes are just way outside the mainstream on this. > Interjecting them in the design process too soon and giving their opinion overriding power is a mistake. The success of Google clearly shows it's not a mistake, numbers don't lie, but designers are full…

Desktop apps are used by more people on a more regular basis than any web app to date. Web apps are getting there, but there not there yet. Sound, when used appropriately, is a very critical component to user experience and more importantly, usability — hence why most operating systems use sound feedback. Apple's new Nano uses sound to extend its usability tremendously, and other examples are endless. (By no means do…

[deleted]

Re: Goodbye Google: "Visual Design Lead" leaves Google

#92
post #87

Earlier quoted context omitted.

> Requiring user testing for shades of blue and thicknesses of border is the height of silliness. 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…

I think that's right, but a little overgenerous to engineers. We have our hangups, too. 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."

You can't measure emacs vs vim like you can the effect of color or layout on conversion of an app. When measuring is trivial to do and results are easily seen to directly impact revenue, there's just no excuse to not do it.

Re: Goodbye Google: "Visual Design Lead" leaves Google

#93
post #87

Earlier quoted context omitted.

> Requiring user testing for shades of blue and thicknesses of border is the height of silliness. 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…

I think that's right, but a little overgenerous to engineers. We have our hangups, too. 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."

[deleted]

Re: Goodbye Google: "Visual Design Lead" leaves Google

#94
post #76

Earlier quoted context omitted.

You just spent three days of a teams time over what the designer already knew.

The point of the blue-bar incident was that the designer was not correct, and a different shade of blue (which most people inside the Googleplex thought was inferior) generated measurably more revenue - more than the designer's salary, and certainly more than the time spent experimenting with different shades of blue. The best thing about a data-driven approach is that it gives room to be wrong. And we're proven wron…

I wonder if there is any research/reasoning in why one shade of blue would generate more revenue than another?

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

Re: Goodbye Google: "Visual Design Lead" leaves Google

#95
post #84

Earlier quoted context omitted.

Desktop apps are used by more people on a more regular basis than any web app to date. Web apps are getting there, but there not there yet. Sound, when used appropriately, is a very critical component to user experience and more importantly, usability — hence why most operating systems use sound feedback. Apple's new Nano uses sound to extend its usability tremendously, and other examples are endless. (By no means do…

You're moving the goal post. No one's talking about desktop apps, you said web apps. Web apps are a different space and sound is just not appropriate there, and it likely won't ever be.

There are many cases that justify when to use and when not use sound on the web...

I would say it's the goal of most web-app builders to mimic desktop apps b/c the result is a familiar environment for the end user. Software/UI design is an established practice, with many studied and proven methodologies for handling complex user interaction that has been unfamiliar to the web in former years.

That said, I believe it's inevitable that web-apps will mirror their desktop counter-parts in time (many are doing so already)... the exception being, highly-specialized web apps.

Re: Goodbye Google: "Visual Design Lead" leaves Google

#96

>"Yes, it’s true that a team at Google couldn’t decide between two blues, so they’re testing 41 shades between each blue to see which one performs better." compare that quote with the one from here: http://gawker.com/5162532/marissa-mayer-googles-biggest-fail... >"In dictating the appearance of Google's Web pages, Mayer freely admits she makes subjective decisions. In more than a decade on the job, she has not yet co…

Eek a Valleywag link! It shouldn't really be blocked if it has relevant or original articles...

Re: Goodbye Google: "Visual Design Lead" leaves Google

#97
10 days ago I suggested Google in a Grid re-design. I suggested one optional button to switch from normal to grid mode. I realized that the people are very very protective about Google. 70% without any particular reason hated the idea of any kind of Google redesign. Even do my arguments were stable "The Grid can hold much more information, more photos and videos and can contribute for better visible experience" almost nobody bother to discus with real arguments. My post (http://www.vcarrer.com/2009/03/google-redesign-google-in-gri...)

I'm first developer then designer and I do believe that one product should constantly be developed in bought direction. In the case of Google they have excellent query search result but can do much much better visual experience. I'm not talking about rebuilding everything but sometimes one pixel can make great difference.

Re: Goodbye Google: "Visual Design Lead" leaves Google

#98
If Google applied this to PageRank, they wouldn't have started.

In the beginning, Google was Ark A. Then it was Ark C. Now it's Ark B (tRatEotU - DNA)

But I have to admit, being able to precisely exactly quantify the beauty and usability of a design is irresistibly compelling to me. Especially when billions of dollars hinge on it (and you can measure them).

Re: Goodbye Google: "Visual Design Lead" leaves Google

#99
post #94

Earlier quoted context omitted.

The point of the blue-bar incident was that the designer was not correct, and a different shade of blue (which most people inside the Googleplex thought was inferior) generated measurably more revenue - more than the designer's salary, and certainly more than the time spent experimenting with different shades of blue. The best thing about a data-driven approach is that it gives room to be wrong. And we're proven wron…

I wonder if there is any research/reasoning in why one shade of blue would generate more revenue than another? 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 de…

Well, that's the point of multi-level A/B testing. You try all of the combinations to isolate the impact of each varying feature, but you are always testing 'wholistically'. They don't just throw a green bar up there on its own and see who clicks on it.

Re: Goodbye Google: "Visual Design Lead" leaves Google

#100
post #47

Earlier quoted context omitted.

Nowhere does his post imply that the reason he's leaving is because his design aesthetic clashes with Google's desire for "clean, spartan, and utilitarian." It's perfectly possible to meet those goals and not be ugly, like, e.g., iGoogle and Gmail are. I consider most of Apple's designs to be "clean, spartan, and utilitarian". Requiring user testing for shades of blue and thicknesses of border is the height of sillin…

> Requiring user testing for shades of blue and thicknesses of border is the height of silliness. 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…

From the way I understood it, he was suggesting that testing for shades of blue and border thickness is nitpicking. An equivalent nitpick more familiar to us would be testing whether using tabs or spaces for code indenting improves coding efficiency.
Post reply on HN