collaboration
It passes by the river
Business people and developers
Engineering, design, and product management
The problem with CAD
We want you to work with an artist
The power of One
picnic.lectoro.me
Designer + Developer Workflow
An Article by Dan MallThe way designers and developers work together today is broken. It’s too siloed and separate; “collaboration” is a fantasy that few enjoy.
The state of advertising in the 1940s was similar. All of that changed when copywriter Bill Bernbach met art director Paul Rand. Their collaborative working style led to the birth of the idea of “the creative team,” the mutual respect and partnership between art director and copywriter that tended to yield unique results. Bob Gage, an art director that worked for DDB, the agency Bernbach co-founded, described it like this:
“Two people who respect each other sit in the same room for a length of time and arrive at a state of free association, where the mention of one idea will lead to another idea, then to another. The art director might suggest a headline, the writer a visual. The entire ad is conceived as a whole, in a kind of ping pong between disciplines.”
Isn’t that what we all strive for in our jobs? True collaboration with equals and partners? Ideas that build off one another? Why does this seem so far away for some of us?
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.
Nobody gives a hoot about groupthink
An Article by Baldur BjarnasonTwo relatively common ‘fashions’ today are real-time collaboration and shared data repositories of one kind or another.
Both increase productivity in the naive sense. We work more; everybody is more active; the group feels more cohesive.
The downside is that they also both tend to reduce the quality of the work and increase busywork.
Pair Design: Better Together
Pair design is the counterintuitive practice of getting more and better UX design done by putting two designers together as thought partners to solve design problems. It’s counterintuitive because you might expect that you could split them up to work in parallel to get double the design done, but for many situations, you’d be wrong. This document will help explain what pair design is, how it works, and tour through the practicalities of implementing it in your practice.
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.
When we were all together in-person
A Quote“We believe that in-person collaboration is essential to our culture and our future,” said Deirdre O’Brien, senior vice president of retail and people, in a video recording viewed by The Verge. “If we take a moment to reflect on our unbelievable product launches this past year, the products and the launch execution were built upon the base of years of work that we did when we were all together in-person.”
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 Small Group
An Article by James MulhollandLying somewhere between a club and a loosely defined set of friends, the SMALL GROUP is a repeated theme in the lives of the successful. Benjamin Franklin had the Junto Club, Tolkien and C.S. Lewis had The Inklings, Jobs and Wozniak had Homebrew.
Around a dozen members is the sweet spot of social motivation: small enough to know everyone, yet large enough that the group won’t collapse if one or two members’ enthusiasm wanes; small enough that you are not daunted by competing with the whole world, yet large enough that you still need to be on your toes to keep up.
Scenius
Scenius stands for the intelligence and the intuition of a whole cultural scene. It is the communal form of the concept of the genius.
Mutual appreciation
A Fragment by Matt WebbTo use slightly different terms, mutual appreciation is a healthy jealousy without envy – a drive to achieve the same but without wanting to take it from the other.
The Real World of Technology
Technology is a system
Technology is not the sum of the artifacts, of the wheels and gears, of the rails and electronic transmitters. Technology is a system. It entails far more than its individual material components. Technology involves organization, procedures, symbols, new words, equations, and, most of all, a mindset.
Fish and water
How does one speak about something that is both fish and water, means as well as end?
Defining activities
One has to keep in mind how much the technology of doing something defines the activity itself.
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.
One-machine policy
Today population forecasts are based on extensive and reliable data. However, no such demographic base exists for the world's growing population of machines and devices. Now may be the time to take machine demography seriously and enter into real discussions about machine population control.
The downgrading of experience
Today scientific constructs have become the model of describing reality rather than one of the ways of describing life around us. As a consequence there has been a very marked decrease in the reliance of people on their own experience and their own senses.
The downgrading of experience and the glorification of expertise is a very significant feature of the real world of technology.
Reciprocity
Whenever human activities incorporate machines or rigidly prescribed procedures, the modes of human interaction change. In general, technical arrangements reduce or eliminate reciprocity. Reciprocity is some manner of interactive give and take, a genuine communication among interacting parties.
Instruments of cooperation
When work isn't shared, the instruments of cooperation – listening, taking note, adjusting – atrophy like muscles that are no longer in use.
When all you have is a hammer
The success and spread of a particular tool – and this tool can be organizational or administrative as well as mechanical – has another consequence. Any task tends to be structured by the available tools. It can appear that the available tools represent the best or even the only way to deal with a situation.
Thus is may be wise, when communities are faced with new technological solutions to existing problems, to ask what these techniques may prevent and not only to check what the techniques promise to do.
Consumption
The proponents of technology in the 1840s were very enthusiastic about replacing workers with machines. But somehow I find no indication that they realized that while production could be carried out with few workers and still run to high outputs, buyers would be needed for those outputs. The realization that though the need for workers decreased, the need for purchasers could increase, did not seem to be part of the discourse on the machinery question. Since then, however, technology and its promoters have had to create a social institution – the consumer – in order to deal with the increasingly tricky problem that machines can produce but it is usually people who consume.
Bridges as walls
The biographer of Robert Moses, Robert A. Caro, refers to the bridges and underpasses of the famed New York State parkways. These bridges and underpasses are quite low, intentionally specified by Moses to allow only private cars to pass. All those who traveled by bus because they were poor or black or both were barred from the use and enjoyment of the parkland and its "public amenities" by the technical design of the bridges. Even at the time of Robert Moses, a political statement of the form "We don't want them blacks in our parks" would have been unacceptable in New York State. But a technological expression of the same prejudice appeared to be all right. Of course, to the public the intent of the design became evident only after it was executed, and then the bridges were there.
Designed to be ruins
I don't want to talk here about the grand designs of the past – the sort of thing one finds in majestic cities, in palaces and temples; the sorts of layouts that brought a friend of mine to sum up his first impression of Washington D.C. by saying, "The place seems to be designed to be ruins."
Little sense of season
The real world of technology denies the existence and the reality of nature. For instance, there is little sense of season as one walks through a North American or western European supermarket.
Just as there is a little sense of season, there is little sense of climate. Everything possible is done to equalize the ambiance – to construct and environment that is warm in the winter, cool in the summer.
Humility
Maybe what the real world of technology needs more than anything else are citizens with a sense of humility – the humility of Kepler or Newton, who studied the universe but knew they were not asked to run it.
Technological middle age
In the automobile's technological middle age, it is hard, if not impossible, to tune or repair one's own vehicle. Technical standardization of cars has occurred, and with it the elimination of the user's access to the machine itself. At the same time, the infrastructures that once served those who did not use automobiles atrophied and vanished. Some may say they were deliberately starved out. Railways gave way to more and more roadways. And thus a technology that had been perceived to liberate its users began to enslave them.
All things change
The authors of this prognostication evidently assumed that the introduction of the sewing machine would result in more sewing – and easier sewing – by those who had always sewn. They would do the work they had always done in an unchanged setting. Reality turned out to be quite different.
It should be evident by now that there is no such thing as "just introducing" a new gadget to do one particular task. It is foolish to assume that everything else in such a situation will remain the same; all things change when one thing changes.
Exploiting emotion
There are no shortcuts to the investment of time and care in friendship and human bonding, and it is fraudulent to pretend otherwise. When human loneliness becomes a source of income for others through devices, we'd better stop and think a bit about the place of human needs in the real world of technology.
The receiving end
At times it helps to rephrase an observation in line with a perspective from the receiving end of technology. When my colleagues in the field of cold-water engineering speak of "ice-infested waters", I am tempted to think of "rig-infested oceans". Language is a fine barometer of values and priorities. As such it deserves careful attention.
Speaking people
Surely those who oversee and guide municipal transportation systems ought to use public transit during their work days. Why not put a clause to that effect in their job description or contract?
Requiring those whose work has a major impact on people's lives to experience some of the impact is really not too much ask. It means that they speak "people" rather than French, Cree, or Spanish.
Ping-pong patterns
The role of asynchronicity in unraveling social and political patterns without apparent replacement with other patterns cannot be overestimated. The ping-pong pattern of verbal communication is no longer tied to space or time.
Mechanisms and organisms
"Kant described a mechanism as a functional unity, in which the parts exist for one another in the performance of a particular function.
An organism, on the other hand, is a functional and structural unity in which the parts exist for and by means of one another in the expression of a particular nature.
This means that the parts of an organism – leaves, roots, flowers, limbs, eyes, heart, brain – are not made independently and then assembled, as in a machine, but arise as a result of interactions within the developing organism."
— Brian Goodwin, How the Leopard Changed His Spots