process
On Process
People get confused, companies get confused. When they start getting bigger, they want to replicate their initial success, and a lot of them think that somehow there’s some magic in the process that they’ve created. And so they start to institutionalize process across the company. And before very long people get very confused that the process is the content.
In my career I’ve found that the best people are the ones who really understand the content. And they’re a pain in the butt to manage. But you put up with it because they’re so great at the content. And that’s what makes great products. It’s not process, it’s content.
Just-in-time manufacturing
Get embedded in the team. Designers should use sprint planning, grooming, standup, and retro as opportunities to provide design to — and receive feedback from — the rest of the team. Designs can take the form of written or verbal descriptions, not just wireframes and high-fidelity mockups.
Only design what’s needed. Use constant communication between engineering and product partners to understand what your collaborators will need next. Then, plan on delivering only what is needed, and nothing more. Use the agile process — grooming, planning, and retro — to find any shortfalls or excesses.
Avoid creating a backlog of designs. Designs don’t age well. In the time between finishing design and shipping code, it’s likely that you’ll learn something new that changes your understanding. If you’re producing more design than can be implemented, focus more on the quality of each design.
How beautiful the world would be if there were a procedure for moving through labyrinths
Design skirmishes
it is apparent that the unfolding of the design process assumed a distinctly episodic structure, which we might characterize as a series of related skirmishes with various aspects of the problem at hand.
As the scope of the problem became more determined and finite for the designer, the episodic character of the process seems to have become less pronounced. During this period a systematic working out of issues and conditions took hold within the framework that had been established. This phenomenon is not at all surprising when we consider the fundamental difference between moments of problem solving when matters are poorly defined and those with clarity and sufficiency of structure.
Within the episodic structure of the process, the problem, as perceived by the designer, tends to fluctuate from being rather nebulous to being more specific and well-defined. Furthermore, moments of "blinding" followed by periods of backtracking take place, where blinding refers to conditions in which obvious connections between various considerations of importance go unrecognized by a designer.
How we can do better
It actually doesn't matter whether you actually have a formal retrospective. It doesn't matter whether you have four or five labels of things on your retro board, or exactly how you do the retro. What does matter is the notion of thinking about what we're doing and how we can do better, and it is the team that's doing the work that does this, that is the central thing.
Holistic and prescriptive technologies
Holistic technologies are normally associated with the notion of craft. Artisans, be they potters, weavers, metal-smiths, or cooks, control the process of their own work from beginning to finish. Using holistic technologies does not mean that people do not work together, but the way in which they work together leaves the individual worker in control of a particular process of creating or doing something.
The opposite is specialization by process; this I call prescriptive technology. Here, the making or doing of something is broken down into clearly identifiable steps. Each step is carried out by a separate worker, or group or workers, who need to be familiar only with the skills of performing that one step. This is what is normally meant by "division of labor".
That which requires caring
Today's real world of technology is characterized by the dominance of prescriptive technologies.
The temptation to design more or less everything according to prescriptive and broken-up technologies is so strong that it is even applied to those tasks that should be conducted in a holistic way. Any tasks that require caring, whether for people or nature, any tasks that require immediate feedback and adjustment, are best done holistically. Such tasks cannot be planed, coordinated, and controlled the way prescriptive tasks must be.
Prescriptive technologies eliminate the occasions for decision-making and judgment in general and especially for the making of principled decisions. Any goal of the technology is incorporated a priori in the design and is not negotiable.
Direct management
Direct Management does not include or permit the concept of profit to occur. The management is fee-based, or based as a fixed salary, and all construction costs are fixed ahead of time, and the building design is modified during construction, to make up any over-runs. The manager is not able to move money around at will, or put it in their pocket. At the same time, the design is approximately fixed, but with the understanding that it may be changed, during the evolution of the building, so that subtle adaptations can be included in the emerging building. In the Direct Management method it is the architect themselves and the direct manager who together manage the building works and all on-site construction for the owner.
Manifesto for Agile Software Development
A DefinitionWe are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Deadlines are bullshit
An ArticleIn software development deadlines are a necessary evil. It is important to understand when they are necessary, and it is important to understand why they are evil.
- External vs. internal deadlines
- Why are internal deadlines evil?
- Engineers who love their work
The Design Diagram
An Idea by Charles Eames & Ray EamesThis Eames drawing, often referred to as the Design Diagram, was created for a 1969 exhibition at the Louvre entitled, What is Design? Charles and Ray mailed it to the exhibition curator to augment their answers to a series of questions she had posed.
In Defence of Intuition
An Essay by Boris MüllerDesign, it seems, is not only becoming more methodical but also more scientific. This is not surprising. Design as a discipline has moved from “product beautification” to being a central part of product development. It has incorporated methodologies from human-computer interaction, sociology, and anthropology as well as advertising and management. And with the rise of design thinking, a wider range of professional disciplines are using creative methods.
I don’t want to criticize design methodologies. But against the backdrop of an overly structured design process, it is important to remind our community that there is one fundamental aspect to design that cannot be formalized in a methodology. And that is intuition.
Why we need to stop over-complicating UX
An Article by Hugo FroesMany have become so focused on the process and methodologies that they’ve forgotten the fundamentals of why we started focusing on the user and what we hope to achieve with that focus.
Beyond Artboards
An Essay by Chuánqí SunThe Pursuit of Lossless Design-Development Handoffs.
Just-in-time Design
An Article by Matthew StrömThere is a disconnect between product design and product engineering.
The Hot Potato Process
An Article by Dan MallThe big misconception I’ve seen designers and developers often fall victim to is believing that handoff goes one way. Designers hand off comps to developers and think their work is done. That puts a lot of pressure on the designer to get everything perfect in one pass.
Instead, great collaboration follows what Brad Frost and I call “The Hot Potato Process,” where ideas are passed quickly back and forth from designer to developer and back to designer then back to developer for the entirety of a product creation cycle.
Building Momentum
An Article by Dan MallFight the Waterfall
Start all of the pieces of work a little bit earlier. The key to starting work early is not succumbing to the pressure of having to finish the work. Don’t worry about finishing. If you’re a developer, you can start doing things while your design or information architect are working because a lot of your work actually isn’t dependent on their work. Some of it is, so you probably won’t be able to finish, but that shouldn’t stop you from starting.
Share Work-in-Progress Early and Often
When you share work-in-progress, share it with the caveat that no feedback is needed at this point. You’re simply sharing it to let people know where you are. For example, if you have to make 12 wireframes, share it when you finish 2 or 3. Rather than spending a whole week to drop 12 wireframes, share 2 – 3 wireframes every 2 days. The more often you do this, you start to build rhythm, and rhythm builds momentum.
The care and feeding of software engineers (or, why engineers are grumpy)
An Article by Nicholas ZakasWe do say “no” very quickly, not just to designs, but to everything. That led me into thinking about the psychology of software engineers and what makes us the way we are.
The art of taking
A Quote"By making it possible for the photographer to observe his work and his subject simultaneously, and by removing most of the manipulative barriers between the photographer and the photograph, it is hoped that many of the satisfactions of working in the early arts can be brought to a new group of photographers. The process must be concealed from—non-existent for—the photographer, who by definition need think of the art in taking and not in making photographs. In short, all that should be necessary to get a good picture is to take a good picture, and our task is to make that possible."
— Edwin H. Land, co-founder of Polaroid
Painting With the Web
An Article by Matthias OttSo much about [Gerhard Richter's painting process] reminds me of designing and building for the Web: The unpredictability, the peculiarities of the material, the improvisation, the bugs, the happy accidents. There is one crucial difference, though. By using static wireframes and static layouts, by separating design and development, we are often limiting our ability to have that creative dialogue with the Web and its materials. We are limiting our potential for playful exploration and for creating surprising and novel solutions. And, most importantly, we are limiting our ability to make conscious, well-informed decisions going forward. By adding more and more layers of abstraction, we are breaking the feedback loop of the creative process.
Technical debt as a lack of understanding
An Article by Dave Rupert"If you develop a program for a long period of time by only adding features but never reorganizing it to reflect your understanding of those features, then eventually that program simply does not contain any understanding and all efforts to work on it take longer and longer.” — Ward Cunningham
Interaction of Color
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.Practice before theory
Instead of mechanically applying or merely implying laws and rules
of color harmony, distinct color effects are produced
– through recognition of the interaction of color –
by making, for instance,
2 very different colors look alike, or nearly alike.The aim of such study is to develop – through experience
– by trial and error – an eye for color.
This means, specifically, seeing color action
as well as feeling color relatedness.As a general training it means development of observation and articulation.
This book, therefore, does not follow an academic conception
of “theory and practice.”
It reverses this order and places practice before theory,
which, after all, is the conclusion of practice.50 reds
If one says “Red” (the name of a color)
and there are 50 people listening,
it can be expected that there will be 50 reds in their minds.
And one can be sure that all these reds will be very different.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.Scotopic seeing
The sensitivity
and consequently the registration of the retina of an eye is different
from the sensitivity and registration of a photographic film.Normally, black-and-white photography registers all lights lighter
and all darks darker than the more adjustable eye perceives them.
The eye also distinguishes better the so-called middle grays,
which in photography are often flattened if not lost.This shows what a higher key in light can lose in photography.
The greatest advantage the eye has over photography
is its scotopic seeing in addition to its photopic seeing.
The former means, briefly, the retinal adjustment to lower light conditions.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.Color intervals
The tune of “Good morning to you” consists of 4 tones. It can be sung
in a high soprano, a low basso, and in all in-between voices, as well as
on many levels and in many keys. It can be played on innumerable instruments.In all possible ways of performance, this melody will keep its character
and it will be recognized instantly.Why? The intervals of the 4 tones, that is, their acoustical
constellation (again comparable with a topographical relationship),
remains the same.Although it is not common practice, one can also speak of intervals
between colors.
Colors and hues are defined, as are tones in music, by wavelength.Any color (shade or tint) always has 2 decisive characteristics:
color intensity (brightness) and light intensity (lightness).
Therefore, color intervals also have this double-sidedness, this duality.Time and space
Tones appear placed and directed predominantly in time from before to now to later.
Their juxtaposition in a musical composition is perceived
within a prescribed sequence only.
Horizontally, the tones follow each other,
perhaps not in a straight line, but of necessity in a prescribed order
and only in 1 direction – forward.
Tones heard earlier fade, and those farther back disappear, vanish.
We do not hear them backward.Colors appear connected predominantly in space. Therefore,
as constellations they can be seen in any direction and
at any speed. And as they remain, we can return to them repeatedly
and in many ways.
This remaining and not remaining, or vanishing and not vanishing,
shows only 1 essential difference between the fields of tone
and color.The accuracy of perception in one field is matched
by the durability of retention in the other, demonstrating
a curious reversal in visual and auditory memory.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.Flexible imagination
By giving up preference for harmony,
we accept dissonance to be as desirable as consonance.Besides a balance through color harmony, which is comparable
to symmetry, there is equilibrium possible between
color tensions, related to a more dynamic asymmetry.Again: knowledge and its application is not our aim;
instead, it is flexible imagination, discovery, invention – 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."The Weber-Fechner law
Exponential increases in physical stimuli produce linear perceptual increases.
Thinking in situations
Naturally, practice is not preceded but followed by theory.
Such study promotes a more lasting teaching and learning
through experience. Its aim is development of creativeness
realized in discovery and invention – the criteria of creativity,
or flexibility, being imagination and fantasy. Altogether
it promotes “thinking in situations,” a new educational concept
unfortunately little known and less cultivated, so far.Not of method but of heart
In the end, teaching is a matter not of method but of heart.
The teacher actually is right and always will gain confidence
when he admits that he does not know, that he cannot decide, and,
as it often is with color, that he is unable to make a choice
or to give advice.Besides, good teaching is more a giving of right questions
than a giving of right answers.Results of a search
This book presents results of a search, not of what is academically called research.
In addition to the dedication of this book, I should like to state that my students in color have taught me more color than have books about color.
Simple forms
The concept that “the simpler the form of a letter the simpler its reading” was an obsession of beginning constructivism. It became something like a dogma, and is still followed by “modernistic” typographers.
This notion has proved to be wrong, because in reading we do not read letters but words, words as a whole, as a “word picture.” Ophthalmology has disclosed that the more the letters are differentiated from each other, the easier is the reading.
Without going into comparisons and the details, it should be realized that words consisting of only capital letters present the most difficult reading—because of their equal height, equal volume, and, with most, their equal width. When comparing serif letters with sans-serif, the latter provide an uneasy reading. The fashionable preference for sans-serif in text shows neither historical nor practical competence.