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
We are surrounded by ghosts An Article by David R. MacIver notebook.drmaciver.com I'd like to call the more general phenomenon that this is a specific instance of "ghost knowledge": It is knowledge that is present somewhere in the epistemic community, and is perhaps readily accessible to some central member of that community, but it is not really written down anywhere and it's not clear how to access it. Roughly what makes something ghost knowledge is two things: It is readily discoverable if you have trusted access to expert members of the community. It is almost completely inaccessible if you are not. In this sense, most knowledge is ghost, particularly if you take an expansive view of what counts as an epistemic community. knowledge