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.
What Good Means
The center of the way
The advice I’ve received from those who are close to the center of this timeless way of building is to start small. Like with a piece of tile, or a tea tray. And to then imagine along with Christopher Alexander:
What it would be like
to live in a mental world
where one’s reasons
for making something
functionally
and one’s reasons
for making something
a certain shape,
or in a certain
ornamental way
are coming
from precisely
the same place
in you
.Seduction
“The classic pervasive seduction to designers is finding a solution instead of the truth.” — Richard Saul Wurman
What the material wants to be
Part of how Lou Kahn made things be good was to ask the material what it wanted to do and be. He asked brick what it liked, and would get a different answer depending on the context for the building. In Dacca, the capital of Bangladesh, brick said it liked an arch. For the Korman House in Philadelphia, brick said it liked two giant fireplaces with a lintel between them for a doorway beneath and a balcony above.
Asking yourself some questions
All of the moves that we make in space will tend toward being in accord with this phenomenon of wholeness / beauty / life if we’re willing to bring the requisite level of care to the doing of our work.
Alexander says that each of us possess the means for accessing this order within ourselves and — here’s where he loses most other architects and many in the so-called sciences in academia — he contends that what we’re connecting with inside of ourselves is an objective criterion for what good means.
Applying the criterion is easy: you ask yourself some questions:
With any action you might take with regard to placement, and with regard to the situatedness of things in space you ask yourself: does this move increase wholeness / beauty / life?
Does the intervention you’re taking intensify the feelings of wholeness in you as the maker when you are performing the work?
How does your work on this one part enhance what’s going on among wholes at the system level?
Losing meaning
The people who’ve proven that they can make very good individual products with the radical focus of a spotlight seem to be pushed ever further from making good ecosystems.
Products are being made “consistent” with the application of so-called “design patterns,” and rather than bringing coherence to these various touch-points, the painting-on of interface standards and interaction patterns did something far less valuable.
Rote consistency, in the way many seem to be going about it (Material Design being just one example), is at odds with making things be good. It simplifies what needs to remain complex.
Always, when simplification is underway, meaning is being lost.
Two coffee trays
We speculate that the shop owners designed and built an initial quantity of these remarkable coffee trays, replete with what Alexander considers to be the fifteen geometric properties that correlate with wholeness / beauty / life.
Then they got busy. And then they got successful. They needed more coffee trays, and our hypothesis is that somebody decided to simplify the trays to ensure they could be produced in the quantities and at the price that worked for their budget, within an urgent food-service timeline.
The simplified tray fulfills every function the more complex tray does, with less fuss in manufacturing on account of having standardized its geometry. The simplified tray works, but isn’t alive. It lacks the gradients, local symmetries, levels of scale, contrast, and boundaries that are all present and accounted for in the tray that’s got wholeness / beauty / life. The tray with wholeness isn’t necessarily better than the simpler one. But it is good.