Goodbye, Google An Article by Douglas Bowman stopdesign.com Without a person at (or near) the helm who thoroughly understands the principles and elements of Design, a company eventually runs out of reasons for design decisions. With every new design decision, critics cry foul. Without conviction, doubt creeps in. Instincts fail. “Is this the right move?” When a company is filled with engineers, it turns to engineering to solve problems. Reduce each decision to a simple logic problem. Remove all subjectivity and just look at the data. Data in your favor? Ok, launch it. Data shows negative effects? Back to the drawing board. And that data eventually becomes a crutch for every decision, paralyzing the company and preventing it from making any daring design decisions. 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. I had a recent debate over whether a border should be 3, 4 or 5 pixels wide, and was asked to prove my case. I can’t operate in an environment like that. I’ve grown tired of debating such minuscule design decisions. There are more exciting design problems in this world to tackle. designdecisionsdata
The plan must anticipate all that is needed Ebenezer Howard set spinning powerful and city-destroying ideas: He conceived that the way to deal with the city’s functions was to sort and sift out of the whole certain simple uses, and to arrange each of these in relative self-containment. And he conceived of good planning as a series of static acts; in each case the plan must anticipate all that is needed and be protected, after it is built, against any but the most minor subsequent changes. Jane Jacobs, The Death and Life of Great American Cities Same name in the same basket planningfunction