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.
Rethinking Repair
This chapter is an exercise in broken world thinking. It asks what happens when we take erosion, breakdown, and decay, rather than novelty, growth, and progress, as our starting points in thinking through the nature, use, and effects of information technology and new media.
The modern infrastructural ideal
The form and possibility of the "modern infrastructural ideal" is increasingly under threat, as cracks (sometimes literal ones) show up in our bridges, our highways, our airports, and the nets of our social welfare systems. For these and other reasons, broken world thinking asserts that breakdown, dissolution, and change, rather than innovation, development, or design as conventionally practices and thought about are the key themes and problems facing new media and technology scholarship today.
Attached to this, however, comes a second and more hopeful approach: namely, a deep wonder and appreciation for the ongoing activities by which stability (such as it is) is maintained, the subtle arts of repair by which rich and robust lives are sustained against the weight of centrifugal odds, and how sociotechnical forms and infrastructures, large and small, get not only broken but restored, one not-so-metaphoric brick at a time.
The fulcrum of these two worlds
Here, then, are two radically different forces and realities. On one hand, a fractal world, a centrifugal world, and always-almost-falling-apart world. On the other, a world in constant process of fixing and reinvention, reconfiguring and reassembling into new combinations and new possibilities...the fulcrum of these two worlds is repair.
A creature of bones, not words
In building connections, [articulation work] builds meaning and identity, sorting out ontologies on the fly rather than mixing and matching between fixed and stable entities. Articulation lives first and foremost in practice, not representation; as its proper etymology suggests, it's a creature of bones, not words. When articulation fails, systems seize up, and our sociotechnical worlds become stuff, arthritic, unworkable.
The world is always breaking
So the world is always breaking; it's in its nature to break.
A side that goes unrecognized
Edward Burtynsky, Shipbreaking #4.
Burtynsky's [shipbreaking] photos tell us important things about the themes of breakdown, maintenance, and repair raised here. The first is the extent to which such work is rendered invisible under our normal modes of picturing and theorizing technology. Burtynsky's photos share, in exquisite detail, a side or moment of technological life that goes for the most part unrecognized.
If we are to understand maintenance, repair, and technology more broadly, scenes such as Burtynsky's must be made empirically and conceptually familiar, even normal.
Turned into other things
Ask yourself this: for all the representations of great ships in history you've encountered, at what times and in what forms have you seen such vessels? In almost every instance it will be at moments of birth, or at the heights of strength and glory: the christening before the maiden voyage, rounding the cape, facing down the Spanish fleet, and so on. But what happens (or happened) to these ships? Save for the special cases of hostile sinking, shipwreck, or honorable retirement and preservation, it was this: they were disassembled, repurposed, stripped, and turned into other things.
An engine of technological difference
Whether at the level of national "technological styles" that shape and differentiate the nature of "same" technologies in different national contexts, or the simple but consequential variations by which industrial commodities are brought into, enlivened, and sustained within the circumstances of individual homes and lives, repair may constitute an important engine by which technological difference is produced and fit is accomplished.
The internet grew by breaking
The Internet grew by breaking, bumping up against the limits of existing protocols and practices and working around them, leaving behind almost by accident some of the properties that we now enumerate as key and distinctive virtues of the Internet as infrastructural form. Far from being a generalized cultural tendency or a property of individual minds, innovation in the technology space, as in culture more generally, is therefore organized around problems. This makes innovation simultaneously specific and in some measure collective in nature. And its engine is breakdown and repair.
What the fixer knows
Can repair sites and repair actors claim special insight or knowledge, by virtue of their positioning vis-à-vis the worlds of technology they engage? Can the fixer know and see different things—indeed, different worlds—than the better-known figures of "designer" or "user"?
Tool-being
Take Heidegger's notion of "tool-being", built around the central distinction between tools that are "ready-to-hand" versus "present-at-hand".
In the former state, technologies function as anticipated, do and stay where they're supposed to, and therefore sink below the level of conscious reflection. In the latter, the material world resists, obstructs, or frustrates action, and therefore calls attention to itself (precisely because we must now work to figure out and overcome barriers in our no-longer seamless world).
An ethics of mutual care
Foregrounding maintenance and repair as an aspect of technological work invites not only new functional but also moral relations to the world of technology. It references what is in fact a very old but routinely forgotten relationship of humans to things in the world: namely, an ethics of mutual care and responsibility.
To love deeply a world of things
Care brings the worlds of action and meaning back together, and reconnects the necessary work of maintenance with the forms of attachment that so often (but invisibly, at least to analysts) sustain it.
...What if we care about our technologies, and do so in more than a trivial way? This feature or property has sometimes been extended to technologies in the past, but usually only ones that come out of deep folk or craft traditions, and rarely the products of a modern industrial culture.
...Is it possible to love, and love deeply, a world of things?
We live in the aftermath
So do we live in later modernity, postmodernity, alternative modernity, or liquid modernity? Knowledge societies, information societies, network societies, or risk societies? New media, old media, dead media, or hypermedia? The world of information, the world of search, the world of networks, or the or the world of big data?
The answer is simple: like every generation before, we live in the aftermath.