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
Dieter Rams: As Little Design as Possible
Beyond improvement
In so many ways Dieter Rams’s work is beyond improvement. Although new technologies have since offered new opportunities, his designs are not undermined by the limits of the technologies of their time. The concave button top, designed to stop your finger from slipping as it made the long travel necessary for earlier mechanical switches, does not point to obsolete mechanisms. Instead, it reminds us how immediately and intuitively form alone can describe what an object does and suggest how we should use it.
Cardinal sin
Indifference towards people and the reality in which they live is actually the one and only cardinal sin in design.
The duty of industrial design is first and foremost to users and the users are, generally, human beings, with all their complexities, habits, ideas and idiosyncrasies.
On display
The SK4 record player, aka 'Snow White's Coffin'.
Instead of being hidden away in a piece of furniture, the controls and the functional aspects of the device were not only on display, but they were the predominant feature of the design.
Rams suggested making a transparent lid from a new plastic that had just come on the market and was being used for advertising displays. It was an inspired thought and lent the phonograph just the lightness needed to balance the metal and wood of the base, as well as helping to define the acoustics. It also set the standard for all record players that followed - a turntable without a Perspex dust cover is now almost unthinkable.
Long-term
"Apart from his own design work, this is the second greatest achievement of Dieter Rams: establishing a design department within a company, which succeeded for decades in preserving its own individual approach and rigorously advancing it, without really being influenced by changing market interests." — Klaus Kemp
He is right; it was a remarkable feat. It takes a considerable degree of doggedness and conviction to follow the ungratifying and difficult path of insisting on a consistently long-term view in a corporate world that is constantly shifting and full of short-term decisions.
Humble servants
Our electrical appliances should be humble servants, to be seen and heard as little as possible. They should ideally stay in the background, like a valet in the old days, that one hardly noticed. — Erwin Braun
They should accompany an individual over a long period of time without hindering or disturbing through ‘extravagant forms, loud colors or flashy proportions’.
Restrained beauty
Braun design had a beauty that was more than skin deep. It would be wrong to say that because the Braun approach spurned fashion in an ongoing quest for functional and useable perfection, it ended up with this beauty by accident. There is a very strong aesthetic sense in both the proportion and materials of nearly all the products of the Rams era. They have a ‘restrained beauty’, he admits.
Braun products designed by Rams and his team have a haptic aesthetic as well: when you pick them up, handle them, and use them as the tools they are supposed to be, you become aware of the effort that has gone into making them sit comfortably in the hand, of the texture, weight and balance they possess, and of the satisfying click of the control buttons.
Camels
When you look at the consumer products generated by many other manufacturers, and even by Braun today, there seem to be an awful lot of camels around. Maybe these companies are too diffuse, have the decision-makers in the wrong places or are continually making the wrong decisions and have no one to stop them. They make products with short-term goals in mind, seducing the eye of the buyer with fashionable colors, sensational curves or exotic surfaces. They may have external designers and, perhaps most significantly, the brand identity is defined by external marketing concerns, rather than design or user-related issues.
The lesson to learn from Braun is that allowing a consistent philanthropic design approach to define a company can be extremely successful if it is executed with discipline, flexibility and good timing combined with hard work and, not least, great talent.
A timeless quality
Of all Rams’s products, the 606 Universal Shelving System is perhaps his most successful in fulfilling his own principles of good design. It is still in production today, some fifty years after its conception. The system is distinctive yet unobtrusive, and when the shelves and cabinets are filled, its slim profile allows it to fade quietly into the background.
Its ‘plainness’ lends it a timeless quality that has transcended the vagaries of fashion like no other of Rams’s designs. It was conceived in such a way as to optimize its function as simply and in as many different situations as possible, while still permitting upgrades and alterations without falling into obsolescence: all later adaptations and additions could still be integrated into the original structure and sizes.
"Fashion objects are not capable of being long-lived," said Rams in 2007. "We simply cannot afford this throw-away mentality anymore. Good design has to have built-in longevity. I believe that the secret of the longevity of my furniture lies in its simplicity and restraint. Furniture should not dominate, it should be quiet, pleasant, understandable and durable."
A certain kind of world
Perhaps more directly than with the Braun products, my furniture arose from a belief in how the world should be ‘furnished’ and how man should live in this artificial environment. In this respect, each piece of furniture is also a design for a certain kind of world and way of living, they reflect a specific vision of mankind.
Designing detail
My heart belongs to the details.
I actually always found them to be more important than the big picture.
Nothing works without details.
They are everything, the baseline of quality.Truly functional design only comes from the most careful and intense attention to detail.
Although he did not directly design all products and even had very little to do with some of them, he constantly encouraged tiny improvements that could make a good design better. This attention to detail ranged from the acuteness of angles in forms; the size, feels and distances between switches; the integration of handle fixings; the placement and nature of graphic elements on the products themselves and extended to product photography and packaging.
Designing detail is about achieving a fine balance in all aspects and areas of the product, including those external to the object.
Controlled!
Braun design is greatly reduced - stripped of all that is unnecessary. Nevertheless, there is a strong aesthetic characterized by balance, order and harmony.
Self-control is very important. Although my own taste is involved it always has to be under control. Not suppressed though! Controlled!
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.
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.
Shorten the wings
The labile tastes of certain decision-makers in a company are often a great burden for designers. Too many feel themselves qualified to pass judgment. And how insensitive, how superficial these judgments often are.
Taste, believes Rams, is something that needs to be trained, since the aesthetic decisions at this level in product design are intrinsically bound to the entire form and function of the object. It would be unimaginable, for example, that the management of an aerospace company would ask the designers of a new plane to shorten the wings because they think it would make it look prettier.
The evolution of Braun design principles
1975
Three general rules govern every Braun design - a rule of order, a rule of harmony and a rule of economy.1976
The function for us is the starting point and the target of every design.
Experience with design is experience with people.
Only orderliness makes design useful to us.
Our design attempts to bring all individual elements into their proper proportions.
Good design means to us: as little design as possible.
Our design is innovative because the behavior patterns of people change.1983
Good design is innovative.
Good design renders utility to a product.
Good design is aesthetic design.
Good design makes a product easy to understand.
Good design is unobtrusive.
Good design is honest.1985
Good design is innovative.
Good design makes a product useful.
Good design is aesthetic.
Good design makes a product understandable.
Good design is honest.
Good design is unobtrusive.
Good design is long-lasting.
Good design is thorough down to the last detail.
Good design is environmentally friendly.
Good design is as little design as possible.Less, but better
There must be millions less of things, less words, less gestures, less of everything. But every word and every gesture will become more valuable. If we can put it all into perspective we will need less things as a result.