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
A grossly obese set of requirements Who advocates in the requirements process for the product itself—its conceptual integrity, its efficiency, its economy, it’s robustness? Often, no one. As often, an architect or engineer who can offer only opinion based on taste and instinct, unbuttressed as yet by facts. For in a classical Waterfall Model product process, requirements are set before design is begun. The result, of course, is a grossly obese set of requirements, the union of many wish lists, assembled without constraints. Usually, the list is neither prioritized nor weighted. The social forces in the committee forbid the painful conflicts occasioned by even weighting, much less prioritizing. Frederick P. Brooks, Jr., The Design of Design Requirements proliferationA Plea for Lean Software features