Church on the Water, Hokkaido, 1985–8 At the edges of the outer walls to left and right, the slate floor is held back, creating a shadowed slot into which the concrete wall slips out of sight. Because the wall does not meet and bear upon the floor, as is usual, the relationship of the wall to the ground is uncertain, and the rippling surface of the black slate floor appears to float free of the walls, merging with the rippling surface of the water. Robert McCarter & Juhani Pallasmaa, Understanding Architecture weight
Lightness & Heaviness "Lightness is born of heaviness and heaviness of lightness, instantaneously and reciprocally, returning creation for creation, gaining strength proportionally as they gain in life, and as much more in life as they gain in motion. They destroy one another also at the same time, fulfilling a mutual vendetta, proof that lightness is created only in conjunction with heaviness, and heaviness only where lightness follows." — Leonardo da Vinci Robert McCarter & Juhani Pallasmaa, Understanding Architecture materialweight
Buttresses Buttresses, Ruskin writes, are structures against pressure: a cathedral’s walls want to fall outward, for example, pushed aside by the relentless weight of the roof. But this gravitational pressure can be stabilized by an exoskeleton: a sequence of buttresses that will prevent those walls from collapsing outward. However, Ruskin points out, there is a similar kind of pressure from the waves of the sea. Think of the curved hull of a ship, he writes, which is internally buttressed against the “crushing force” of the ocean around it. It is a kind of inside-out cathedral. Geoff Manaugh, BLDGBLOG www.bldgblog.com weightarchitecture
What's Wrong With This Model? A Chapter from The Design of Design by Frederick P. Brooks, Jr. What's wrong with the rational modelDeciding what to designEvaluating goodnessChanging constraintsThey just don't work that way+1 More
What's wrong with the rational model We Don’t Really Know the Goal When We Start We Usually Don’t Know the Decision Tree – We Discover It as We Go The Nodes Are Really Not Design Decisions, but Tentative Complete Designs The Goodness Function Cannot be Evaluated Incrementally The Desiderata and Their Weightings Keep Changing The Constraints Keep Changing Changing constraintsDeciding what to designThe situation talks back
Deciding what to design We Don’t Really Know the Goal When We Start The most serious model shortcoming is that the designer often has a vague, incompletely specified goal, or primary objective. In such cases, the hardest part of design is deciding what to design. I came to realize that the most useful service I was performing for my client was helping him decide what he really wanted. Today, we recognize that rapid prototyping is an essential tool for formulating precise requirements. Not only is the design process iterative; the design-goal-setting process is itself iterative. Knowing complete product requirements up front is a quite rare exception, not the norm. Therefore, goal iteration must be considered an inherent part of the design process. What's wrong with the rational model iteration
Evaluating goodness The Goodness Function Cannot be Evaluated Incrementally The Rational Model assumes that design involves a search of the decision tree, and that at every node, one can evaluate the goodness function of several downward branches. In fact, one cannot in general do this without exploring all the downward branches to all their leaves, which is possible in principle, but leads to a combinatorial explosion of alternatives in practice. What's wrong with the rational model
Changing constraints The Constraints Keep Changing The explicit listing of known constraints in the design program helps here. The designer can periodically scan the list, asking, “Can this constraint now be removed because the world has changed? Can it be entirely circumvented by working outside the design space?” What's wrong with the rational model constraints
They just don't work that way Perhaps the most devastating critique of the Rational Model, although perhaps the hardest to prove, is that most experienced designers just don’t work that way. “Conventional wisdom about problem-solving seems often to be contradicted by the behavior of expert designers. Empirical studies of design activity have frequently found ‘intuitive’ features of design ability to be the most effective and relevant to the intrinsic nature of design. Some aspects of design theory, however, have tried to develop counter-intuitive models and prescriptions for design behavior.” — Nigel Cross
We must outgrow it Why all this fuss about the process model? Does the model we and others use to think about our design process really affect our designing itself? I believe it does. I believe our inadequate model and following it slavishly lead to fat, cumbersome, over-features products and also to schedule, budget, and performance disasters. The Rational Model, in any of its forms, leads us to demand up-front statements of design requirements. It leads us to believe that such can be formulated. It leads us to make contracts with one another on the basis of enshrined ignorance. A more realistic process model would make design work more efficient, obviating many arguments with clients and much rework. The Waterfall Model is wrong and harmful; we must outgrow it.