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.
What Good Means
The center of the way
The advice I’ve received from those who are close to the center of this timeless way of building is to start small. Like with a piece of tile, or a tea tray. And to then imagine along with Christopher Alexander:
What it would be like
to live in a mental world
where one’s reasons
for making something
functionally
and one’s reasons
for making something
a certain shape,
or in a certain
ornamental way
are coming
from precisely
the same place
in you
.Seduction
“The classic pervasive seduction to designers is finding a solution instead of the truth.” — Richard Saul Wurman
What the material wants to be
Part of how Lou Kahn made things be good was to ask the material what it wanted to do and be. He asked brick what it liked, and would get a different answer depending on the context for the building. In Dacca, the capital of Bangladesh, brick said it liked an arch. For the Korman House in Philadelphia, brick said it liked two giant fireplaces with a lintel between them for a doorway beneath and a balcony above.
Asking yourself some questions
All of the moves that we make in space will tend toward being in accord with this phenomenon of wholeness / beauty / life if we’re willing to bring the requisite level of care to the doing of our work.
Alexander says that each of us possess the means for accessing this order within ourselves and — here’s where he loses most other architects and many in the so-called sciences in academia — he contends that what we’re connecting with inside of ourselves is an objective criterion for what good means.
Applying the criterion is easy: you ask yourself some questions:
With any action you might take with regard to placement, and with regard to the situatedness of things in space you ask yourself: does this move increase wholeness / beauty / life?
Does the intervention you’re taking intensify the feelings of wholeness in you as the maker when you are performing the work?
How does your work on this one part enhance what’s going on among wholes at the system level?
Losing meaning
The people who’ve proven that they can make very good individual products with the radical focus of a spotlight seem to be pushed ever further from making good ecosystems.
Products are being made “consistent” with the application of so-called “design patterns,” and rather than bringing coherence to these various touch-points, the painting-on of interface standards and interaction patterns did something far less valuable.
Rote consistency, in the way many seem to be going about it (Material Design being just one example), is at odds with making things be good. It simplifies what needs to remain complex.
Always, when simplification is underway, meaning is being lost.
Two coffee trays
We speculate that the shop owners designed and built an initial quantity of these remarkable coffee trays, replete with what Alexander considers to be the fifteen geometric properties that correlate with wholeness / beauty / life.
Then they got busy. And then they got successful. They needed more coffee trays, and our hypothesis is that somebody decided to simplify the trays to ensure they could be produced in the quantities and at the price that worked for their budget, within an urgent food-service timeline.
The simplified tray fulfills every function the more complex tray does, with less fuss in manufacturing on account of having standardized its geometry. The simplified tray works, but isn’t alive. It lacks the gradients, local symmetries, levels of scale, contrast, and boundaries that are all present and accounted for in the tray that’s got wholeness / beauty / life. The tray with wholeness isn’t necessarily better than the simpler one. But it is good.