Color
When the phenomena are endless
"There can be no description or theory of color per se," Irwin insists, "when the phenomena are endless." The notion that color can be reduced to a series of codes, to a grammar, or to a form of "mathematics," to use Wittegensetein's term, is, for Irwin, nonsense, since color is dependent on context and ground-up perceptual experience. Beginning with color codes or concepts was to reduce in advance an infinitely wide range of phenomena to a limited set of categories, editing out all specificity in favor of abstraction.
Irwin Fluorescents
In order: Kenny Price, Blue Lou, Legacy, Fourfold, Niagara.
Irwin has explained that he decided to use the fluorescent tubes in the "dumbest" way possible, but, as one critic cautioned, "dumb, it turns out, has a special meaning for him: It's a form so simple that you end up not paying attention to it as a form." Irwin's interest was, rather, in the range of light, color, reflection, and shadow interaction made possible by combining tubes with different hues and finishes by wrapping them with theatrical gels.
In the lee of the sills
The first thing you register here is the dramatic inconsistency in the coloration of the timber cladding the house in Haldenstein: the natural hues of the wood survive only in the lee of the sills, like re-growth along the parties of a head of dyed hair. But a second glance takes in the precision of the cuts made to accommodate the window and the fact that the pine is used in seamless lengths.
A universal correspondence
In 1923 Kandinsky proposed a universal correspondence between the three elementary shapes and the three primary colors: the dynamic triangle is inherently yellow, the static square is intrinsically red, and the serene circle is naturally blue.
The series ▲■● represents Kandinsky’s attempt to prove a universal correlation between color and geometry; it has become one of the most famous icons of the Bauhaus. Kandinsky conceived of these colors and shapes as a series of oppositions: yellow and blue represent the extremes of hot/cold, light/dark, and active/passive, while red is the intermediary between them. The triangle, square, and circle are graphic equivalents of the same polarities.
250. Warm Colors
Problem
The greens and grays of hospitals and office corridors are depressing and cold. Natural wood, sunlight, bright colors are warm. In some way, the warmth of the colors in a room makes a great deal of difference between comfort and discomfort.
Solution
Choose surface colors which, together with the color of the natural light, reflected light, and artificial lights, create a warm light in the rooms.
Hues subdued
Colors in nature are, in general, more subdued than what comes directly from the pencil or the tube of paint. Greens, especially, tend to be a lot browner than we expect.
The palette of nature
"What nature does with its colors is invariably—the palette of nature is twice as complicated, at least twice as sophisticated, as anything any artist can ever come up with. On a couple levels.
To start with, there are these amazing combinations of colors, filled with surprises and almost never wrong. I don't know how Nature ever conceived to put, say, those together. But, boy, are they right on the money!"
Colors in nature
Twice every summer we discussed whether colors in nature could clash.
Color codes
When not compelled to do otherwise, the Braun design team’s use of color in products was reduced to highly specific areas such as control switches. Restricting the use of color to small points on an otherwise neutral object concentrates its effect, which is shifted away from decoration and towards function, especially when each color is assigned a signal role such as green for ‘on / off' switches, red for ‘fm’ and yellow for ‘phono’ on hi-fis or yellow for the second hand on clocks and watches.
This color coding of operating details is a primary example of the self-explanatory nature of Braun products.
Sketches
Sketches and written notes.
The deception of color
In order to use color effectively it is necessary to recognize
that color deceives continually.What counts here – first and last – is not so-called knowledge
of so-called facts, but vision – seeing.Not the what but the how
Our concern is the interaction of color; that is, seeing
what happens between colors.We are able to hear a single tone.
But we almost never (that is, without special devices) see a single color
unconnected and unrelated to other colors.
Colors present themselves in continuous flux, constantly related to
changing neighbors and changing conditions.As a consequence, this proves for the reading of color
what Kandinsky often demanded for the reading of art:
what counts is not the what but the how.Disliked colors
We try to recognize our preferences and our aversions –
what colors dominate in our work; what colors, on the other hand,
are rejected, disliked, or of no appeal. Usually a special effort
in using disliked colors ends with our falling in love with them.A cook with taste
Observe the interior and exterior, the furniture and textile decoration
following such color schemes, as well as commercialized color “suggestions”
for innumerable do-it-yourselves.Our conclusion: we may forget for a while those rules of thumb
of complementaries, whether complete or “split”, and of triads and
tetrads as well.
They are worn out.Second, no mechanical color system is flexible enough
to precalculate the manifold changing factors, as named before,
in a single prescribed recipe.Good painting, good coloring, is comparable to good cooking.
Even a good cooking recipe demands tasting and repeated tasting
while it is being followed.
And the best tasting still depends on a cook with taste.Does it have color?
Whether something “has color” or not is as hard to define verbally as are
such questions as “what is music” or “what is musical."Chromatic mutiny
Nevertheless there were a number of colorful appliances produced by Braun, particularly from the late 1960s onwards, when plastics in bright primary colors became fashionable and available.
T3 domino lighter
KMM 2 coffee grinder
HLD 4 hairdryer
KF 145 coffee maker
HT 95 pop-up toasterWhen Rams’s team used color in such a way, it was uncompromising in its intensity: loud and demanding. The highly reduced forms of the products that it clothed, which had gently rounded edges, smooth opaque surfaces and discreet (usually black) detailing only served to increase this intensity.
"The intention was to create product alternatives for people who wished for strong color highlights in their living environments. This impulse came from marketing - not from design,” says Rams, dissociating himself from this approach. This was one instance where marketing got the upper hand in the decision-making process and the design team had to bow to contemporary fashion.
Indeed, there is a defiant aspect to these chromatic exceptions; they are not so much compromises as mutinous responses. Nevertheless, the resulting products are beautiful objects in their stand-alone way.
A strange calligraphy
Along the sand there will be frisky shadows, that will dance and fall away.
Or, if there is snow, the flames will write a strange calligraphy against the whiteness.Interaction of Color
A Book by Josef AlbersBetter colormaps?
An Article by Mark LibermanA modest sample of alternative ways of coloring the same type of 2-D density plots of rates of F0 change and amplitude change.
Werner’s Nomenclature of Colours
A Website by Nicholas RougeuxA recreation of the original 1821 color guidebook with new cross references, photographic examples, and posters designed by Nicholas Rougeux.
Color Controversy
A Website by Leo RobinovitchSo some friends and I were talking about colors one day and how we all see colors a bit differently and how that's neat.
But is there a color that is interpreted differently THE MOST? Is there a most controversial color? Well, (if I contrive an ongoing survey and collect data about it), the answer is yes, of course!
The Subtleties of Color
A Series by Robert SimmonThe use of color to display data is a solved problem, right? Just pick a palette from a drop-down menu (probably either a grayscale ramp or a rainbow), set start and end points, press “apply,” and you’re done. Although we all know it’s not that simple, that’s often how colors are chosen in the real world. As a result, many visualizations fail to represent the underlying data as well as they could.
The Design of Design
What's Wrong With This Model?
A ChapterDesign process models: A summary argument
- A formal design process model is needed, to help organize design work, to aid communication in and about projects, and for teaching.
- Having a visual, geometric representation of a design process model is crucial, for designers are spatial thinkers. They will most easily learn, think about, share, and talk in terms of a model with a clear geometric picture.
- The Rational Model of design occurs naturally to engineers.
- The linear, step-by-step Rational Model is highly misleading. It does not reflect what real designers do, or what the best design thinkers identify as the essence of the design process.
- The bad model matters. It has led to the too-early binding of requirements, leading in turn to bloated products and schedule/budget/performance disasters.
- The Rational Model has persisted in practice despite its inadequacies and plenty of cogent critiques. This is because of its seductive logical simplicity, and because builders and clients needs “contracts."
- Several alternative models have been proposed. I find Boehm’s Spiral Model the most promising. We need to keep developing it.
The spiral model
The spiral shape certainly suggests progress. It associates successive repetitions of the same activity. The geometric shape is easily understood and memorable. The model emphasizes prototyping, starting with user-interface prototypes and user testing long before an operational prototype is possible.
Since a development model is principally used by developers, I believe having it designer-centered is entirely appropriate. With Boehm and against Denning and Dragon, I advocate frequent but not continuous interaction with representative users, with successive prototypes as the vehicles.
I strongly believe that way forward is to embrace and develop the Spiral Model.
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.
Requirements proliferation
Any attempt to formulate all possible requirements at the start of a project will fail and would cause considerable delays. — Pahl and Beitz, Engineering Design
As Project Manager, I had to reject the requirements document as totally impractical, and have a quite small team of architects, marketers, and implementers extract the essence.
Requirements proliferation must be fought, by both birth control and infanticide.
The architectural contracting model
It is the necessity for contracts, whether within an organization or between organizations, that forces the too-early binding of goals, requirements, constraints. The pressure for a complete and agreed-upon set of requirements run into the hard fact, that it is essentially impossible to specify any complete and accurate set of requirements for any complex system except in iterative interaction with the design process.
How have the centuries-old building design disciplines handled this perplexity? Fundamentally, by a quite different contracting model.
- The client develops a program, not a specification, for the building.
- He contracts with an architect, usually on an hourly or percentage basis, for services, not for a specified product.
- The architect elicits from the client, the users, and other stakeholders a more complete program, which does not pretend to be a rigid contractable product specification.
- The architect does a conceptual design that approximates the reconciliation of program and the constraints of budget, schedule, and code. This serves as a first prototype, to be conceptually tested by the stakeholders.
- After iteration, the architect performs design development, often producing more detailed drawings, a 3-D scale model, mockups, and so on. After stakeholder iteration, the architect produces construction drawings and specifications.
- The client uses these drawings and specifications to enter into a fixed-price contract for the product.
Notice how this long-evolved model separates the contract for design from the contract for construction. Even when both are performed by the same organization, this separation clarifies many things.
The rational model of design
Engineers seem to have a clear, if usually implicit, model of the process of design. It is usually an orderly model of an orderly process as the engineer conceives it.
The notion that the design process should be modeled as a systematic step-by-step process seems to have first developed in the German mechanical engineering community.
Herbert Simon independently argues for design as a search process in The Sciences of the Artificial. He was motivated to lay out a strictly rational model of design precisely because such a model was a necessary precursor to automating design. His model remains influential even if today we recognize the "wicked problem" of original design as one of the least promising candidates for AI.
In software engineering, Winston Royce independently introduced a seven-step Waterfall Model to bring order to the process. In fact, Royce introduced his waterfall as a straw man that he then argued against, but many people have cited and followed the straw man rather than his more sophisticated models. Even if ironically, Royce's seven-step model must be considered one of the foundational statements of the Rational Model of Design.
Design process models
Any systematization of the design process is a great step forward compared to "Let's just start coding, or building." It:
- Provides clear steps for planning a design project
- Furnishes clearly definable milestones
- Suggests project organization and staffing
- Helps communication within the design team
- Is readily teachable to novices, and tells novices facing their first design assignments where to begin.
The Rational Model in particular brings yet more advantages. The early explicit statement of goals, secondary desiderata, and constraints helps a team avoid wandering, and it breeds team unification on purposes. Planning the whole design process before starting coding or formal drawings avoids many troubles and much wasted effort. Casting the process as a systematic search of a design space broadens the horizon of the individual designers and lifts their eyes far beyond their previous personal experiences.
But the rational model is much too simplistic, even in Simon's richly developed version.
The dual ladder
The first task for growing designers, as opposed to managers, is to craft a proper career path for them, one whose compensation and sociological status reflect their true value to the creative enterprise. This is commonly called the dual ladder. It it easy to give corresponding salaries to corresponding rungs, but it requires strong proactive measures to give them equal prestige: equal offices, equal staff support, reverse-biased raises when duties change.
Why does the dual ladder need special attention? Perhaps because managers, being human, are inherently inclined to consider their own tasks more difficult and important than design and need to deliberately assess what makes creativity and innovation happen.
A platonic ideal
As the architecture design progressed, I observed what at first seemed quite strange. For the architecture team, the real System/360 was the Design Concept itself, a Platonic ideal computer. Those physical and electrical Model 50, Model 60, Model 70, and Model 90 things under construction out on the engineering floors were but Plato’s shadows of the real System/360. The real System/360’s most complete and faithful embodiment was not in silicon, copper, and steel, but in the prose and diagrams of IBM System/360 Principles of Operation, the programmer’s machine language manual.
I had a similar experience with the View/360 beach house. Its Design Concept came to be real long before any construction began. It persisted through many versions of drawings and cardboard models.
The design concept
Is there positive value to recognizing an invisible Design Concept as a real entity in design conversations? I think so.
First, great designs have conceptual integrity—unity, economy, clarity. They not only work, they delight, as Vitruvius first articulated. We use terms such as elegant, clean, beautiful to talk about bridges, sonatas, circuits, bicycles, computers, and iPhones. Recognizing the Design Concept as an entity helps us to seek its integrity in our own solo designs, to work together for it in team designs, and to teach it to our youth.
Second, talking frequently about the Design Concept as such vastly aids communication within a design team. Unity of concept is the goal; it is achieved only by much conversation.
Thus, moviemakers use storyboards to keep their design conversations focused on the Design Concept, rather than on implementation details.
The Idea
The design is thus the mental formulation, which Sayers calls “the Idea,” and it can be complete before any realization is begun. Mozart’s response to his father’s inquiry about an opera due to the duke in three weeks both stuns us and clarifies the concept.
For most human makers of things, the incompletenesses and inconsistencies of our ideas become clear only during implementation. Thus it is that writing, experimentation, “working out,” are essential disciplines for the theoretician.
The boldest decisions
In retrospect, many of the case studies have a striking common attribute: the boldest design decisions, whoever made them, have accounted for a high fraction of the goodness of the outcome. These bold decisions were made due sometimes to vision, sometimes to desperation. They were always gambles, requiring extra investment in hopes of getting a much better result.
Intuition and systems
Systematic design excluding intuition yields pedestrian follow-ons and knock-offs; intuitive design without system yields flawed fancies. How to weld intuition and systematic approach? How to grow as a designer? How to function in a design team?