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
Understanding Understanding
A dot went for a walk
A dot went for a walk and turned into a line.
The dot, the line, the dance, the story, and the painting had found connections. Memory became learning, learning became understanding.Learning is remembering what one is interested in. Learning, interest, and memory are the tango of understanding.
Creating a map of meaning between data and understanding is the transformation of big data into big understanding.
The dot had embraced understanding.
Understanding precedes action.
Each of us is a dot on a journey.Admitting ignorance
The most essential prerequisite to understanding is to be able to admit when you don't know something. Striving to be the dumbest person in the room.
When you don’t have to filter your inquisitiveness through a smoke screen of intellectual posturing, you can genuinely receive or listen to new information. If you are always trying to disguise your ignorance of a subject, you will be distracted from understanding it.
Information imposters
Information imposters: This is nonsense that masquerades as information because it is postured in the form of information. We automatically give a certain weight to data based on the form in which it is delivered to us. Because we don’t take the time to question this, we assume that we have received some information.
My favorite example of this is in cookbook recipes that call for you to “cook until done.” This doesn’t tell you very much. Why bother? Information imposters are fodder for administravitis.
Michaelangelo's hammer
A young man named Michelangelo stands in front of a huge granite monolith. He stands there at a time in history before the technologies that brought us the hammer and chisel have occurred. He gazes at the rock. He dreams his dream and the best that he is able to say is, What a wonderful stone you are.
…
Michaelangelo now stands in front of the same rock. Thrust into his hands are a hammer in one and a chisel in the other. He looks at his hands, at the technological tools that they hold, and gazing at the same stone, with epiphanic zeal, says I must let Moses out.
I won't get
If I don't ask, I won't get.
Talking with Clinton
When you are talking with Clinton, he is not looking over your shoulder to see who else is in the room. You can tell he is not thinking about how he is going to respond to you. He is there, present and listening.
By the way, when you scramble the letters in the word listen, it becomes a new word: silent. We’re so often wrapped up in our own self-talk, we forget to listen and learn the information in the first place…and you can’t remember or understand something you never observed.
Scales of change
To understand revolutionary change in its full complexity – not just what happened, but why it happened – we need a model that works across multiple scales, and the disciplines that traverse them.
The method
Well no, see, that’s the tricky part. I always try to come up with things that when they find out the method, the method is as interesting as the effect itself. — David Blaine
Selling your own ignorance
When you sell your expertise - and what I mean by sell is to move ahead in a corporation, or sell an idea to a publisher, or sell an ability to a client - by definition, you’re selling from a limited repertoire.
However, when you sell your ignorance to move ahead, when you sell your desire to create and explore and navigate paths to knowledge, when you sell your curiosity - you sell from a bucket with an infinitely deep bottom that represents an unlimited repertoire. And, you sell in a way that’s not intimidating, in a way that joins the explanation to the fascination that comes with understanding.
You only understand something relative to something you already understand
A good question is better than a brilliant answer
The eyes of a traveler
We’ve all heard that travel broadens the mind. But beneath this cliché lies a deep truth. Things stand out because they’re different, so we notice every detail, from street signs to mailboxes to two you pay at a restaurant. We learn a lot when we travel, not because we are any smarter on the road but because we pay such close attention. On a trip, we become our own version of Sherlock Holmes, intensely observing the environment around us. We are continuously trying to figure out a world that is foreign and new.
Too often, we go through our day-to-day life on cruise control, oblivious to huge swaths of our surroundings. To notice friction points – and therefore opportunities to do things better – it helps to see the world with fresh eyes. When you meet creative people with lots of ideas constantly bubbling to the surface, you often come away feeling that they are operating on a different frequency. And they are, most of the time. They have all their receptors on — and frequently turned up to eleven. But the fact is, we are all capable of this mode. Try to engage a beginner’s mind. For kids, everything is novel, so they ask lots of questions, and look at the world wide-eyed, soaking it all in. Everywhere they turn, they tend to think, Isn’t that interesting? rather than, I already know that.
By adopting the eyes of a traveler and a beginner’s mindset, you will notice a lot of details that you might normally have overlook. You put aside assumptions and are fully immersed in the world around you. In this receptive mode, you’re ready to start actively searching out inspiration.
Cart before the horse
It seemed to him that in pursuit of an all-purpose, all-serving health care plan, the country was designing an ocean liner before it even understood why boats float.
The What and the How
How many aspects of problem solving and design solutions are there? Many, many might answer.
But there are actually just two: What to do and how to do it.
Before anything else, before you consider how you’re going to get it done or how much you’ll have to pay for it or how you’ll get permission to do it — before anything else, you have to decide what you want. You have to decide what kind of place you want to live in, what kind of community, what kind of city.
We don’t pay enough attention to the old adage: Be careful what you wish for, because you just may get it.
Thinking with the hand
The idea of thinking with your hands is not the exclusive domain of sculptors or engineers. In healthcare, for exams, surgeons have a powerful link between the head and the hands. Of course, like all healthcare professionals, their work involves a lot of deep knowledge and understanding. But it’s not all in their brain. If you were in medical school, learning to be a surgeon, for example, would you want your professor to be someone who writes about surgery or would you rather be taught by a surgeon? Many surgeons don’t publish scholarly articles. They spent time perfecting their skill with their hands. In some ways, the relationship between surgery and the larger field of medicine is analogous to the relationship between design and the larger field of engineering. Designers — and design thinkers —often think with their hands.
A pattern of understandings
The clock has no finished design and it has been made without any careful drawings or mathematical calculations. The pieces are only made if I can hold their details in my head as I make them, without reference to any set of external measures. I do make rough sketches of some parts as a path to understanding them, but never use these during the making of the parts. The clock gradually grows through trial and error and lots of physical work with metal, but out of this has come a set of principles of making that were not clear to me before doing the clock. I have finally realized that what I am actually making is a pattern of understandings of the process of making rather than the things that are actually being made. — Richard Benson
#15
How different am I, making clock number 15, from the process of natural selection laboring under changing conditions to generate the biological constructs? That ancient evolutionary system works on the basis of trial and error repeated in huge numbers over immense spans of time, with the failures discarded and the successes retained. At times it seems to me that my clock making is quite similar, as my mind, just barely thinking, sorts through huge numbers of possibilities and discards them as failures before even trying them, so the few that are made have a pretty good chance of success. Is this foresight some form of understanding? I think not. No revelation here, just enough thinking to spur the maker on to cut some piece of metal which, once made, might fail or succeed. Yet — in either case — the thing made and its creation remains the sole root of any real understanding that takes place. The clock is crude but gets built, and even in its base simplicity teaches its maker how to understand what must be understood for something to be made. — Richard Benson
A classroom without walls
The city is education – and the architecture of education rarely has much to do with the building of schools. The city is a schoolhouse, and its ground floor is both bulletin board and library. The graffiti of the city are its window displays announcing themselves, telling about what they’re doing and why and where they’re doing it. Everything we do – if described, made clear, and made observable – is education: the Show and Tell, the city itself. It is a classroom without walls, an open university for people of all ages offering a boundless curriculum with unlimited expertise. If we can make our urban environment comprehensible and observable, we will have created classrooms with endless windows on the world.