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
The Shape of Design
Near and far
The creative process, in essence, is an individual in dialogue with themselves and the work. The painter, when at a distance from the easel, can assess and analyze the whole of the work from this vantage. He scrutinizes and listens, chooses the next stroke to make, then approaches the canvas to do it. Then, he steps back again to see what he’s done in relation to the whole. It is a dance of switching contexts, a pitter-patter pacing across the studio floor that produces a tight feedback loop between mark-making and mark-assessing. The artist, when near, is concerned with production; when far, he enters a mode of criticism where he judges the degree of benefit (or detriment) the previous choice has had on the full arrangement.
Painting’s near and far states are akin to How and Why: the artist, when close to the canvas, is asking How questions related to craft; when he steps back, he raises Why questions concerned with the whole of the work and its purpose. Near and Far may be rephrased as Craft and Analysis, which describe the kinds of questions the artist asks while in each mode. This relationship can be restated in many different ways, each addressing a necessary balance:
- How and Why
- Near and Far
- Making and Thinking
- Execution and Strategy
- Craft and Analysis
Why we should read
Unfortunately, the program met its end because the show’s approach opposed the contemporary standard format of children’s television: teaching kids how to read, rather than Reading Rainbow’s objective, which was to teach kids about why they should read.
Reading Rainbow had a long run, lasting twenty-three years, but its cancellation feels like a symbolic blow. Education, just like climbing the ladder, must be balanced between How and Why. We so quickly forget that people, especially children, will not willingly do what we teach them unless they are shown the joys of doing so. The things we don’t do out of necessity or responsibility we do for pleasure or love; if we wish children to read, they must know why.
We hear a voice whisper
The Shakers have a proverb that says, “Do not make something unless it is both necessary and useful; but if it is both, do not hesitate to make it beautiful.” We all believe that design’s primary job is to be useful. Our minds say that so long as the design works well, the work’s appearance does not necessarily matter. And yet, our hearts say otherwise. No matter how rational our thinking, we hear a voice whisper that beauty has an important role to play.
Needs more love
He held the phone to his chest, looked at me, and simply said, “Needs more love.” He pushed the portfolio back across his desk, smiled warmly, and shooed me out of his office.
I still think about this advice, and what exactly he might have meant when he said my work needed more love. At the time, I took it to mean that I should improve my craft, but I’ve come to realize that he was speaking of something more fundamental and vital. My work was flat, because it was missing the spark that comes from creating something you believe in for someone you care about. This is the source of the highest craft, because an affection for the audience produces the care necessary to make the work well.
One candle can light another
Lighting one candle
with another candle—
spring evening.Buson is saying that we accept the light contained in the work of others without darkening their efforts. One candle can light another, and the light may spread without its source being diminished.
A great leap of lightness
The first step of any process should be to define the objectives of the work with Why-based questions. The second step, however, should be to put those objectives in a drawer. Objectives guide the process toward an effective end, but they don’t do much to help one get going. In fact, the weight of the objectives can crush the seeds of thought necessary to begin down an adventurous path.
The creative process, like a good story, needs to start with a great leap of lightness, and that is only attainable through a suspension of disbelief. The objectives shouldn’t be ignored forever, but they should be defined ahead of time, set aside, and then deployed at the appropriate moment so that we may be audacious with our ideas.
Going evil
To begin, we must build momentum and then reintroduce the objectives to steer the motion. I find the best way to gain momentum is to think of the worst possible way to tackle the project. Quality may be elusive, but stupidity is always easily accessible; absurdity is fine, maybe even desired. If the project is a business card for an optician, perhaps you imagine it is illegible. (This is in the spirit, but you can do better.) If it is a brochure for an insurance agency, imagine otters on the cover and deranged handwriting on the inside for the copy. (Further!) If it is design for an exhibition of Ming Dynasty vases, brand it as an interactive show for kids, and put the vases on precariously balanced pedestals made of a shiny metal that asks to be touched. (Yes!)
The important realization to have from this fun—though fruitless–exercise is that every idea you have after these will be better. Your ideas must improve, because there is no conceivable way that you could come up with anything worse.
The momentum of making
Limitations narrow a big process into a smaller, more understandable space to explore. It’s the difference between swimming in a pool and being dropped off in the middle of the ocean with no land in sight. Those limitations also become the basis for the crucial first steps in improvisation. After those, the momentum of making accelerates as ideas are quickly generated without judgment.
Let the body wander
If the mind needs to wander, best let the body do the same. A short walk is more effective in coming up with an idea than pouring all the coffee in the world down your gullet.
Message, tone, format
All design work seems to have three common traits: there is a message to the work, the tone of that message, and the format that the work takes. Successful design has all three elements working in co-dependence to achieve a whole greater than the sum of the individual parts.
Asking why
Most inventions are recombinations of existing things, but where do the sparks for those combinations come from? What instigates that magic to make hybrids, to use them for unimagined purposes, and to inspire new settings for the three levers? Certain advancements seem logical and inevitable—smaller cellphones, faster computers, more reliable medical technology—while others seem to come out of nowhere. Turning avocado into caviar, for example, is not a logical conclusion in the kitchen. That choice is an inspired one. You can always spot these brilliant inventions as instances of magic, because our reaction, much like Achatz’s first meal at elBulli, is always disbelief.
Henry Ford famously said that if he had asked his customers what they wanted, they would have said a faster horse. Of course, we know that the faster horse is a testament to the limited imagination of customers, but I’d suggest that it’s more representational of not reassessing the objectives of the work in light of new opportunities. The faster horse is a recombination of the three levers in a predictable way: the customer’s answer is staunchly loyal to the horse, the already established format of transportation. They are inside of the adjacent possible, and ask a How question: How can horses be better?
Asking a Why question leads us to a different conclusion: Why are horses important? Because they quickly and reliably get us from one place to another. A Why question defines our need and uses an objective to create a satisfactory outcome for the work. This type of question is specific enough to be observable, but flexible enough to be approached in a variety of different ways. It’s easy to think that the way to improve life is to iterate on the things that we already have, but that is a trap of limited imagination. We should be iterating on how we answer our needs, and not necessarily on the way our old solutions have taken shape. The root of our practice is located in the usefulness of the work, not the form that it takes.
Outcomes and consequences
The primary purpose of the design is to have it do something particular, not be any particular thing. All of this implies that design is a field of outcomes and consequences more than one of artifacts. The forms that designers produce are flexible, so long as the results serve the need.
The source of delight
Design doesn’t need to be delightful for it to work, but that’s like saying food doesn’t need to be tasty to keep us alive. The pedigree of great design isn’t solely based on aesthetics or utility, but also the sensation it creates when it is seen or used. It’s a bit like food: plating a dish adds beauty to the experience, but the testament to the quality of the cooking is in its taste. It’s the same for design, in that the source of a delightful experience comes from the design’s use.
Every exit is an entrance somewhere
At the Ace Hotel in New York, a required exit sign over a door was an eyesore, and a stark contrast from the considered, detailed wall where it was mounted. Rather than accept the wart as it was, the sign was embraced as a chance to create an experience for the hotel’s guests by integrating the exit sign into the space. Now, surrounding the sign are other letters painted on the wall in a similar condensed style.
Every requirement is an opportunity for delight, even the ugly ones. Sometimes the creative treatment of these warts are the most enjoyable parts of a design.