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
Skeleton, Organs, Circulation, Sinew, Skin An Article by Dorian Taylor I’m concerned with how I witness the work of user experience practitioners getting treated: like it’s just a set of motions toward a product’s all-important implementation, and one that we try to compress, due to its ostensible superfluity. Once the implementation is finished, the UX work appears to usually get discarded. Tracing the answer backThe UX coral reef ux
Tracing the answer back I submit that the materials that form the precursors to a product’s implementation have considerable value on their own. My vision is that I will be able to ask a question as mundane as one about the wording of a single button, and trace the answer all the way back to the overarching business strategy to see that it makes sense. decisions
The UX coral reef It isn’t a site, or a service, or even an identifiable product at all, but rather a system for creating a skin around and connective tissue between things like: Demographic studies Contextual inquiries Stakeholder and user interviews Surveys The business ecosystem Personas Scenarios Sketches, storyboards, wireframes Mockups, models and prototypes Email and IM conversations Meeting notes Content inventories and audits Concept schemes, taxonomies, thesauri A UI style guide A branding and visual identity guide A voice and tone guide A code style guide ...etc The individual elements of such a corpus represent the work of half a dozen specialist sub-disciplines, and are useful for realizing a product’s implementation. But if you hook them all up together, they merge to become a strategic artifact that transcends products and operates as a critical control surface for the business. This is because what such an artifact represents is a coral reef of deeply-considered and hard-fought decisions, and a story of the process that yielded them. connection