iteration
So that you can get feedback on it and make it better
Fascinatingly, one of the other big complaints people had about agile is no iteration. I don't understand how being in an agile environment makes people less iterative, but somehow that seems to be the case. And I think it's because people misunderstand and think that agile is just about putting features out faster, and not about the important part, which is getting something in front of users faster so that you can get feedback on it and make it better.
The most rewarding iterations
Initial designs for sophisticated software applications are invariably complicated, even when developed by competent engineers. Truly good solutions emerge after iterative improvements or after redesigns that exploit new insights, and the most rewarding iterations are those that result in program simplifications.
Evolutions of this kind, however, are extremely rare in current software practice—they require time-consuming thought processes that are rarely rewarded. Instead, software inadequacies are typically corrected by quickly conceived additions that invariably result in the well-known bulk.
To anticipate all the uses and abuses
Success depends wholly on the anticipation and obviation of failure, and it is virtually impossible to anticipate all the uses and abuses to which a product will be subjected until it is in fact used and abused not in the laboratory but in real life. Hence, new products are seldom even near perfect, but we buy them and adapt to their form because they do fulfill, however imperfectly, a function that we find useful.
When we make a model and realize it's rubbish
Much of the design process is a conversation, a back-and-forth as we walk around the tables and play with the models. He doesn't like to read complex drawings. He wants to see and feel a model. He's right. I get surprised when we make a model and then realize it's rubbish, even though based on the CAD renderings it looked great.
He loves coming in here because it's calm and gentle. It's a paradise if you're a visual person. There are no formal design reviews, so there are no huge decision points. Instead we can make the presentations fluid. Since we iterate every day and never have dumb-ass presentations, we don't run into major disagreements.
Building is never a straight line
You might think that Mario 64 was built with tickets and sprints, but, according to interviews, there was no master plan, only the principles that the game should feel good and be fun. They started with just Mario in a small room, and tuned his animations and physics until he felt nice and responsive. After that, the levels were also created as they went, with the designers, developers, and director going back and forth using sketches and prototypes.
Building like this is never a straight line. Ideas and code get left on the cutting room floor because part of innovation is questioning whether what you made should exist. The process is cyclical and iterative, looking something like this.
Between the two spaces
It is widely accepted that creative design is not a matter of first fixing the problem and then searching for a satisfactory solution concept; instead it seems more to be a matter of developing and refining together both the formulation of the problem and ideas for its solution, with constant iteration of analysis, synthesis, and evaluation processes between the two “spaces” – problem and solution.
The game discovering itself
We like to think about this process as the game discovering itself over time. Because as iterators, rather than designers, it’s our job to simply play the game, listen to it, feel it, and kind of feel out what it seems to want to become - and just follow the trails of what’s fun.
Deciding what to design
We Don’t Really Know the Goal When We Start
The most serious model shortcoming is that the designer often has a vague, incompletely specified goal, or primary objective. In such cases, the hardest part of design is deciding what to design.
I came to realize that the most useful service I was performing for my client was helping him decide what he really wanted.
Today, we recognize that rapid prototyping is an essential tool for formulating precise requirements. Not only is the design process iterative; the design-goal-setting process is itself iterative. Knowing complete product requirements up front is a quite rare exception, not the norm. Therefore, goal iteration must be considered an inherent part of the design process.
Embracing the mess
Design is non-linear. At Figma, we often talk about “embracing the mess,” and that really means leaning into the chaos and complexity that makes the design process what it is. Even once you have the seedling of an idea, you need to explore and iterate, then pull back and evaluate to see what’s working and what’s not. Sometimes you’ll scrap an idea after a brainstorm session, and other times you’ll get pretty far with a concept, but still need different perspectives and input to move forward.
Models and iterations
Every month or so, Manock and Oyama would present a new iteration based on Jobs's previous criticisms. The latest plaster model would be dramatically unveiled, and all the previous attempts would be lined up next to it. That not only helped them gauge the design's evolution, but it prevented Jobs from insisting that one of his suggestions had been ignored.
The surprising effectiveness of writing and rewriting
An Article by Matt Webb- The act of writing the first draft creates new “essential data” that feeds the imagination and makes possible figuring out the second draft.
- Or: In your head, ideas expand until they max out “working memory” – and it’s only be externalising them in the written word that you have capacity to iterate them.
- Or: Good writing necessarily takes multiple edits, and the act of writing and act of rewriting are sufficiently different that performing both simultaneously is like rubbing your tummy and patting your head.
Asynchronous Design Critique: Getting Feedback
An Article by Erin CasaliGetting feedback can be thought of as a form of design research. In the same way that we wouldn’t do any research without the right questions to get the insights that we need, the best way to ask for feedback is also to craft sharp questions.
Back to the Drawing Board
The lost art of drawing for engineers and architects.
- You can almost tell which software they were designed in
- Conversational drawing
- The effort heuristic
- Tablets have caught up
You can almost tell which software they were designed in
Tatiana von Preussen, cofounder of London practice vPPR Architects, says that certain software comes with constraints that encourage a particular style:
“Something I’ve noticed with new buildings is that you can almost tell which software they were designed in. For instance, if you take Revit, it’s very hard to freely create non-orthogonal, non-linear geometries, and it’s very easy to create repetitive elements, so it lends itself to a particular way of building.”
Conversational drawing
A skilled draughtsman guides design conversations by selecting and emphasizing details in a way that computer programmes cannot. Ron Slade, author of Sketching for Engineers and Architects and a structural director at WSP in London, calls it “conversational drawing”. He notes how botany field guides are always based on detailed drawings rather than photographs — as much for what they leave out as for what they show. “Extraneous material that might exist in a photograph is eliminated. It may be important to pick out and illustrate particular areas and leave other parts in sketchy or broad outline.”
The effort heuristic
Psychologists have noted that people tend to place greater artistic value on images when they can see the work that has gone into them — a tendency known as the “effort heuristic”. They are also more likely to connect emotionally with the work if they can detect the human hand, says Goldsmiths’ Chamberlain. “There’s an argument that if we see a brush stroke, we almost recreate it, and that’s part of the connection we feel with the artist — you can feel the intention.”
Perhaps to capitalize on this, some architects now show presentation drawings that look hand-drawn but are actually generated entirely by computer. “It’s totally fake,” says Brillhart. “They just take a computer image into Photoshop and put filters over it to make it look like it’s drawn by hand. It’s kind of amusing — instead of just sitting down and drawing for an hour, they spend eight hours making it look like a hand drawing.”
Tablets have caught up
But in the past couple of years, Brennan believes that tablets have caught up, with apps such as Apple’s ProCreate and Morpholio’s Trace becoming far more responsive to the user’s marks. “Tablets didn’t used to have that immediate response, from brain to eye to hand to pen to paper. A half-second delay has a huge impact on how you think — it causes you to stumble. But now that lag’s gone, it’s almost the same as drawing with pen on paper. You don’t need to engage with the airbrushes or other features — just use it in its purest form.” The stylus, too, far more convincingly apes a manual pen: “You’re able to tune it to almost replicate your favourite pen — and it doesn’t run out of ink.
Chetwood is an iPad devotee, using it to produce fantastical urban artworks as well as architecture. Far from hindering the drawing process, he believes tablets will give rise to a new era of creative drawing. “A lot of people say technology and computers are taking away the true art of drawing. That’s rubbish, it releases sketching. You can move so much quicker and change things much more quickly, and it keeps a record of what you’re doing. The control is just brilliant.” The polished glass surface is the only flaw, but textured acetates applied to the screen can make it feel more like paper.