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
Infrastructure: A Guide to the Industrial Landscape
Savage, hostile, and cruel
Some may find puzzling or distasteful the parallel I am drawing between the study of nature and the study of technology. After all, nature is good and good for you, whereas everyone knows that technology is ugly, evil, and dangerous.
A few centuries ago—say, on the American western frontier—a quite different view prevailed. Nature was seen as savage, hostile, cruel. Mountains and forests were barriers, not refuges. The lights of civilization were a comforting sight. We took our charter from the book of Genesis, which grants mankind dominion over the beasts, and felt it was both our entitlement and our duty to tame the wilderness, fell the trees, plow the land, and dam the rivers.
Nature undisturbed
My chief aim is simply to describe and explain the technological fabric of society, not to judge whether it is good or bad, beautiful or ugly. And yet I would not argue that technology is neutral or value-free. Quite the contrary: I suggest that the signs of human presence are the only elements of the landscape that have and moral or aesthetic significance at all. In nature undisturbed, a desert is not better or worse than a forest or a swamp; there is simply no scale on which to rank such things unless it is a human scale of utility or beauty. Only when people intervene in nature is there any question of right or wrong, better or worse.
The raw materials of society
A big hole in the ground: This is where most of the raw materials of an industrial society come from. To appreciate the scale of this excavation, note that the bright blue object on a shelf near the center of the image is a Porta Potti.
The dragline
A dragline is the largest of the machines used to strip away the overburden and mine the ore layer at an open-cast mine. A bucketload for this particular dragline, one of the world's largest, is 220 cubic yards. Note the school bus, which would easily fit in the bucket.
Dark satanic steel
When poet William Blake wrote of "dark satanic mills", he couldn't have been looking at a steel mill because there were none in 1804. Nevertheless, when I visit a steel mill, Blake's phrase always comes to mind. With the heat and the pounding noise, the dust and smoke, and the red glow against the night sky, it's hard not to see these places as infernal. And yet the process of making steel also produces some of the most hauntingly beautiful images found anywhere in the world of industry.
Strength from both mass and form
Hoover Dam has the shape of an arch dam, but it is actually a hybrid structure, gathering strength from both mass and form. The dam is often ranked as one of the most exquisite of all engineered structures. It is fitted to its site so well that the gnarly canyon wall looks like an organic growth engulfing the mass of concrete.
Warmed by the afternoon sun
Textbooks on water-system engineering state that supply mains are generally installed on the north side of the street in the Northern Hemisphere and on the south side in the Southern Hemisphere, so that the sun will warm them. In both hemispheres they are supposed to be on the east side of north-south streets, on the premise that the afternoon sun is warmer than the morning sun.
Trompe l'oeil fantasies
In residential neighborhoods some sewage-pumping stations are trompe l'oeil fantasies, dressed up to look like the split-level or colonial houses that surround them. If you look closely, it's not hard to spot these disguised pumphouses: the heavy-duty power connections, the big ventilating fans, and the diesel generator in the backyard are all tip-offs. Furthermore, the windows are often fakes, with sash and shutters adorning a blank wall.
Quaker Square Inn
The modernist architect Le Corbusier was an admirer of American grain elevators, suggesting that their regularity and modularity could serve as a model for other kinds of buildings. At least one later architect took the suggestion seriously. The Quaker Square Inn in Akron, Ohio, occupies the shell of a former elevator. If you're in town for the night, you can rent a round room in one of the silos.
A metropolis for hydrocarbons
An oil refinery suggests the image of a metropolis for hydrocarbons, the pipe manifolds like expressways, the distillation towers like skyscrapers.
A haunting, syncopated music
"Rappers" on the roof of the electrostatic precipitator knock the accumulated dust free, letting it fall into the storage hopper. Each rapper is the size and shape of a baseball bat. Inside is an electromagnet that pulls a steel plunger upward, then allows it to fall again, producing a sharp knock. The rappers are energized at seemingly random intervals, producing a haunting, syncopated music. (The rhythm seemed more modern jazz than rap.)
Safety cut rope axe man
In the first nuclear reactor, constructed by Enrico Fermi in 1942 under the bleachers of the University of Chicago football stadium, the control rods were held up by a manila rope. A man with an axe was told to cut the rope if the reactor got out of hand. This "safety cut rope axe man" is supposedly the origin of the term SCRAM for an emergency shutdown procedure.
Pylons
Not all the towers along a transmission line are identical. Look closely at a tower where the line makes a sharp turn and you will likely find it is wider and beefier than other towers along the route. The added strength and weight are needed to resist the unbalanced pull of the conductors, which might overturn an ordinary tower. These special towers are called deviation or angle towers.
The transmission-line tower everybody knows is an Erector Set latticework of steel girders and diagonal braces. The techniques for designing and building these towers are the same ones used in constructing steel bridge trusses or crane booms. The individual pieces can be made cheaply from rolled steel and then bolted together on the site. This last point is more important than it might seem: transporting a fully assembled tower 100 feet tall is an awkward and expensive business.
Color coding
Telephone wires erupt in a multicolor cascade in a ground-level, pedestal-type splice case on a city street.
Dividing the set of 10 colors into two contrasting groups of 5 allows for exactly 25 combinations with one color from each group; thus, each pair in a bundle can be uniquely colored. A similar color code is applied to the ribbons that bind together all the pairs in a bundle, and to those of the superbundles. The result is highly festive! A specific wire might be identified as the blue-red conductor within the orange-black bundle within the brown-yellow superbundle.
The Iridium System
Several Low-Earth-Orbit (LEO) networks were proposed, but only one got off the ground: the Iridium system. The original Iridium proposal called for a "constellation" of 77 satellites, which gave the plan its name: the element iridium has atomic number 77, meaning that an iridium atom has 77 orbiting electrons. Before the satellites were launched, the constellation was scaled back to 66 active satellites, but no one wanted to change the name to Dysprosium.
Roads to nowhere
Among real-estate developers, straight lines and right angles went out of fashion sometime in the middle of the twentieth century. If you look at a town or a residential neighborhood laid out since then, you are more likely to find sinuous, serpentine roads—whether or not the topography offers any excuse for such curves. Many of these roads go nowhere: they are loops that bring you back to where you started, or they are cul-de-sacs. Making it easy to find your way through the network of streets is obviously not a high priority. This is an interesting development in urban geography: having redesigned the city to accommodate the automobile, we now search for ways to discourage people from driving on the streets.
A gradual refinement
The steel rail is an artifact whose form has been carefully optimized. This gradual refinement of the design was done not by a single brilliant engineer but by more than a century of industrial evolution. The rail was never meant to be an object of beauty, but its cross section has all the elegance of fine typography.
Hyperart: U.S. Rail
The steepest grade on U.S. main-line track is at the small town of Saluda, on a Norfolk Southern route between Spartanburg, South Carolina, and Asheville, North Carolina. The grade goes on for three miles at a slope of 4 or 5 percent. Trains have not been running on the line since 2001, but the tracks are still maintained.
An emblem of friendship
Bridges make connections; they bring people together—a role that has made them a traditional emblem of friendship. Consider the town of Mostar in Bosnia-Herzegovina. When fighting between ethnic factions broke out there in the 1990s, nothing symbolized the social disintegration more clearly than the destruction of a sixteenth-century stone-arch bridge that had linked the two parts of the town on opposite banks of the Neretva River. And the emblem of efforts to heal the divisions is a rebuilt bridge, opened with fireworks and fanfare in July of 2004.
Routine design
When we think of bridges, it is the dramatic and monumental long spans that come to mind first, especially the lithe suspension bridges such as the Golden Gate and the pure geometric arches such as Sydney Harbour. But the majority of bridges are not such spectacular structures. Most of them are ordinary overpasses, with spans of 30 or 40 feet, carrying roadways or rails across other thoroughfares or over small streams. You see such bridges by the dozen on any drive down the Interstate. They may be lacking in glamour, but they are more representative of a bridge builder's art.
The engineering and construction of girder bridges are pretty routine these days, but the bridges are not quite standard items you order from a catalogue. The girders, whether of steel or concrete, are custom-build for each bridge, then trucked to the site and hoisted into place with a crane. The designer still has scope for variation and creativity, and it shows out on the highways: some overpasses are prettier than others.
No Smoking
What's that big electrical cord that also connects the ship to the dock? It's not a power cord to run machinery aboard ship; it's a grounding strap, to prevent sparks from static electricity. Something else you're sure to notice on a tanker is a big warning sign about the fire hazard. Frederick Allen, the editor of American Heritage of Invention & Technology, has remarked that all tankers seem to be named No Smoking.
Port furniture
All the miscellaneous fittings and fixtures on wharves and piers and elsewhere in nautical neighborhoods are known by the charming term port furniture.
The mirror-image economy
When we enter the world of refuse and waste, we cross over into a mirror-image economy. In the "normal" world, we pay to acquire things; on the other side of the looking glass, we pay to get rid of them. Junk isn't merely worthless; it has negative value.
A chemical engineer once told me about a recent improvement in a manufacturing process; by fine-tuning a chemical synthesis he had increased the yield of a certain commodity from 98 percent to 99 percent. I congratulated him, but I couldn't help remarking that this seemed like a rather paltry improvement. "Ah, you miss the important point," he said. "The amount of waste goes from 2 percent down to 1 percent. It's cut in half. We save tremendously on disposal costs."
NIMBY, BANANA, NOPE
Waste-disposal facilities of all kinds—landfills, incinerators, even transfer stations—are sure bets for generating the NIMBY response: not in my backyard. In its most cynical form, NIMBY is the attitude of citizens who acknowledge the need for a facility, somewhere, but who oppose a plan for building it simply because the selected site is too close to their own property. But opposition to landfills and many other kinds of development goes well beyond cynical NIMBY. Another catch phrase for this phenomenon is BANANA: build absolutely nothing anywhere near anybody. Or else it's NOPE: not on planet earth.
Creations of human artifice
In the twenty-first century, the question most of us ask when disaster strikes is not "How could God let that happen?" but "Who screwed up?" This is a salutary development: We take responsibility for the world we live in. Whether or not our world is the best of all possible worlds, it is a world we have made for ourselves. We live in an engineered landscape, on an engineered planet. Our cities and farms, our dwellings and vehicles, our power plans and communication networks—these are all creations of human artifice. If we don't like it here, we have only ourselves to blame.
What kind of world it's going to be
The wonderful thing about living in a world of our own creation is that we get to choose what kind of world it's going to be—at least in principle. But the promise is meaningful only if a broad enough "we" can be engaged in the process. At present, mechanisms and democratic institutions for making collective decisions about the deployment of technology are hopelessly cumbersome. How can anyone make a sensible choice without being able to weigh one alternative against another?