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.
Cubed
A dry, husky business
Despite the furor over their aggressive unmanliness, clerks, and with them the office, crept silently into the world of nineteenth-century America. Moral philosophers were mostly preoccupied with the clang of industrialization and its satanic mills, and most regarded as negligible the barely audible scratch of pens across ledgers and receipts that characterized the new world of clerical work. It was only a “dry, husky business,” as the narrator of Bartleby had it.
A segment of the enormous file
As office buildings grew taller, and flammability became a problem, steel file cabinets replaced wooden ones – the tall cabinets mimicking the shape of the skyscraper, such that the “file” seemed to be a metaphorical stand-in for the office itself. “Each office within the skyscraper,” C. Wright Mills would argue some years later, “is a segment of the enormous file, a part of the symbolic factory that produces the billion slips of paper that gear modern society into its daily shape.” Aldous Huxley, in his dystopian novel Brave New World, could imagine no more powerful symbol of a totally bureaucratized world than the idea of each person having his or her name on a file.
Taylorism
“In the past the man has been first. In the future the system must be first.” — Fred W. Taylor
Taylorism was a way of thinking that came at the expense of the workers’ own knowledge of their system. Taylor summed up his philosophy thus:
“It is only through enforced standardization of methods, enforced adoption of the best implements and working conditions, and enforced cooperation that this faster work can be assured. And the duty of enforcing the adoption of standard and enforcing this cooperation rests with the management alone.”
The unscripted practices of the old offices would remain, but as a kind of subterfuge: in the future, a leisurely pace wouldn’t be the norm; time would not be given, but stolen.
Divided against itself
By separating knowledge from the basic work process (“the separation of conception from execution,” as Harry Braverman once put it), in the factory as well as the office, the ideology of Taylorism all but ensured a workplace divided against itself, both in space and in practice, with a group of managers controlling how work was done and their workers merely performing that work.
Somewhat more dangerously, this division put into serious doubt the notion that office workers were, as a whole, on the way up. It became increasingly clear from the shape of the offices themselves, and from the distance between the top and the bottom rungs of the “ladder”, that some workers were never going to join the upper layers of management. For some, work was always, frankly, going to suck.
Form follows finance
The formula that Sullivan coined to explain this individualist-conformist principle has become a commonplace of architectural history: “Form follows function.” The envelope of the building was to reflect no particular style, no empty ideal, but rather, with as pure a transparency as possible, the shape and feel of the interior. It was the office that determined the skyscraper – a fact that might have had a beneficial effect on the form of the office itself.
But the result was the opposite: few conceptions of the office have had a more deleterious effect on the human work environment. The title of an influential work by the architectural historian Carol Willis gives us a better, if less palatable, explanation: Form follows Finance. For by and large, making an office “functional” had less to do with making it serve the needs of a particular corporation and much more with serving any corporation. The point was not to make an office building per specification of a given company, but rather to build for an economy in which an organization could move in and out of a space without any difficulty. The space had to be eminently rentable.
Serendipity
This was not meant to be like Bell Labs; there were no expectations that the clerical workers would run into their managers in a “serendipitous encounter” and produce a new innovation. The ideas was rather to create a workplace in which status barriers seemed to dissolve, in which participation and friendliness all around made the work environment look less like the white-collar factory it was.
Office survival
“The caveman was undoubtedly very pleased to find a good cave but he also undoubtedly positioned himself at the entrance looking out. Protect your back but know what is going on outside is a very good rule for survival. It is also a good survival rule for life in offices.” — Robert Propst, The Office: A Facility Based on Chicago
The office landscape
An organic, almost forest-like office layout.
There is an affinity with certain planned “landscapes” of the natural world – namely, the classic Italian Baroque garden. In the sample plans the Schnelle brothers devised, the arrangement of desks seems utterly chaotic, totally unplanned – a mess, like a forest of refrigerator magnets. But, as with the seemingly “wild” overgrowth of a “natural” garden, the office landscape is more thoroughly planned than any symmetrical and orderly arrangement of desks. Imaginary lines wend their way around every cluster, delineating common pools of activity; between and through the undergrowth of clusters are invisible, sinuous paths of work flow.
Open-plan the world
In the end, noise would always be a problem, when quiet was not placed at a premium. Interaction and communication were conceived of as norms in the landscaped office; introspection and concentration were sidelines. In the rush to open-plan the world, some crucial values for the performance of work were lost.
The cubicle
The cubicle had the effect of putting people close enough to each other to create serious social annoyances, but dividing them so that they didn’t actually feel that they were working together. It had all the hazards of privacy and sociability but the benefits of neither. It got so bad that nobody wanted them taken away; even those three walls offered some kind of psychological home, a place one could call one’s own. All these factors could deepen the frenzied solitude of an office worker.
Chilled-out anxiety
Working in the typical dot-com office was an admixture of frenetic pace and a relaxed overall atmosphere, exemplifying that chilled-out anxiety which was the general mood of the 1990’s.
A resource
The office, Chiat argued, had become the site of a turf war, not a place to do work. Changing the office “means focusing on doing great work instead of focusing on agency politics,” he argued. “You come to work because the office is a resource.”