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
A concept of style It is a concept based not on the classification of various physical features of architecture and urban design but on the problem-solving process itself. We have seen that the final outcome of a design process is strongly determined by at least three aspects of that process: the subject matter of the organizing principles which are adopted, the manner in which these principles are interpreted and reinterpreted in the context of the problem at hand, and the sequent of applying such organizing principles. Consistency in style among the output of designers can thus be understood as a habitual way of doing things, of solving problems. Peter G. Rowe, Design Thinking It was all change until the very last second style