Combinations and arrangements Everything designed has an element of arbitrariness in its form. Loewy described how groups of his designers used to go about designing a new model automobile. Different groups were given different tasks, such as the front and rear of the car, and the conceptual work began, to be cut off at some predetermined time by deadlines that were imposed at the outset. After a time, there were "piles of rough sketches," and Loewy saw the design proceed as follows: Now the important process of elimination begins. From the roughs, I select the designs that indicate germinal direction. Those that show the greatest promise are studied in detail, and these in turn are used in combination or arrangements with one another. A promising front treatment can be tried in combination with a likely side elevation sketch, etc. From this a new set of designs emerges. These are then sketched in detail. After careful analysis, they boil down to four or five. Raymond Loewy, The Evolution of Useful Things Useless work on useful things drawing
Such an unholy alliance Something was wrong, according to Raymond Loewy, who admitted that, "with few exceptions, the [competitors'] products were good." He was "disappointed and amazed at their poor physical appearance, their clumsiness, and...their design vulgarity." He found "quality and ugliness combined," and wondered about "such an unholy alliance." ...Loewy was also "shocked by the fact that most preeminent engineers, executive geniuses, and financial titans seemed to live in an aesthetic vacuum," and he believed that he could "add something to the field." But, not surprisingly, the people he approached were "rough, antagonistic, often resentful." Raymond Loewy, The Evolution of Useful Things On TasteWe might as well make them beautifulRestrained beauty aesthetics
What went wrong? If something ships from one of the companies I advise, and it is virtually unusable because of poor design (which as we all know occasionally does happen), you can bet I go directly to the designer and ask how this happened? It is absolutely on the designer to ensure this does not happen, so something went wrong. Similarly, if the product ships and performance is terrible you can bet I go directly to the tech lead with the same question. And most frequently of all, if something ships and the analytics show that it’s either not being bought or not being used, or it turns out that it violates some business constraint like compliance or privacy, you can bet I go right to the product manager with that question. Marty Cagan, Product vs. Feature Teams svpg.com Viability, usablity, feasibility