The 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 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.
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 art world is highly invested in the idea that you can take an object and set it in a room, and the internal relationships will be so strong and so meaningful that all the kinds of change that take place on the object as a result of its being in a new environment will not critically affect our perception of the object. If that is the given assumption, then the object can be moved from one environment to another without its being critically altered, which then gives rise to the illusion that it can be moved from culture to culture, that it has the ability to transcend its cultural specificity, which in turn gives rise to the ultimate illusion that the object can transcend time. Because what is being claimed is that there exist certain objects isolated and meaningful enough to be transcendent, that they have the power to go on and on, that they are, as it were, timeless.
"Well, one of the things that I was becoming involved in at that point in playing artist was the growing suspicion that this breaking down of the edge, the idea of the painting's moving into its environment, was putting the whole heightened rationale of the art object into doubt. There is simply no real separation line, only an intellectual one, between the object and its time environment. They are completely interlocking: nothing can exist in the world independent of all the other things in the world."