Embracing Asymmetrical Design An Article by Ben Nadel www.bennadel.com Humans love symmetry. We find symmetry to be very attractive. Our brains may even be hard-wired through evolution to process symmetrical data more efficiently. So, it's no surprise that, as designers, we try to build symmetry into our product interfaces and layouts. It makes them feel very pleasant to look at. Unfortunately, data is not symmetrical…Once you release a product into "the real world", and users start to enter "real world data" into it, you immediately see that asymmetrical data, shoe-horned into a symmetrical design, can start to look terrible. To fix this, we need to lean into an asymmetric reality. We need to embrace the fact that data is asymmetric and we need to design user interfaces that can expand and contract to work with the asymmetry, not against it. To borrow from Bruce Lee, we need to build user interfaces that act more like water: “You must be shapeless, formless, like water. When you pour water in a cup, it becomes the cup. When you pour water in a bottle, it becomes the bottle. When you pour water in a teapot, it becomes the teapot. Water can drip and it can crash. Become like water my friend.” — Bruce Lee The pernicious issue with pangramsChanging Our Development Mindset datainterfaces
Conversational drawing A skilled draughtsman guides design conversations by selecting and emphasizing details in a way that computer programmes cannot. Ron Slade, author of Sketching for Engineers and Architects and a structural director at WSP in London, calls it “conversational drawing”. He notes how botany field guides are always based on detailed drawings rather than photographs — as much for what they leave out as for what they show. “Extraneous material that might exist in a photograph is eliminated. It may be important to pick out and illustrate particular areas and leave other parts in sketchy or broad outline.” Nick Jones, Back to the Drawing Board Why Sketch?