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
My Life as an Architect in Tokyo
World renowned architect Kengo Kuma presents an enlightening tour of Tokyo, expressing his personal thoughts and reflections on the city's most influential buildings and its rich architectural heritage.
A collection of villages
I became a 'border person', as defined by the sociologist and philosopher Max Weber, viewing Tokyo from an outsider's perspective. Observing the city while walking around its streets enabled me to discover a wide variety of location, cultures and people, and that Tokyo is a collection of small villages, rather than one big city.
...When I design a building in any city, I believe that the world is a collection of villages, instead of a group of nations.
Low wooden silhouettes
While [Kenzo] Tange aspired to verticality, we looked to horizontality, believing that pre-1964 Tokyo, with its low wooden silhouettes, was a better model for the city of the future.
Occupied by a void
Roland Barthes wrote that the centre of Tokyo is occupied by a void...it is a quiet forest that lies at Tokyo's heart.
...The centre of Tokyo is certainly a void, but one that is protected by a circular train line, the Yamanote, which forms a 40-km (25-mile) loop around it. It seems to me that this ring of steel emphasizes the importance of the void, and the depth of its significance.
Such an enormous machine
In cities across the world, industrial zones beside rivers and canals have become the focus of attention, with their unique vivacity associated with places where things are made.
...Because the area is designated as a semi-industrial zone, we were able to get away with such an enormous machine inside [the Starbucks Reserve Roastery].
A more spiritual place
In the centre of the forest is the sandō, leading up to the shrine. It follows an L-shaped curve, and is very different to the straight processional pathways found in religious buildings in the West or in China. Curves ensure that the view changes constantly, helping visitors make the transition to a deeper, more spiritual place.
The building as less important than the path
In the design of Japanese tea houses, the building is seen as less important than the path (roji) leading up to it, and tea masters of the past believed that the journey along the roji allowed participants to better immerse themselves in the slow time of the tea ceremony.
The gentle light of shoji screens
Le Corbusier, the greatest architect of the last century, noted that 'architecture is the learned game, correct and magnificent, of forms assembled in light', demonstrating to what extent light has been prioritized in the Western tradition. Tanizaki, on the other hand, spoke of the important of shadows, of extended eaves. Rather than the light that shines directly into a room, he praised the soft light that penetrates a space after being reflected off the floor, and again from the ceiling.
...In Japanese architecture, the gentle light that passes through shoji screens serves a key purpose. It reaches right to the back of the room, so that the space feels bright, even without the aid of artificial light. The soft light filtering through the white film at Takanawa Gateway Station represents a form of light that was forgotten about by Japanese Modernism.
The thin lip of a teacup
To give the building a sense of the delicacy associated with such crafts, as well as a feeling of warmth, I designed louvres from white porcelain panels, and used them to cover the outer walls. The louvres are tapered, to make their tips as fine as possible. (In fact, making tips as thin as possible is one of my key design principles: the thin lip of a teacup allows a better experience of the subtleties of tea - this is always at the forefront of my mind when I pay such close attention to edges.)
Skyscrapers are frowned upon
During the twentieth century, much importance was attached to things that were big and tall, but, as we moved into the twenty-first century, I felt that being big and tall had become embarrassing.
...Today, skyscrapers are frowned upon in Japan, and are seen as the product of the mistaken mindset that prevailed during the country is period of enhanced growth.
The Metabolist philosophy
Tange put Tsukiji as the centre of his plan, which now seems grandiose and delusional. His design for the Dentsu building had much in common with the Metabolist philosophy of the 1960s, which maintained that buildings needed to continually evolve in a flexible way.
...With [the Nakagin Capture Tower], Kurokawa's Metabolist philosophy was fully realized. After it was completed, however, it became almost impossible to switch over the capsules - indeed, since its completion, not one of the capsules has been moved. As a result, the Metabolist movement has been forgotten. Yet its core principles, which sought to draw architectural lessons from living organisms, has much inspiration to offer society today.
A city of hills
Many of the stations [on the Yamanote Line] have one entrance on the uphill side and another lower down, and the neighbourhoods around them have a totally different feel, depending on which exit you use to leave the station.
The hilly areas in Tokyo are mostly made up of quiet, well-to-do residential districts, while the lower sections often have more of a populist feel, with shopping arcades and small urban factories. As a result, the atmosphere outside the entrances are dramatically different in character. Take the wrong exit, and you might find yourself lost in a completely different kind of neighbourhood than you were expecting. In Tokyo, elite and working-class cultures exist alongside one another and mix together. I think the fundamental cause of this is the complexity of the city's topography.
...Tokyo is a city of hills, with most of it lying on an alluvial plain between the Tama and Kanda rivers. It is via these hills that the upland, elite neighbourhoods are connected with the more working-class areas down below. The slopes are thus a key part of the co-existence of these two worlds, used by people to come and go between them. Kagurazaka is particularly notable in this respect.
They can smell the wood
All of the wooden shelves used for storing books were on the warehouse's first floor. We decided to keep these shelves as they were to form a library, and we also created a small lecture hall for holding talks by writers and makers. Although contemporary society is moving away from books and towards computers and information technology, people nevertheless have a strong feeling of connection to – and nostalgia for – trees and things that are made from wood. La kagu is a space where visitors can really get a sense of the culture of books. When they step inside, some even say that they can smell wood.
As a kind of gateway
Historically, Japan's shrines have been built in order to worship the gods who live in the sacred mountains or seas; They don't reside in the shrine itself, but in the space beyond it. This belief that the spirits and deities exist beyond the confines of the shrine, and that the shrine itself acts not as a centre, but as a kind of gateway, is very different to the grand, imposing churches and cathedrals of Christianity.
The majority of shrines are not found in the mountains or in the middle of the fields, therefore, but at the borders of mountain villages – which is to say, at what is seen as the edge of the mountains. The tori gate, marking the entrance to a shrine, indicates that there are gods on the other side of it.
The golden poo
On the opposite bank of the Sumida River lies the Asahi Beer headquarters (1989), a strange building with a golden sculpture mounted on top of a granite-plated black box. It was designed by Philippe Starck, and completed in 198g when the Japanese economy was still going strong. The sculpture, with no clearly defined use, is a clear representation of its time. Today, the building is known as the 'golden poo', a reference to the shape of its crowning object.
Like crossing the sea
The Sumida is a symbol of Tokyo, but is not like the Thames in London or the Seine in Paris, or other rivers that are woven into the geography of the city. Its banks were pushed back, so that the river became extremely wide and travelling across it feels liberating, like crossing the sea.
These thrown-away items
I decided to furnish the restaurant [Tetchan] with the kinds of discarded items one wouldn't normally use in interior design, from recycled LAN cables to acrylic by-products.
When using discarded objects in interior design, it gives even brand-new places the feeling that they have always been there. I think this is due to the inherent history of these thrown-away items, which lives on inside of them.
Kengo Kuma's sketches