4 ms·
Google believes in data only. Designers are not used to justifying their ideas with data. While no one comes out and says it, the implication is that most of w
by neilk 17y ago
Google believes in data only. Designers are not used to justifying their ideas with data.
While no one comes out and says it, the implication is that most of what constitutes the design profession is mere flimflammery. You don't need a designer to tell you what shade of blue to pick when you can just A/B test a few hundred shades.
That's why a lot of designers quit.
- petercooper 17y agoCan you imagine if they used those sorts of techniques to refine TV schedules? You'd end up with non stop reality and talent shows. Oh, hang on..
- dirtyaura 17y agoBullshit. For example, do you honestly think that Android UI was done in a data-driven way from the scratch without designers? Google uses data to tweak experience of their existing products like Search UI. That's it. Designing interfaces for new products or features is done by designers (or in some case, like many Google Labs products, by developers).
- neilk 17y agoYou're right, I should have qualified that. That said, there are a lot of people working as designers in Google, but in my experience they are essentially user interaction designers. The more woolly aspects of design -- like picking a different font just because of how it "feels" -- Google's pretty hostile to that. There's a default concept of "Googliness" which everyone understands to be a kind of high-energy, primary-color blandness with near-magical UI. There aren't a lot of projects that deviate from that, no matter what the designer thinks. If you compare it to the kind of design variety you see at Yahoo or even Microsoft you'll see what I mean. At Yahoo a lot of projects are almost led by design, for good (Flickr) or ill (almost everything else). And there are design principles of Flickr which Google could never accept, like "serendipity". The idea that a user interface could be deliberately not laser-efficient, in the name of promoting exploration and community engagement, would totally baffle Google managers and they wouldn't tolerate that kind of designer-talk.
- jlees 17y agoHeaven forfend one should use an attractive font on a Google product. Seeing the incredible engineering innovations going on at Google, and the incredible UI innovations going on elsewhere, makes me a little sad - never the twain shall meet, and instead they're redeemed to making shallow copies of each other and never quite hitting the spot. Over-designed and under-engineered, or vice versa. Adding design-led products or hiring more designers, however, would kind of change what Google is about IMO. Can engineers be taught design? ;)
- krakensden 17y agoHave you ever considered that maybe designers have created a culture that is not quite congruent with reality, and that their perception of a good interface is not, in fact, always a good interface? Engineers like the Google style, but so do lots of my acquaintances who are non-engineers, from scientists to writers to school teachers. Designers seem to be the only demographic with a problem.
- elblanco 17y agoDesigner driven applications and websites seem to too often fall into the "pretty but unusable" bucket, I agree.
- Devilboy 17y agoYes but the designers have to prove (using formal usability testing) that their 4 pixel bezel is superior to a 3 or a 5 pixel bezel for example.
- dsspence 17y agoI think this is the link you are referring to: http://stopdesign.com/archive/2009/03/20/goodbye-google.html http://stopdesign.com/archive/2009/03/20/goodbye-google.html
- _delirium 17y agoI agree sorta, but only for the more tweaky visual design aspects, rather than interaction design. If anything, I see Google as actually less data-driven in its design than many areas. Industrial psychology and HCI are traditionally very big on data-driven design for interaction design, with a big focus on Methodologies, quantitative measurement of task performance improvement, and various other statistical evaluation metrics. But the main downside of that is that you can't really answer open-ended design questions: you can A/B test between two specific proposed interfaces, and determine A causes N% of users X quantity less hassle than B does (or whatever your metric is), but if you want to invent an entire new interface, you're basically doing a random walk in design space, which will take a really long time to get anywhere. I mean, imagine how many A/B questions you'd have to ask to invent the Gmail interface, using, say, the Hotmail interface as your starting point, and having to justify every change you make from that starting point using data. I suppose it depends on your norm, though--- Google is very data-driven by the web-design standard, but sort of loosey-goosey, anything-goes compared to the much more statistics-and-methodology-heavy design practices that go on in traditional engineering and HCI.