Curiosity & Wonder
Pebbles on the beach
An affection for words
Humility
Don’t Play It Like the Flute
Eulogy for Steve Jobs
The five dimensions of curiosity
Ignorant, but curious
Pointing at things
Looking Closely is Everything
An Essay by Craig ModKambara, detail by detail.
I’d say that that huh is the foundational block of curiosity. To get good at the huh is to get good at both paying attention and nurturing compassion; if you don’t notice, you can’t give a shit. But the huh is only half the equation. You gotta go huh, alright — the “alright,” the follow-up, the openness to what comes next is where the cascade lives. It’s the sometimes-sardonic, sometimes-optimistic engine driving the next huh and so on and so forth.
How am I doing, wonder?
A Quote by Louis KahnForm comes from wonder. Wonder stems from our 'in touchness' with how we were made. One senses that nature records the process of what it makes, so that in what it makes there is also the records of how it was made. In touch with this record we are in wonder. This wonder gives rise to knowledge. But knowledge is related to other knowledge and this relation gives a sense of order, a sense of how they inter-relate in a harmony that makes all things exist. From knowledge to sense of order we then wink at wonder and say How am I doing, wonder?
What's Wrong With This Model?
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
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.
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.
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?”
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.