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
Contrasting Concepts of Harmony in Architecture
The realm of feeling
Alexander: If you say: "Well, look, you're a feeling type, and I'm a thinking type, so let's not discuss that because we are always going to be on different sides", then it removes from this discussion what I feel to be the absolute heart and soul of the matter when it comes to buildings. Now I don't want to deny at all what you are saying about personalities. But I really cannot conceive of a properly formed attitude towards buildings, as an artist or a builder, or in any way, if it doesn't ultimately confront the fact that buildings work in the realm of feeling.
Panic
Alexander: It never occurred to me that someone could so explicitly reject the core experience of something like Chartres. It's very interesting to have this conversation. If this weren't a public situation, I'd be tempted to get into this on a psychiatric level. I'm actually quite serious about this. What I'm saying is that I understand how one could be very panicked by these kinds of feelings. Actually, it's been my impression that a large part of the history of modern architecture has been a kind of panicked withdrawal from these kinds of feelings, which have governed the formation of buildings over the last 2000 years or so.
Why that panicked withdrawal occurred, I'm still trying to find out. It's not clear to me. But I've never heard somebody say, until a few moments ago, someone say explicitly: "Yes, I find that stuff freaky. I don't like to deal with feelings. I like to deal with ideas.”
The pitched roof
Eisenman: I would argue that the pitched roof is – as Gaston Bachelard points out – one of the essential characteristics of "houseness". It was the extension of the vertebrate structure which sheltered and enclosed man. Michel Foucault has said that when man began to study man in the 19th century, there was a displacement of man from the center. The representation of the fact that man was no longer the center of the world, no longer the arbiter, and, therefore, no longer controlling artifacts, was reflected in a change from the vertebrate-center type of structure to the center-as-void.
The trick of little machines
Alexander: Up until about 1600, most of the world views that existed in different cultures did see man and the universe as more or less intertwined and inseparable ... either through the medium of what they called God or in some other way. But all that was understood. The particular intellectual game that led us to discover all the wonders of science forced us to abandon temporarily that idea. In other words, in order to do physics, to do biology, we were actually taught to pretend that things were like little machines because only then could you tinker with them and find out what makes them tick. That's all fine. It was a tremendous endeavor, and it paid off.
But it may have been factually wrong. That is, the constitution of the universe may be such that the human self and the substance that things made out of, the spatial matter or whatever you call it, are much more inextricably related than we realized. Now, I am not talking about some kind of aboriginal primitivism. I am saying that it may actually be a matter of fact that those things are more related than we realize. And that we have been trained to play a trick on ourselves for the last 300 years in order to discover certain things. Now, if that's true – there are plenty of people in the world who are beginning to say it is, by the way, certainly in physics and other related subjects – then my own contribution to that line of thought has to do with these structures of sameness that I have been talking about.
In other words, the order I was sketching out last night is ultimately, fundamentally an order produced by centers or wholes which are reinforcing each other and creating each other. Now, if all of that is so, then the pitched roof would simply come about as a consequence of all that – not as an antecedent. It would turn out that, in circumstances where one is putting a roof on a building, in the absence of other very strong forces that are forcing you to do something different, that is the most natural and simple roof to do. And, therefore, that kind of order would tend to reappear – of course, in a completely different, modern technological style – simply because that is the nature of order, not because of a romantic harkening back to past years.
Merely a building
Eisenman: Le Corbusier once defined architecture as having to do with a window which is either too large or too small, but never the right size. Once it was the right size it was no longer functioning. When it is the right size, that building is merely a building. The only way in the presence of architecture that is that feeling, that need for something other, when the window was either too large or too small.
Fucking up the world
City Hall by Rafael Moneo, Logroño, La Rioja, Spain.
Alexander : At least my experience tells me, that when a group of different people set out to try and find out what is harmonious, what feels most comfortable in such and such a situation, their opinions about it will tend to converge, if they are mocking up full-scale, real stuff. Of course, if they're making sketches or throwing out ideas, they won't agree. But if you start making the real thing, one tends to reach agreement. My only concern is to produce that kind of harmony.
The thing that strikes me about your friend's building – if I understood you correctly – is that somehow in some intentional way it is not harmonious. That is, Moneo intentionally wants to produce an effect of disharmony. Maybe even of incongruity.
Eisenman: That is correct.
Eisenman: I find that incomprehensible. I find it very irresponsible. I find it nutty. I feel sorry for the man. I also feel incredibly angry because he is fucking up the world.
A good table
Eisenman: Tolstoy wrote about the man who had so many modern conveniences in Russia that when he was adjusting the chair and the furniture, etc., that he was so comfortable and so nice and so pleasant that he didn't know – he lost all control of his physical and mental reality. There was nothing. What I'm suggesting is that if we make people so comfortable in these nice little structures of yours, that we might lull them into thinking that everything's all right, Jack, which it isn't. And so the role of art or architecture might be just to remind people that everything wasn't all right.
Alexander: I can't, as a maker of things, I just can't understand it. I do not have a concept of things in which I can even talk about making something in the frame of mind you are describing. I mean, to take a simple example, when I make a table I say to myself: "All right, I'm going to make a table, and I'm going to try to make a good table." And of course, then from there on I go to the ultimate resources I have and what I know, how well I can make it. But for me to then introduce some kind of little edge, which starts trying to be a literary comment, and then somehow the table is supposed to be at the same time a good table, but it also is supposed to be I don't know what; a comment on nuclear warfare, making a little joke, doing various other things... I'm practically naive; it doesn't make sense to me.