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.
Gods of the Word
Imagine that we had no voice and no tongue
Socrates: Imagine that we have no voice and no tongue, but want to communicate with one another. Wouldn’t we like the deaf and the dumb make signs with the hands and the head and the rest of the body?
Hermogenes: There would be no choice, Socrates.
Socrates: We would imitate the nature of the thing: lifting the hands to heaven would mean lightness and upwardness. Heaviness and downwardness would be expressed by letting them drop toward the ground...
Hermogenes: I don’t see that we could do anything else.
Socrates: And when we want to express ourselves with the voice or tongue or mouth, the expression is simply their imitation of what we want to express?
Hermogenes: I think, it must be so.My name
“I am the utterance of my name.”
— Thunder, Perfect Mind, The Nag Hammadi Library
Reference and Is-ness
There are at least two aspects to what we have traditionally called the meaning of a word. One aspect is reference, and the other is something I will call ‘inherent meaning’ following Ullman (1963). Inherent meaning is ‘Is-ness’ meaning. Inherent meaning is a word’s identity, and reference merely its resumé, where it has gone and what it has done, an itemization of its contexts. ‘Is-ness’ is unifying. Each word has a single pronunciation, a single inherent meaning. But reference is divisive. It makes what was one thing – the word – appear to be many things – its senses. It is inherent meaning which gives all those multifarious senses the power of being a single word.
It flows out and fills
This deeper meaning of a word isn’t confined to what we think of as a dictionary definition. Rather it flows out and fills all the space available to it. Although a basic sense does affect the dynamics of a word, it has no power over its essence. Like the captain of a ship, it can control the crew’s actions, but not their minds. Each word has an aspect of meaning which lies deeper than any of its senses, and it is fundamentally on this meaning that all the senses depend.
No less than a Zeus
I too am a true believer in the autonomy of the archetype. A
/t/
or an/h/
is no less than a Zeus. The consonants are not essentially physical, but they live, evolve and influence human affairs. We overlook something essential if we deny that they can get up and walk around. This is not to say that their existence is independent of the human psyche. But then everything depends on everything.Like a prism
When you look at phonemes, you look through the perspective of morphemes, which are one linguistic level higher. The higher level is like a prism that splits the light in two. What was one thing, like ‘length’ at the phoneme level, looks like two opposite things ‘long’ and ‘short’ from the perspective of the morphemes. In practice, when you find both a word and its opposite, then the phoneme is not about either of these two things, but about what is common to them.
Fracturing
If we step back and view from afar this process of One-ness and Is-ness to fracturing and interpretation – of inherent meaning to reference, it follows that what lies at the foundation of language is simply what it is – sound – free of reference and interpretation. What makes what we know as language from its sound is fracturing and interpretation or using a word for a function other than what it simply is.
To evolve the language itself
So in the process of talking, we might say we are putting words in slightly new contexts, and then testing them against our peers to see if our experiment in juxtaposition had ‘meaning. If we succeed, we have introduced new contexts for the words we use. These contexts will be taken up by our listeners, and will gradually become clearly enough defined to be thought of as referents. Once our words gain new referents, they start affecting the underlying phonosemantic structure of the language, the clustering patterns, the network of semantic relations. That is, the purpose of talking in the long run is to evolve the language itself.
Scooting over
There is at this point no evidence that acquired characteristics can be inherited. It is held that all changes to a genome are random, and cannot be subject to any higher principle. However, when a word is used in a new context, as it is whenever we say something new, a new sense is permitted. This does affect the phonosemantic structure, the linguistic DNA. Words in the vicinity of this word ‘scoot over’ to make room and allow themselves to be influenced by its philosophy. The language itself is now different.
The element becomes a sign
Each unit can be seen purely as form, as what it is. Or it can be viewed as having a function. Its function is only understandable within the next higher level of organization. And in every case, function must succumb to the constraints of form. Once this worldly function is assigned, the element becomes a ‘sign’. It falls into the realm of concept. There is a mapping from one thought system to another.
The demand of a new word
Why are these phonosemantic classes enough, and we need neither more nor less? Why are these consonants enough, and we need neither more nor less? What determines the need for a new word? How is this demand ‘felt’ by a language? How did the metabolic pathways of American English recognize that ‘jerk’ and ‘twerp’ and ‘punk’ and ‘nitwit’ and ‘dork’ and ‘ass’ and ‘goon’ and ‘twit’ and ‘dodo’ and ‘bum’ and ‘nerd’ and ‘dunce’ and ‘turd’ and ‘boob’ and ‘chump’ and ‘bitch’ and ‘bastard’ and ‘prude’ and so on and so forth simply were not equal to the task? We had to add ‘turkey’ and ‘squirrel’ as well?